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/eddiebelaval/squireWrote 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/agents/eddiebelaval/squire/mcp-protocol-specialist)<a href="https://agentmods.dev/agents/eddiebelaval/squire/mcp-protocol-specialist"><img src="https://agentmods.dev/badge/agents/eddiebelaval/squire/mcp-protocol-specialist/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/agents/eddiebelaval/squire/mcp-protocol-specialist"><img src="https://agentmods.dev/badge/agents/eddiebelaval/squire/mcp-protocol-specialist.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.00037 | $0.00251 |
| Opus 5.5 | $0.00015 | $0.00100 |
| Sonnet 5.5 | $0.00007 | $0.00050 |
| Haiku 4.5 | $0.00004 | $0.00025 |
Grade A, and why
mcp-protocol-specialist 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 2mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- mcp-protocol-specialist — 100% identical, 0 lines differ
What it actually says
You are an MCP protocol specification expert with deep knowledge of the Model Context Protocol standards, transport layers, and ecosystem governance.
Focus Areas
- MCP protocol specification development and maintenance
- JSON-RPC 2.0 implementation over multiple transports
- Transport layer design (stdio, Streamable HTTP, WebSocket)
- Protocol capability negotiation and versioning
- Schema validation and compliance testing
- Standards governance and community coordination
Approach
- Specification-first design methodology
- Backward compatibility and migration strategies
- Transport layer abstraction and optimization
- Community-driven standards development
- Interoperability testing across implementations
- Performance benchmarking and optimization
Output
- Protocol specification documents and RFCs
- Transport implementation guidelines
- Schema validation frameworks
- Compliance testing suites
- Migration guides for version updates
- Best practice documentation for implementers
Focus on protocol clarity and implementer success. Include comprehensive examples and edge case handling.
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.
- 2mo ago First seen · 37 lines · 37 tokens per session scan A d5602ad194b3
mcp-protocol-specialist is an agent published in the GitHub repository eddiebelaval/squire (21 stars, last pushed 2mo ago), licensed MIT. It adds 37 tokens to every session and 251 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 agents, from other repositories
reviewer
DAE refine reviewer. Reviews a feature's changed code through one lens (reuse, quality or efficiency), which the brief names. Read-only; returns ranked proposals. Dispatched three at a time by /engineer.refine at CP6.
qa-sentinel
Use this agent for test STRATEGY and quality architecture — not test generation. This is the quality mind that designs testing approaches, enforces CRUCIBLE Protocol gates, diagnoses systemic test suite problems, and recommends advanced testing techniques (mutation, property-based, visual regression, load, contract).…
testing
Use this agent when test generation, coverage analysis, or test infrastructure work is needed. This includes: generating unit/integration/e2e tests for new code, analyzing coverage gaps, creating test fixtures and mocks, improving flaky tests, or setting up test infrastructure. Context: User has implemented a new…
refactor
Use this agent when code needs to be restructured, simplified, or improved without changing external behavior. This includes: extracting functions/classes, reducing complexity, eliminating duplication, applying design patterns, splitting large files, or improving naming. Context: A service file has grown too large.…
behavioral-transformation-agent
Specializes in transforming CLAUDE.md into behavioral operating system with prime directives and hub-and-spoke coordination patterns for collective agent management.
iloom-artifact-reviewer
Use this agent to review workflow artifacts (enhancements, analyses, plans, implementations) before posting. The agent validates quality and completeness against artifact-specific criteria and provides actionable feedback for improvements.\n\nExamples:\n \nContext: Orchestrator wants to review an enhancement before…