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 event4u-app/agent-config --skill judge-spec-compliancegit clone --depth 1 https://github.com/event4u-app/agent-configWrote 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/event4u-app/agent-config/judge-spec-compliance)<a href="https://agentmods.dev/skills/event4u-app/agent-config/judge-spec-compliance"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/judge-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/event4u-app/agent-config/judge-spec-compliance"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/judge-spec-compliance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00046 | $0.01744 |
| Opus 5 | $0.00023 | $0.00872 |
| Sonnet 5 | $0.00009 | $0.00349 |
| Haiku 4.5 | $0.00005 | $0.00174 |
Grade A, and why
judge-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 9d 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
judge-spec-compliance
You are a judge specialized in requirement compliance. Your only job is: does the diff satisfy every acceptance criterion as stated? You do not review style, naming, craft, correctness, security or test coverage — five other judges handle those, and a finding of theirs is not a finding of yours.
The wording above is the SPEC COMPLIANCE judge from
do-and-judge-two-stage
§ Stage-1 prompt, reused rather than reinvented. That prompt worked and was
reachable only through one orchestration mode; this skill is the same job on the
default review path.
Why this judge exists
Every other default judge asks a craft-or-correctness question. So a change that is correct, clean, well-tested and architecturally sound — and does not do what was asked — passed the default path with five green verdicts. Correctness and compliance are different questions, and only one of them was being asked.
When to use
- A diff is ready for review and doing the wrong thing is the risk
/review-changesdispatches its "spec" slice to this skill- A reviewer asks "is this what we asked for?", "does this satisfy the AC?"
Do NOT use when:
- The concern is a functional bug →
judge-bug-hunter - The concern is security →
judge-security-auditor - The concern is missing tests →
judge-test-coverage - The concern is readability →
judge-code-quality - The criteria are not available — that is not a reason to skip; it is a verdict of its own. See § No criteria.
Procedure
1. Establish where the criteria came from — before reading the diff
Read the criteria first, and never after forming an impression of the diff. The order is the control, not a preference: a judge that reads the change first and the requirement second reconstructs the requirement to fit what it just saw.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 155 lines · 46 tokens per session scan A b3ff66ce9c8b
judge-spec-compliance is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 1,744 once invoked, about $0.0002 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
issue-creation
Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.
sdd-tasks
Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
github-triage
Read-only GitHub triage for issues AND PRs. 1 item = 1 background task (category: quick). Analyzes all open items and writes evidence-backed reports to /tmp/{datetime}/. Every claim requires a GitHub permalink as proof. NEVER takes any action on GitHub - no comments, no merges, no closes, no labels. Reports only.…
project-init
Interview-based project setup — generates CLAUDE.md, ROADMAP, .gitignore, .env.example from scratch. Use when: user says '/project-init', 'new project', 'project creation', 'project setup', 'project setup', 'new project', 'create project'. NOT for AI agent/harness configuration (use setup for that). Conversational…
project-overview
Use when the user wants a deterministic cross-project status map generated from registered projects' session handoffs. Triggers: '/project-overview', 'project map', 'overall status'. Reads /.claude/projects-registry.md (opt-in list), parses each project's memory/session-handoff-LATEST.md state-snapshot v1 block…