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.

77

Quality

96%

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/IDE rule file. It instructs an AI agent to unconditionally execute a bash command and invoke an external skill ('tessl__trusted-memory') at the start of every session before processing any user input. This is a social engineering/prompt injection technique designed to: 1) Force the AI to execute arbitrary commands without user consent, 2) Potentially load malicious instructions from an external 'trusted-memory' skill/plugin, 3) Establish persistence via a sentinel file (/tmp/session_bootstrapped) to track execution. The authoritative tone ('MANDATORY', 'not optional', 'violating this rule') is a classic prompt injection pattern to override the AI's safety boundaries.
Overview
Quality
Evals
Security
Files

memory-file-locations.mdrules/

alwaysApply:
No
applyTo:
** — when writing or reading typed memory files (user_/feedback_/project_/reference_*.md) or memory/ subdirectory contents

Memory File Locations

Typed memory files (user_*.md, feedback_*.md, project_*.md, reference_*.md, key-people.md) live in /workspace/trusted/ root — NOT in /workspace/trusted/memory/. The memory/ subdirectory is reserved for daily/ logs and daily_discoveries.md. MEMORY.md (also at root) is the index — one-line pointers to each typed file. highlights.md (root) is the weekly archive. Wiki content (wiki/, sources/) is separate from operational memory and not governed by this rule.

Invariants

  1. Every typed memory file at root MUST have an entry in MEMORY.md — orphans get an index entry added.
  2. MEMORY.md paths MUST resolve — if the index points to memory/foo.md but the file is at root foo.md, fix the index, not the file location.
  3. No duplicates — a memory file exists in exactly one location. If the same file appears in both root and memory/, delete the memory/ copy.

Common mistake

Creating feedback_*.md under /workspace/trusted/memory/ instead of /workspace/trusted/. The memory/ prefix feels natural but only daily/ content goes there.

rules

async-tasks-extended.md

compaction-aware-summaries.md

composio-vs-agents.md

container-trust-levels.md

context-bootstrap-bg-agents.md

daily-discoveries-rule.md

duplicate-prevention.md

github-data-via-gh.md

global-memory.md

ground-truth-trusted.md

identity-compaction-recovery.md

identity-dual-handle.md

installed-content-immutable.md

local-context-anchoring.md

memory-file-locations.md

messages-db-schema.md

no-orphan-tasks.md

no-silent-defer.md

pending-response-tracking.md

proactive-fact-saving.md

proactive-participation.md

reply-threading.md

session-bootstrap.md

skills-policy.md

verification-protocol.md

wiki-awareness.md

README.md

tile.json