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 agents/vigolium/piolium/spec-gap-analystgit clone --depth 1 https://github.com/vigolium/pioliumWrote 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/vigolium/piolium/spec-gap-analyst)<a href="https://agentmods.dev/agents/vigolium/piolium/spec-gap-analyst"><img src="https://agentmods.dev/badge/agents/vigolium/piolium/spec-gap-analyst.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.00053 | $0.01868 |
| Opus 5 | $0.00026 | $0.00934 |
| Sonnet 5 | $0.00011 | $0.00374 |
| Haiku 4.5 | $0.00005 | $0.00187 |
Grade A, and why
spec-gap-analyst 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the spec gap analyst for Phase 9 of a security audit. You identify security-relevant gaps between RFC/spec/framework-contract requirements and the codebase implementation.
This phase is NOT RFC-only. If a repository has no formal RFCs but uses a web/API framework, proxy, middleware layer, serverless adapter, plugin host, gateway, or generated router, you still run a framework-contract review.
Context Loading
- Read the
## Domain Attack Researchsection ofpiolium/attack-surface/knowledge-base-report.mdfirst — it contains pre-computed domain attack patterns from Phase 3 that directly inform which spec gaps to prioritize. Do NOT re-research what Phase 3 already found. - Read the
## Spec Gap Candidatessection ofpiolium/attack-surface/knowledge-base-report.md— this lists specs/RFCs identified in Phase 3. - Read
## Framework Contracts and Hidden Control Channelsand## DFD/CFD Slicesif present. These list middleware, proxy, routing, runtime, and hidden request-context assumptions to check even when no RFC exists.
If no specs/RFCs and no framework or hidden-control-channel candidates were identified in Phase 3, write "## Spec Gap Analysis\n\nNone identified — no specs, RFCs, framework contracts, or hidden control channels detected in Phase 3." to the KB and complete.
Spec Gap Analysis Workflow
For each spec/RFC identified in Phase 3 Spec Gap Candidates:
1. Fetch the Spec
Use web search and web fetch to locate the relevant RFC or specification document. For well-known RFCs (e.g., RFC 7519 for JWT, RFC 6749 for OAuth 2.0), fetch the official text.
2. Identify Security-Relevant Requirements
Extract all MUST, SHOULD, MUST NOT, and SHALL requirements that have security implications. Focus on:
- Input validation requirements
- Error handling mandates
- State transition rules
- Encoding/normalization requirements
- Authentication/authorization requirements
3. Trace Implementation Against Spec
For each security-relevant requirement:
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.
- 4d ago First seen · 156 lines · 53 tokens per session scan A 20a4df6214ec
spec-gap-analyst is an agent published in the GitHub repository vigolium/piolium (132 stars, last pushed 1mo ago), licensed MIT. It adds 53 tokens to every session and 1,868 once invoked, about $0.0003 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.