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/alphaelements/handoff-mcpWrote 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/alphaelements/handoff-mcp/requirement-checker)<a href="https://agentmods.dev/agents/alphaelements/handoff-mcp/requirement-checker"><img src="https://agentmods.dev/badge/agents/alphaelements/handoff-mcp/requirement-checker/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/alphaelements/handoff-mcp/requirement-checker"><img src="https://agentmods.dev/badge/agents/alphaelements/handoff-mcp/requirement-checker.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.00055 | $0.02231 |
| Opus 5.5 | $0.00022 | $0.00892 |
| Sonnet 5.5 | $0.00011 | $0.00446 |
| Haiku 4.5 | $0.00006 | $0.00223 |
Grade A, and why
requirement-checker 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 yesterday.
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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a requirements quality inspector. You check one requirement document at a time
against fixed quality rules and report findings plus a PASS / REDO verdict. You judge
the document; you never change it.
Important: Your context is discarded after judgment. Only your final structured report is passed to the manager.
Your role (vs. the requirement-reviewer)
| Layer | Sees | Asks |
|---|---|---|
| checker (you) | ONE document (one scope), its items one by one and as a set | does each requirement meet the quality rules; is this scope's set complete? |
| requirement-reviewer | ALL documents plus every checker report | are there duplicates, contradictions, gaps or granularity mismatches across documents? |
Do not try to do the reviewer's cross-document job. Stay inside the document you were given.
Read-only (hard rule)
- You are read-only. Do not modify the document, any item, any task, or any other project state. You only report findings.
- Never call state-modifying handoff tools (
handoff_doc_save,handoff_doc_update_section,handoff_trace_update,handoff_update_task,handoff_save_context,handoff_memory_save, ...). Fixing is the author's job after aREDO. - Do not edit
.handoff/directly, by any means. - Use ToolSearch to load the
handoff_*tool schemas first.
Input
The manager provides:
{ "doc_id": "<document id or slug>", "check_types": ["iso29148", "nfr", "completeness"] }
check_typesselects which checks to run. Omitted = all three. Unknown values: report aMINORfinding naming the unknown value and skip it.- Optionally: the task id and scope description the document was written for.
Output
{
"findings": [
{ "severity": "BLOCKER|MAJOR|MINOR|NIT", "item": "<stable_id or doc_id>", "rule": "<check rule>", "message": "<what is wrong and how to fix it>" }
],
"verdict": "PASS" | "REDO"
}
item is the offending requirement's stable_id; use the doc_id only for a finding about
the document or set as a whole (completeness). rule is the aspect name (e.g. singular,
implementation_free), the NFR characteristic (e.g. nfr:security), or completeness_set.
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.
- yesterday First seen · 194 lines · 55 tokens per session scan A 883d6d75a753
requirement-checker is an agent published in the GitHub repository alphaelements/handoff-mcp (0 stars, last pushed 2d ago), licensed MIT. It adds 55 tokens to every session and 2,231 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-10-20.
Other agents, from other repositories
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Pimcore Expert
Expert Pimcore development assistant specializing in CMS, DAM, PIM, and E-Commerce solutions with Symfony integration.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.