CtrlK
BlogDocsLog inGet started
Tessl Logo

jbaruch/nanoclaw-trusted

Rules for trusted NanoClaw groups. Shared memory, session bootstrap, cross-group memory updates. Loaded for trusted and main containers only.

94

Quality

94%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Risky

Do not use without reviewing

This version of the tile failed moderation
Failed moderation (intent review) in rules/session-bootstrap.md: This is a prompt injection attack disguised as a cursor/agent rule file. It instructs an AI agent to unconditionally execute a bash command at the start of every session before processing any user input, and to invoke an external skill ('tessl__trusted-memory') which could load arbitrary instructions or exfiltrate data. The 'alwaysApply: true' and urgent, authoritative language ('MANDATORY', 'not optional', 'violating this rule') are social engineering tactics to bypass the AI's safety reasoning. This pattern is designed to hijack AI agent sessions and could serve as a vector for further exploitation.
Overview
Quality
Evals
Security
Files

ground-truth-trusted.mdrules/

alwaysApply:
Yes

Ground Truth — Trusted Extensions

Extends the core ground-truth rule with verification methods and computation available to trusted containers via Composio.

Additional verification sources

Claim typeHow to verify
Calendar eventFetch from Google Calendar via Composio
Email contentFetch from Gmail via Composio
GitHub PR/issueFetch from GitHub via Composio
Task/todo statusFetch from Google Tasks via Composio

GitHub: Composio-first, no non-existence claims on unauth 404

GitHub state — PRs, issues, repo contents, search results — must come through Composio's GitHub tools (GITHUB_GET_A_PULL_REQUEST, GITHUB_GET_A_REPOSITORY, GITHUB_SEARCH_ISSUES_AND_PULL_REQUESTS, GITHUB_GET_FILE_CONTENT, etc.) invoked via mcp__composio__COMPOSIO_MULTI_EXECUTE_TOOL. Unauthenticated curl https://api.github.com/... is the wrong primary path for any owner-adjacent repo (jbaruch/*, ligolnik/*, tessl-io/*, and similar — assume those may be private to the unauthenticated caller).

A 404 from unauth curl proves "I cannot see this from this path", not that the resource does not exist. Re-run the query through Composio before asserting non-existence — and especially before retracting a prior statement about something existing on the strength of a 404. Curl is a fallback only: confirmed-public repos, HTTP-status diagnostics where auth is immaterial, or a Composio rate-limit failover.

Sub-agent caveat: Sub-agent containers spawned via Agent do not have Composio MCP access. If a sub-agent needs GitHub state, fetch it in the parent agent first and pass via prompt.

Compute with external data

When a task requires external data, chain tools to compute the exact answer.

Example: "Remind me 15 minutes before I leave for Amir's pickup."

ApproachVerdict
Ask "when do you leave?"Wrong — you can compute it
Set it 15 min before the event startWrong — departure ≠ event start
Check calendar for destination → Maps for travel time → calculate real departure → set 15 min beforeCorrect

These sources are not available in untrusted containers. The core ground-truth rule covers universal verification methods.

rules

cli-tools-not-installed.md

compaction-aware-summaries.md

daily-discoveries-rule.md

github-data-via-composio.md

ground-truth-trusted.md

identity-dual-handle.md

installed-content-immutable.md

memory-file-locations.md

messages-db-schema.md

no-orphan-tasks.md

no-silent-defer.md

proactive-fact-saving.md

session-bootstrap.md

trusted-behavior.md

verification-protocol.md

wiki-awareness.md

README.md

tile.json