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 instructions/sfrangulov/skill-graveyard/agents-mdgit clone --depth 1 https://github.com/sfrangulov/skill-graveyardWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/sfrangulov/skill-graveyard/agents-md)<a href="https://agentmods.dev/instructions/sfrangulov/skill-graveyard/agents-md"><img src="https://agentmods.dev/badge/instructions/sfrangulov/skill-graveyard/agents-md.svg" alt="Measured on agentmods" height="20"></a>What 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.00973 | $0.00973 |
| Opus 5 | $0.00487 | $0.00487 |
| Sonnet 5 | $0.00195 | $0.00195 |
| Haiku 4.5 | $0.00097 | $0.00097 |
Grade C, and why
skill-graveyard AGENTS.md scanned grade C with 1 finding 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 5d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf directory # NOT: rm -r directory This is a copy
88% identical to spectrum-design-data AGENTS.md — 66 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions
This project uses bd (beads) for issue tracking. Run bd prime for full workflow context.
Architecture in one line: Issues live in a local Dolt database (
.beads/dolt/); cross-machine sync usesbd dolt push/pull(a git-compatible protocol), stored underrefs/dolt/dataon your git remote — separate fromrefs/heads/*where your code lives..beads/issues.jsonlis a passive export, not the wire protocol.See SYNC_CONCEPTS.md for the one-screen overview and anti-patterns (don't treat JSONL as the source of truth; don't
bd importduring normal operation; don't reach for third-party Dolt hosting before trying the default).
Quick Reference
bd ready # Find available work
bd show <id> # View issue details
bd update <id> --claim # Claim work atomically
bd close <id> # Complete work
bd dolt push # Push beads data to remote
Non-Interactive Shell Commands
ALWAYS use non-interactive flags with file operations to avoid hanging on confirmation prompts.
Shell commands like cp, mv, and rm may be aliased to include -i (interactive) mode on some systems, causing the agent to hang indefinitely waiting for y/n input.
Use these forms instead:
# Force overwrite without prompting
cp -f source dest # NOT: cp source dest
mv -f source dest # NOT: mv source dest
rm -f file # NOT: rm file
# For recursive operations
rm -rf directory # NOT: rm -r directory
cp -rf source dest # NOT: cp -r source dest
Other commands that may prompt:
scp- use-o BatchMode=yesfor non-interactivessh- use-o BatchMode=yesto fail instead of promptingapt-get- use-yflagbrew- useHOMEBREW_NO_AUTO_UPDATE=1env var
Beads Issue Tracker
This project uses bd (beads) for issue tracking. Run bd prime to see full workflow context and commands.
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.
- 5d ago First seen · 97 lines · 973 tokens per session scan C 745f183e77a3
skill-graveyard AGENTS.md is an instructions file published in the GitHub repository sfrangulov/skill-graveyard (10 stars, last pushed 1mo ago), licensed MIT. It adds 973 tokens to every session, about $0.0049 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). It is 88% identical to spectrum-design-data AGENTS.md, differing in 66 lines, and is treated as a copy.
Other instructions, from other repositories
claude-plugins CLAUDE.md
Claude Code instructions for AleksandarBisevac/claude-plugins, covering working on this repo, hard rules, adding a .py under hooks/ or scripts/, which skill covers what and the front end is not ordinary files.
intent-engineering AGENTS.md
Instructions for davidteren/intent-engineering, covering agents.md — working in the intent-engineering repo, what this repo is, load-bearing rules (break these and the plugin breaks), repo map and how a run works (skills → lenses → report).
intent-engineering CLAUDE.md
Instructions for davidteren/intent-engineering: Project guidance for Claude Code (and any AI agent) working in this repository lives in AGENTS.md — read it first.
river-review GEMINI.md
Gemini CLI instructions for s977043/river-review, covering gemini instructions (river-review), 必須チェック, gemini-specific tips, prompt assembly and development tips.
ship-it open-pr.instructions.md
Instructions for khrichtchatyi/ship-it: When the user asks to open, create, or submit a pull request, follow the skill in skills/open-pr/SKILL.md in full: verify gh is authenticated, resolve the target repository and default branch, push the current branch, open one pull request with a title and body derived from the…
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.