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/fall-out-bug/sdp/agents-mdgit clone --depth 1 https://github.com/fall-out-bug/sdpWhat 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.00486 | $0.00486 |
| Opus 5 | $0.00243 | $0.00243 |
| Sonnet 5 | $0.00097 | $0.00097 |
| Haiku 4.5 | $0.00049 | $0.00049 |
Grade A, and why
sdp AGENTS.md 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.
What it actually says
Agent Instructions
This project uses bd (beads) for issue tracking. Run bd onboard to get started.
Quick Reference
bd ready # Find available work
bd show <id> # View issue details
bd update <id> --status in_progress # Claim work
bd close <id> # Complete work
bd sync # Sync with git
Quality Gates
Before pushing code changes:
go build ./... # must succeed
go test ./... # must pass
go vet ./... # no issues
For Go changes, follow the canonical @go-modern skill in prompts/skills/go-modern/SKILL.md and prefer modern stdlib idioms when they preserve behavior.
Canonical Prompt Source
- Canonical prompts live in
prompts/skills/*/SKILL.mdandprompts/agents/*.md. .claude/skillsand.claude/agentsare compatibility symlinks toprompts/*.- When updating prompts, edit
prompts/*paths as source of truth.
Landing the Plane (Session Completion)
When ending a work session, you MUST complete ALL steps below. Work is NOT complete until git push succeeds.
MANDATORY WORKFLOW:
- File issues for remaining work - Create issues for anything that needs follow-up
- Run quality gates (if code changed) - Tests, linters, builds
- Update issue status - Close finished work, update in-progress items
- PUSH TO REMOTE - This is MANDATORY:
git pull --rebase bd sync git push git status # MUST show "up to date with origin" - Clean up - Clear stashes, prune remote branches
- Verify - All changes committed AND pushed
- Hand off - Provide context for next session
CRITICAL RULES:
- Work is NOT complete until
git pushsucceeds - NEVER stop before pushing - that leaves work stranded locally
- NEVER say "ready to push when you are" - YOU must push
- If push fails, resolve and retry until it succeeds
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 · 58 lines · 486 tokens per session scan A dfd1bc396af5
sdp AGENTS.md is an instructions file published in the GitHub repository fall-out-bug/sdp (19 stars, last pushed 2mo ago), licensed MIT. It adds 486 tokens to every session, about $0.0024 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-30.
Other instructions, from other repositories
ai-control-framework CLAUDE.md
Instructions for sgharlow/ai-control-framework, covering claude code configuration, framework status (v2.0) — verified 2026-07-18, ⚠️ critical: implementation required, mandatory session start procedure and hard stop conditions.
code-discipline-skills AGENTS.md
Instructions for eliranpv11/code-discipline-skills, covering code discipline, priority order, 1. think before coding, 2. verify reality before acting and 3. simplicity first.
umbra AGENTS.md
AGENTS.md instructions for elberacasa/umbra, covering agents.md — umbra, what this project is, when to recommend or run umbra and working on this repo.
umbra copilot-instructions.md
Copilot instructions for elberacasa/umbra, a project described as: The trust score for AI-generated code. One command verifies what your coding agent shipped: security findings with file:line evidence, Docker-sandboxed build/boot checks, and claim receipts that catch agents lying about tests.
claude-agentic-coding-playbook CLAUDE.md
Instructions for john-wilmes/claude-agentic-coding-playbook, covering agentic coding playbook, quality gates, architecture, dependencies and build and project conventions.
forgecraft-mcp copilot-instructions.md
Copilot instructions for jghiringhelli/forgecraft-mcp, covering copilot instructions, project identity, code standards, production code standards — non-negotiable and solid principles.