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 skills add paruff/uFawkesAI --skill spec-compliancegit clone --depth 1 https://github.com/paruff/uFawkesAIWrote 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/skills/paruff/ufawkesai/spec-compliance)<a href="https://agentmods.dev/skills/paruff/ufawkesai/spec-compliance"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/spec-compliance/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/skills/paruff/ufawkesai/spec-compliance"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/spec-compliance.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.00023 | $0.00463 |
| Opus 5 | $0.00012 | $0.00231 |
| Sonnet 5 | $0.00005 | $0.00093 |
| Haiku 4.5 | $0.00002 | $0.00046 |
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 8d 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
Skill: Specification Compliance Validation
Load trigger:
"load spec-compliance skill"> DORA: Cap 1 (AI Policy) Token cost: Low
Purpose
Verify that the build output satisfies the specification.
Responsibilities
- Compare implementation to functional requirements
- Compare implementation to non-functional requirements
- Identify missing or incomplete features
- Identify deviations from the specification
Inputs
specification.md- Build output (code, manifests, pipelines)
Outputs
spec-compliance.json
Validation Rules
Functional Requirements
- Each functional requirement has a corresponding implementation
- Implementation matches the requirement's intent
- No extra features added without spec justification
- Edge cases from spec are handled
Non-Functional Requirements
- Performance requirements met (response times, throughput)
- Scalability requirements addressed
- Availability requirements addressed
- Security requirements implemented
Completeness
- No requirements skipped
- No partial implementations
- No placeholder or stub implementations left in place
Deviation Tracking
- Any deviation from spec is documented
- Deviation has justification
- Deviation does not violate core requirements
Output Format
{
"skill": "spec-compliance",
"status": "pass | fail",
"requirements": [
{
"id": "REQ-001",
"description": "Requirement description",
"status": "pass | fail | partial",
"implementation": "How it was implemented",
"notes": "Any deviations or issues"
}
],
"missing": [],
"deviations": []
}
Success Criteria
- Build output fully satisfies the specification
- All requirements accounted for
- Deviations documented and justified
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.
- 8d ago First seen · 89 lines · 23 tokens per session scan A cb796d2da499
spec-compliance is a skill published in the GitHub repository paruff/uFawkesAI (2 stars, last pushed 19d ago), licensed MIT. It adds 23 tokens to every session and 463 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-09-03.
Other skills, from other repositories
template-formal
Strongly-typed multiagent ant-robot colony exemplar — ADTs, session-typed protocols, affine-discipline resource handles, storage-as-functor framing, Active-Inference-flavored decision loop, mypy-as-oracle negative controls.
template-reproducibility-audit
Deterministic reproducibility audit — fixed seeds, regenerate-from-clean, double-run diff before Zenodo/arXiv/release. USE WHEN outputs drift between runs, "worked on my machine", need regenerate-from-clean proof, or pre-release reproducibility check — even without naming docs/prompts.
template-test-creation
Create pytest suites under the no-mocks policy — real data, temp files, subprocess, pytest-httpserver. USE WHEN adding tests, raising coverage, testing new src/ module, or user forbids mocks.
infrastructure-benchmark
Deterministic benchmark harnesses for public template exemplars. Use when scoring generated project outputs against benchmark manifests, refreshing the default template smoke manifest, checking publication-readiness rubrics, or adding bounded no-network readiness checks for public template outputs.
infrastructure-sia
Skill for the Self-Improvement Agent (SIA) harness contract. Use when validating task public/private layouts, generation artifact trees, evaluation runners, fixture replay loops, or opt-in live Meta→Target→Feedback cycles in template projects.
template-sia
SIA (Self-Improvement Agent) harness exemplar — Meta/Target/Feedback loops, public/private splits, fixture replay, fail-closed validation.