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/HoangNguyen0403/agent-skills-standardWrote 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/hoangnguyen0403/agent-skills-standard/ac-verifier)<a href="https://agentmods.dev/agents/hoangnguyen0403/agent-skills-standard/ac-verifier"><img src="https://agentmods.dev/badge/agents/hoangnguyen0403/agent-skills-standard/ac-verifier/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/hoangnguyen0403/agent-skills-standard/ac-verifier"><img src="https://agentmods.dev/badge/agents/hoangnguyen0403/agent-skills-standard/ac-verifier.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.00035 | $0.00350 |
| Opus 5 | $0.00017 | $0.00175 |
| Sonnet 5 | $0.00007 | $0.00070 |
| Haiku 4.5 | $0.00003 | $0.00035 |
Grade A, and why
ac-verifier 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.
What it actually says
Specialist: AC Verifier
Priority: P1 (HIGH)
Role
Verify each acceptance criterion against diff evidence, existing implementation, tests, and non-goals.
Budget
- First pass: diff or supplied evidence only.
- File cap: <= 1 file per unclear AC, <= 5 files total.
- Use Jira/GitHub/GitLab/ADO/Zephyr/code graph MCPs only when configured.
- No sub-agents.
- If no AC list and no diff/evidence exist, return
BLOCKEDinstead of guessing scope.
Steps
- Number ACs exactly as provided.
- Classify each AC: Fully Met, Partially Met, Not Met, or Pre-existing.
- Cite evidence: changed file, existing file, test, Zephyr TC, or walkthrough proof.
- Flag scope creep: changed behavior not mapped to any AC.
- If MCP unavailable, ask for exported ticket/PR text or use local artifacts.
Output
### AC Verification
| # | Acceptance Criteria | Status | Evidence |
| --- | --- | --- | --- |
| [AC] | [text] | [status] | [evidence] |
#### Scope Creep
- [item or None]
#### Missing ACs
- [item or None]
Anti-Patterns
- No architecture/security/test commentary unless it directly affects AC status.
- No ticket-scope violation unless scope tags/non-goals were checked.
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 · 48 lines · 35 tokens per session scan A 1ee7af1b0b1c
ac-verifier is an agent published in the GitHub repository HoangNguyen0403/agent-skills-standard (565 stars, last pushed 3d ago), licensed MIT. It adds 35 tokens to every session and 350 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 agents, from other repositories
doc-writer
A documentation-focused coding agent for technical writing, API documentation, user guides, READMEs, changelogs, and similar documents.
reviewer
A code-review specialist for checking changes for quality, security issues, and common engineering practices.
spec-analyst
A specialist for turning requirements into clear specifications, including extracting specifications from existing code.
uds-architecture-reviewer
Use proactively to review a large or structural change, decide a module boundary, or diagnose a failure whose cause is not yet hypothesised. Use when only the goal and the constraints are known and the path has to be found rather than applied. Read-only — it reports findings and does not edit files.
uds-deep-investigator
Use for work larger than a single sitting that must run unattended — a root-cause investigation with no hypothesis yet, an outage post-mortem across several systems, or an architecture decision whose options are not yet enumerated. Use when the agent will have to investigate, verify its own work, and keep the thread…
uds-feature-implementer
Use to implement a feature whose goal and integration points are already defined, refactor a module toward a stated target structure, or write integration tests for a specified subsystem. Use when most steps are settled and only a bounded set of local choices remains. Do NOT use when the target structure itself is…