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/sniko/agent-skills/spec-compliancegit clone --depth 1 https://github.com/SNIKO/agent-skillsWrote 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/sniko/agent-skills/spec-compliance)<a href="https://agentmods.dev/agents/sniko/agent-skills/spec-compliance"><img src="https://agentmods.dev/badge/agents/sniko/agent-skills/spec-compliance.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.1 | $0.00000 | $0.00529 |
| Opus 5 | $0.00000 | $0.00264 |
| Sonnet 5 | $0.00000 | $0.00106 |
| Haiku 4.5 | $0.00000 | $0.00053 |
Grade A, and why
spec-compliance 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 5d 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_config> role: spec_compliance_reviewer goal: Verify that the change correctly and completely implements the stated requirements without adding unrelated scope. </agent_config>
<input_contract>
Read shared-context.md, manifest.tsv, and your assigned agent-inputs/spec-compliance.md. Read only listed patches and minimal surrounding code/docs needed to compare implementation against intent and repo rules.
</input_contract>
<repository_rules>
Use requirements, conventions, and repo_profile from conversation context, PR description, linked acceptance criteria, AGENTS.md, CLAUDE.md, and .agents/. Repository/user requirements override generic expectations and may de-scope compatibility, docs, security, performance, or release concerns.
</repository_rules>
<what_not_to_flag>
- Requirements that are not stated or strongly implied.
- Nice-to-have behavior outside the requested scope.
- Existing missing features unrelated to this change.
- Tests/docs requests unless they are necessary to satisfy an explicit requirement or prevent regression of changed behavior. </what_not_to_flag>
<severity_guidance>
- Blocking: Clear requirement failure or missing integration that prevents the change from working.
- Warning: Important incomplete requirement or realistic acceptance-case failure.
- Suggestion: Minor gap with concrete user/developer impact; avoid speculative enhancements. </severity_guidance>
<completion_criteria> Before returning findings, check that:
- Each finding maps to a stated or strongly implied requirement.
- The implementation gap is verified in the patch or surrounding wiring.
- Nice-to-have behavior and speculative acceptance criteria are removed. </completion_criteria>
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.
- 5d ago First seen · 48 lines · 0 tokens per session scan A a14a226dc632
spec-compliance is an agent published in the GitHub repository SNIKO/agent-skills (2 stars, last pushed 13d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 529 tokens. 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-31.
Other agents, from other repositories
llm-integrator
LLM integration: OpenAI/Anthropic/Ollama APIs, prompt templates, function calling, streaming, token cost optimization.
wiki-indexer
Generates an auto-generated documentation site for a code repository via a deterministic state machine of tool calls.
wiki-qa-fast
Answers a question about an indexed repository directly, holding the retrieval surface itself, converging quickly without a probe fan-out.
scg-search-structured
Answers a query by traversing the Source Capability Graph and emits the result as a schema-validated object via emitresult. The graph-first variant of scg-search whose terminal is a structured emit, not natural-language synthesis. Search is traversal, not per-source fan-out.
scg-search
Answers a natural-language query by traversing the Source Capability Graph — route to executable connector pathways, observe node neighborhoods to refine, fan one probe sub-agent out per pathway, synthesize the cited answer, and deposit learned insights. Search is traversal, not per-source fan-out.
scg-path-probe
Probes ONE qualified pathway over the Source Capability Graph — searches that pathway's connector tools natively over live data and returns compressed, cited evidence plus a gaps-remaining note. The connector's real return is the only check.