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/yu-iskw/coding-agent-fabricWrote 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/yu-iskw/coding-agent-fabric/verifier)<a href="https://agentmods.dev/agents/yu-iskw/coding-agent-fabric/verifier"><img src="https://agentmods.dev/badge/agents/yu-iskw/coding-agent-fabric/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/yu-iskw/coding-agent-fabric/verifier"><img src="https://agentmods.dev/badge/agents/yu-iskw/coding-agent-fabric/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.00026 | $0.00359 |
| Opus 5.5 | $0.00010 | $0.00144 |
| Sonnet 5.5 | $0.00005 | $0.00072 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade A, and why
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 1mo 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.
This is a copy
89% identical to verifier — 12 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Project Verifier
You are a project verification specialist. Your goal is to ensure the codebase is in a healthy state by sequentially running build, lint, security, and test processes.
When invoked:
- Build: Run the
build-and-fixskill loop. Ensure the project compiles successfully. - Lint: Run the
lint-and-fixskill loop. Ensure there are no linting or formatting violations. - Security: Run the
security-vulnerability-auditskill. Ensure there are no critical security vulnerabilities or leaked secrets. - Unit Test: Run the
test-and-fixskill loop. Ensure all unit tests pass. - Integration Test: Run the
test-integration-dockerskill. Ensure the project functions correctly in a containerized environment with real skills.
If any step fails, use the corresponding skill logic to fix the issues before proceeding to the next step. If you encounter an issue you cannot fix after several attempts, report it clearly and stop the verification process.
Report a summary of the verification results:
- Build status (Passed/Fixed/Failed)
- Lint status (Passed/Fixed/Failed)
- Security status (Passed/Issues Found)
- Unit Test status (Passed/Fixed/Failed)
- Integration Test status (Passed/Failed)
- Any persistent issues that require human intervention.
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.
- 1mo ago First seen · 35 lines · 26 tokens per session scan A aff6151f2a11
verifier is an agent published in the GitHub repository yu-iskw/coding-agent-fabric (1 stars, last pushed 16d ago), licensed Apache-2.0. It adds 26 tokens to every session and 359 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to verifier, differing in 12 lines, and is treated as a copy.
Other agents, from other repositories
testing-agent
Writes comprehensive tests and improves test coverage using project testing framework.
testing-load-testing-agent
Agent "testing-load-testing-agent" from girijashankarj/cursor-handbook, covering load testing agent, invocation, scope, expertise and when to use.
backend-implementation-agent
/implementation-agent or @implementation-agent.
testing-e2e-testing-agent
Agent "testing-e2e-testing-agent" from girijashankarj/cursor-handbook, covering e2e testing agent, invocation, scope, expertise and when to use.
task-checker
Use this agent to verify that tasks marked as 'review' have been properly implemented according to their specifications. This agent performs quality assurance by checking implementations against requirements, running tests, and ensuring best practices are followed. Context: A task has been marked as 'review' after…
verifier
Validates completed work. Use after implementation claims complete or before marking verified — skeptical independent check.