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/skill-inspectorWrote 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/skill-inspector/verifier)<a href="https://agentmods.dev/agents/yu-iskw/skill-inspector/verifier"><img src="https://agentmods.dev/badge/agents/yu-iskw/skill-inspector/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/skill-inspector/verifier"><img src="https://agentmods.dev/badge/agents/yu-iskw/skill-inspector/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.00261 |
| Opus 5.5 | $0.00010 | $0.00104 |
| Sonnet 5.5 | $0.00005 | $0.00052 |
| Haiku 4.5 | $0.00003 | $0.00026 |
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- verifier — 89% identical, 12 lines differ
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, 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. - Test: Run the
test-and-fixskill loop. Ensure all unit tests pass.
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)
- Test status (Passed/Fixed/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 · 29 lines · 26 tokens per session scan A 7a92aa0ecf2c
verifier is an agent published in the GitHub repository yu-iskw/skill-inspector (2 stars, last pushed 20d ago), licensed Apache-2.0. It adds 26 tokens to every session and 261 once invoked, about $0.0001 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-08-31.
Other agents, from other repositories
ezra
DevTeam QA Engineer that writes test suites, validates acceptance criteria, runs integration tests, and reports bugs. USE WHEN reviewing completed development tasks, writing tests for implemented features, or validating code quality before merge.
fix-verifier
Delegates to this agent when the user wants to retest a vulnerability after a fix has been deployed, prove that a remediation actually closed the issue, verify a patch before closing a finding or a bug bounty report, check whether a fix broke working functionality, or confirm that a security regression has not…
Reality Checker
Stops fantasy approvals, evidence-based certification - Default to "NEEDS WORK", requires overwhelming proof for production readiness.
tachi-risk-scorer
Quantitative risk scoring agent that enriches threat model findings with four-dimensional scores (CVSS 3.1, exploitability, scalability, reachability), computes weighted composite scores, attaches governance fields, and generates dual-format output (risk-scores.md and risk-scores.sarif).
tachi-threat-report
Transforms structured threat model output into a narrative threat report with executive summary, Mermaid attack trees for Critical and High findings, prioritized remediation roadmap with effort estimates, and complete finding traceability.
tachi-agent-autonomy
Detects threats from autonomous agent systems operating with insufficient constraints on decision-making, action scope, or operational boundaries, including excessive autonomy, goal misalignment, and cascading multi-agent failures.