Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/dbwls99706/deadends.dev/add-canongit clone --depth 1 https://github.com/dbwls99706/deadends.devWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00025 | $0.03014 |
| Opus 5 | $0.00013 | $0.01507 |
| Sonnet 5 | $0.00005 | $0.00603 |
| Haiku 4.5 | $0.00003 | $0.00301 |
Grade A, and why
add-canon scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 293 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/add-canon — one content-growth cycle
Goal: grow indexable, non-duplicate content on deadends.dev, one small PR at a time. SEO survival depends on a steady drip of genuinely new, primary-sourced pages — not bulk dumps of near-identical entries.
Run this end to end. Do not stop after authoring; the cycle is only done when the PR is merged (or you have reported a hard blocker).
Argument (optional): $ARGUMENTS may name a target, e.g. visa jp,
banking br, emergency pl, or a domain like legal. If empty, pick the gap
yourself in step 3 — but run step 2 either way, so you do not collide with a
cycle already in flight.
1. Start from a clean, fresh branch
A merged PR is finished — never reuse its branch. Always cut a new one from
main:
git fetch origin main
git checkout -B canon/$(git log -1 --format=%cd --date=format:%Y%m%d origin/main)-$RANDOM origin/main
Prefer a descriptive name once you know the topic, e.g.
canon/visa-jp-work-permit. Confirm git config user.email is
[email protected] before committing.
2. Claim a target no open PR is already working on
main is not the whole picture. Other cycles may be running right now with
branches already pushed, and their canons will not show up in any count of
data/canons/. Three separate PRs once authored New Zealand coverage at the
same time because each of them looked only at main.
List the open PRs and the files they touch before choosing anything:
# mcp__github__list_pull_requests (state: open), then for each PR:
# mcp__github__pull_request_read (method: get_files)
Treat every country appearing in an open PR as taken, and pick a different one.
Step 6 excludes the canon IDs those branches touch on its own, by reading the pushed branches. It cannot see a PR from a fork, so note the touched IDs of any fork PR here and pass them along explicitly.
3. Pick a real coverage gap (never duplicate)
Count what already exists, then choose an underserved slice:
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 293 lines · 25 tokens per session scan A 6609e307cdcb
add-canon is a command published in the GitHub repository dbwls99706/deadends.dev (0 stars, last pushed 2d ago), licensed MIT. It adds 25 tokens to every session and 3,014 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
commit
Analyze changes and create a high-quality git commit.
quick-commit
Create a conventional commit with an auto-generated message.
commit
Analyze git diffs or staged changes and generate conventional commit messages that explain WHY a change was made. Supports auto-detecting type and scope, intelligent file staging, and interactive overrides. Use when asked to "write a commit message", "generate a commit", "describe my changes", "commit this"…
fest-commit
Commit changes with festival traceability metadata.
ship
Autonomous spec-to-PR pipeline with zero approval gates.
/commit-push
Commit and push all changes from this chat session using Conventional Commits.