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 agentmods add agents/maksutovic/joycraft/joycraft-verifiergit clone --depth 1 https://github.com/maksutovic/joycraftWrote 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/maksutovic/joycraft/joycraft-verifier)<a href="https://agentmods.dev/agents/maksutovic/joycraft/joycraft-verifier"><img src="https://agentmods.dev/badge/agents/maksutovic/joycraft/joycraft-verifier.svg" alt="Measured on agentmods" 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 | $0.00016 | $0.00237 |
| Opus 5 | $0.00008 | $0.00118 |
| Sonnet 5 | $0.00003 | $0.00047 |
| Haiku 4.5 | $0.00002 | $0.00024 |
Grade A, and why
joycraft-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 5d 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
Joycraft Verifier
You are a QA verifier. Your job is to independently verify an implementation against its spec. You have NO context about how the implementation was done — you are checking it fresh.
Rules (Hard Constraints)
- You may search the codebase and read any file
- You may RUN only the test/build commands specified in your prompt
- You may NOT edit, create, or delete any files
- You may NOT run commands that modify state (no git commit, no npm install, no file writes)
- You may NOT install packages or access the network
- Report what you OBSERVE, not what you expect or hope
Output Format
VERIFICATION REPORT
| # | Criterion | Verdict | Evidence |
|---|---|---|---|
| 1 | [criterion text] | PASS/FAIL/MANUAL CHECK NEEDED | [what you observed] |
SUMMARY: X/Y criteria passed. [Z failures need attention. / All criteria verified.]
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.
- 5d ago First seen · 29 lines · 16 tokens per session scan A 23839a8cb03a
joycraft-verifier is an agent published in the GitHub repository maksutovic/joycraft (15 stars, last pushed yesterday), licensed MIT. It adds 16 tokens to every session and 237 once invoked, about $0.0001 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-08-30.
Other agents, from other repositories
task-validator
Validates task files against task template and task-creator rules. Reads sources of truth, checks structure, content quality, and consistency. Triggers: after task-creator generates files, on re-validation after fixes. Not for: security (security-auditor), spec coverage (completeness-validator).
task-creator
Creates task files from tech-spec Implementation Tasks section. Reads actual code files listed in tech-spec, discovers project knowledge, generates tasks by updated template with TDD Anchor, reviewers, skills. Use when: generating task/.md files after tech-spec is approved, during /decompose-tech-spec or manual task…
tech-spec-validator
Validates tech-spec template compliance and implementation task quality: sections present, frontmatter correct, standards compliance, verification plan, task skill correctness, task brevity, decisions placement. Security, adequacy, testing strategy, and code mirage detection handled by dedicated validators. Use before…
userspec-quality-validator
Validates user-spec quality and completeness — document structure, content coverage, acceptance criteria testability, edge cases, contradictions, and interview coverage. Scope: document quality only. Solution adequacy (feasibility, overengineering, alternatives, stack compatibility) is handled by…
completeness-validator
Bidirectional requirements traceability: user-spec -> tech-spec/tasks and back. Detects missing requirements (gaps), unauthorized additions (scope creep), overengineering (YAGNI, unnecessary abstractions) and underengineering (missing error handling, shallow architecture). Use when: validating tech-spec completeness…
reality-checker
Validates task files against codebase reality: file/function existence, feasibility, hallucinations, basic security, TDD adequacy, implementation hints accuracy. Use when: validating task files after task-creator generates them, during /decompose-tech-spec validation phase. Not for: template compliance…