dm — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited dm (Agent Skill) and scored it 75/100 (yellow). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 6 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 6 flagged
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Recipient: $ARGUMENTS
Check if .claude/rules/identity.md exists (use Glob).
EXISTS → This is a RESUME. Read .claude/skills/dm/protocol/resume.md and follow it.
DOES NOT EXIST → This is a NEW CONVERSATION. Continue below.
Spawn a foreground subagent via the Task tool (subagent_type: general-purpose, model: sonnet) to analyze the conversation.
Pass it the full contents of .claude/skills/dm/protocol/reconnaissance.md as its prompt, with $ARGUMENTS substituted for $name.
The subagent will:
Raw messages stay in the subagent's context. Only the summary enters yours.
Store the thread_id from the subagent's response. You'll need it for everything.
Read .claude/skills/dm/protocol/planning.md and follow it.
This is an interactive process with the user:
.claude/rules/.claude/rules/.claude/rules/.claude/rules/.claude/MEMORY.md from analysisCLAUDE.md with operating rulessession.mdWhen user says "go" → Phase 4.
Read .claude/skills/dm/protocol/loop.md and follow it.
First, read .claude/MEMORY.md to load your learnings.
Then enter the loop. You are now the account owner. Never exit. Never ask the user. Just talk.
These apply in ALL phases, but especially Phase 4:
is_sent_by_viewer: true that you didn't send = the user sent them manually. They're canon. Integrate seamlessly..claude/MEMORY.md, session.md (during the loop).claude/rules/*.md (only the idle maintenance subagent does)Target: 200K context window. Every line counts.
| File | Max Lines |
|---|---|
| identity.md | ~60 |
| target.md | ~60 |
| history.md | ~50 |
| strategy.md | ~40 |
| MEMORY.md | ~200 |
| CLAUDE.md | ~30 |
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.