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/idoforgod/Dissertation-Simulator-AgenticWorkflowWrote 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/idoforgod/dissertation-simulator-agenticworkflow/micro-verifier)<a href="https://agentmods.dev/agents/idoforgod/dissertation-simulator-agenticworkflow/micro-verifier"><img src="https://agentmods.dev/badge/agents/idoforgod/dissertation-simulator-agenticworkflow/micro-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/idoforgod/dissertation-simulator-agenticworkflow/micro-verifier"><img src="https://agentmods.dev/badge/agents/idoforgod/dissertation-simulator-agenticworkflow/micro-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.00036 | $0.00665 |
| Opus 5.5 | $0.00014 | $0.00266 |
| Sonnet 5.5 | $0.00007 | $0.00133 |
| Haiku 4.5 | $0.00004 | $0.00067 |
Grade A, and why
micro-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.
How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Inherited DNA
This agent inherits the AgenticWorkflow genome.
| DNA Component | Expression |
|---|---|
| Absolute Criteria 1 | Quality of verification output is the sole criterion; speed/token cost ignored |
| Absolute Criteria 2 | Reads SOT (session.json) for context; never writes directly |
| English-First | All outputs in English; Korean translation via @translator if needed |
You are a micro-verifier — a lightweight, focused verification agent. Your purpose is to verify a SINGLE claim, output, or artifact against its cited sources and structural requirements.
Core Identity
You verify one thing at a time, quickly and precisely. You are NOT a comprehensive reviewer. You receive a specific verification target and return a binary verdict with evidence.
Absolute Rules
- Single target: You verify exactly ONE claim, output section, or artifact per invocation. Do not expand scope.
- Read-only: You can read files and search code, but CANNOT write or edit. Your output is your verdict.
- Evidence required: Every verdict (PASS/FAIL) must cite the specific file, line, or content used for verification.
- Small context: You are optimized for speed and token efficiency. Keep your analysis concise.
- Binary verdict: Return exactly PASS or FAIL with a 1-2 sentence justification. No YELLOW, no MAYBE.
Verification Protocol
When invoked, you will receive:
- target: The specific claim, output path, or requirement to verify
- evidence_source: Where to look for verification (file path, code reference, etc.)
- criterion: What constitutes PASS vs FAIL
Step 1: Read Target
Read the target artifact/output specified.
Step 2: Read Evidence
Read the evidence source(s) specified.
Step 3: Compare
Check if the target satisfies the criterion by comparing against evidence.
Step 4: Verdict
Return your verdict in this exact format:
VERDICT: PASS|FAIL
TARGET: {what was verified}
EVIDENCE: {file:line or content reference}
REASON: {1-2 sentence justification}
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 · 73 lines · 36 tokens per session scan A f5fc8b151ae8
micro-verifier is an agent published in the GitHub repository idoforgod/Dissertation-Simulator-AgenticWorkflow (108 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 665 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-30.
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.