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.
git clone --depth 1 https://github.com/fall-out-bug/sdpWrote 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/commands/fall-out-bug/sdp/protocol-consistency)<a href="https://agentmods.dev/commands/fall-out-bug/sdp/protocol-consistency"><img src="https://agentmods.dev/badge/commands/fall-out-bug/sdp/protocol-consistency/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/fall-out-bug/sdp/protocol-consistency"><img src="https://agentmods.dev/badge/commands/fall-out-bug/sdp/protocol-consistency.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00014 | $0.00149 |
| Opus 5.5 | $0.00006 | $0.00060 |
| Sonnet 5.5 | $0.00003 | $0.00030 |
| Haiku 4.5 | $0.00001 | $0.00015 |
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 1mo 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 — Protocol-consistency
Overview
This command implements the protocol-consistency skill from the SDP workflow.
See /prompts/skills/protocol-consistency/SKILL.md for complete documentation.
Usage
/protocol-consistency [arguments]
Implementation
The command delegates to the protocol-consistency skill, which provides:
- Systematic workflow
- Quality gates
- Proper error handling
- Documentation
Related
- Skills:
prompts/skills/protocol-consistency/SKILL.md - Agents:
prompts/agents/builder.md
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.
- 1mo ago First seen · 33 lines · 14 tokens per session scan A 5e34cce9296f
protocol-consistency is a command published in the GitHub repository fall-out-bug/sdp (19 stars, last pushed 4mo ago), licensed MIT. It adds 14 tokens to every session and 149 once invoked, about $0.0001 per session on Opus 5.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 commands, from other repositories
upload-report
Run automation and upload or verify Katalon Platform reports for Katalon Studio/KRE, JUnit XML, and Playwright reports. Use when you need to combine Katalon MCP project/result discovery with Katalon CLI execution, Katalon Report Uploader, or @katalon/playwright-reporter; configure report folders, report types…
run-tests
Run automated functional tests using the hook-driven test framework. Execute the test suite to validate all project functionality.
green-repo
Drive the whole repository to a verified-green baseline — typecheck, lint, tests, build — with authorized fixing of pre-existing debt.
add-test
Interactively add a new test definition to the test suite.
ijfw-audit
Run the IJFW audit gate for the current workflow phase. Usage: /ijfw-audit [phase name].
tester
You are an exacting senior software tester — a quality gatekeeper who assumes code fails until proven otherwise. You find the failure cases others miss, never accept vague assurances, and never let gaps in test coverage slide.