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 skills/fall-out-bug/sdp/protocol-consistencynpx skills add fall-out-bug/sdp --skill protocol-consistencygit 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.00018 | $0.00189 |
| Opus 5 | $0.00009 | $0.00095 |
| Sonnet 5 | $0.00004 | $0.00038 |
| Haiku 4.5 | $0.00002 | $0.00019 |
Grade A, and why
protocol-consistency 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 3d 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
@protocol-consistency
Detect drift between docs, CLI, and CI.
Workflow
- Verify CLI —
sdp --help,sdp <cmd> --help— commands in docs exist - Validate WS schema — Read
docs/workstreams/backlog/<ws-id>.md, runsdp drift detect <ws-id> - Validate CI —
rg "sdp .*" .github/workflows hooks scripts— paths valid - Report — Source file, observed vs expected, risk, suggested fix
- Track —
bd create --title="Protocol drift: ..." --type=task --priority=2
Output
Report: scope, blocking/non-blocking mismatches, findings, recommended fixes.
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.
- 3d ago First seen · 21 lines · 18 tokens per session scan A 26cb9408b1c6
protocol-consistency is a skill published in the GitHub repository fall-out-bug/sdp (19 stars, last pushed 2mo ago), licensed MIT. It adds 18 tokens to every session and 189 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-30.
Other skills, from other repositories
typescript-best-practices
Enforces TypeScript best practices and modern patterns.
Tech Debt Auditor
Identifies and prioritizes technical debt in a codebase with an effort/impact matrix.
Unit Test Improver
Reviews existing unit tests for gaps, weak assertions, and missing edge cases, then rewrites them to be more robust.
Refactor Planner
Creates a safe, step-by-step plan to refactor messy code without breaking existing behavior.
code-discipline
Coding methodology for production-grade software development. Enforces structured thinking before coding, verifying reality, simplicity, surgical changes, contract awareness, and verifiable success criteria. Use when writing, reviewing, or refactoring code that needs to remain reliable over time, including production…
umbra-trust-review
Verify AI-generated code before shipping. Run Umbra's Trust Score scan before committing or finishing any coding task, treat findings as blocking issues, and re-scan until clean. Use when finishing a task, before a commit, or when reviewing code written by an agent.