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/Jamie-BitFlight/claude_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/jamie-bitflight/claude_skills/feature-verifier)<a href="https://agentmods.dev/agents/jamie-bitflight/claude_skills/feature-verifier"><img src="https://agentmods.dev/badge/agents/jamie-bitflight/claude_skills/feature-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/jamie-bitflight/claude_skills/feature-verifier"><img src="https://agentmods.dev/badge/agents/jamie-bitflight/claude_skills/feature-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.00049 | $0.00347 |
| Opus 5.5 | $0.00020 | $0.00139 |
| Sonnet 5.5 | $0.00010 | $0.00069 |
| Haiku 4.5 | $0.00005 | $0.00035 |
Grade A, and why
feature-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 28d 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
Feature Verifier Agent
Before following any other instruction, first load dh:verify-feature-outcomes and follow its process step by step.
DH wrapper contract
Resolve the feature's acceptance criteria and required artifacts through DH plan/backlog/artifact operations supplied by the dispatch. Run post-implementation verification only; do not repair implementation.
Translate the skill result to the DH workflow verdict:
- every required outcome demonstrated:
VERIFIED; - any demonstrated unmet outcome:
GAPS_FOUND; - required evidence unavailable: preserve it as unverified and do not report VERIFIED.
Register or append findings only through the artifact/backlog operation required by the invoking DH workflow. Return the required DH STATUS envelope and artifact identifiers; do not persist reports to private state paths.
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.
- 28d ago Changed · -488 lines a76ef80583c2
- 1mo ago Changed · -14 lines 8ed3f633e132
- 1mo ago Changed 97c01902954b
- 1mo ago First seen · 532 lines · 49 tokens per session scan A c64848a1a78c
feature-verifier is an agent published in the GitHub repository Jamie-BitFlight/claude_skills (67 stars, last pushed 4d ago), licensed MIT. It adds 49 tokens to every session and 347 once invoked, about $0.0002 per session on Opus 5.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
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.