requirement-checker

requirement-checker is an agent for Claude Code from alphaelements/handoff-mcp. It costs 55 tokens per session (2,231 once invoked), scanned A, original, MIT.

A read-only checker for one requirements document. It compares each requirement and the set as a whole with recognised quality rules, including ISO standards, then returns findings and a PASS or REDO verdict.

In plain words
What is it for?
Use it to inspect a single requirements document and report quality problems and missing coverage. ISO/IEC/IEEE 29148 is a standard for writing and managing requirements; ISO/IEC 25010 describes software quality characteristics.
Why use it?
It helps find unclear, incomplete, or poorly formed requirements before they reach design or development. It does not change the document.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter; names the TodoWrite tool.

Part of the handoff-task-loop plugin — 1 skill, 4 commands, 16 agents shipped together

Good fit Use it to inspect a single requirements document and report quality problems and missing coverage. ISO/IEC/IEEE 29148 is a standard for writing and managing requirements; ISO/IEC 25010 describes software quality characteristics.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/alphaelements/handoff-mcp/requirement-checker
Install

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.

Clone the repo
git clone --depth 1 https://github.com/alphaelements/handoff-mcp

Made for: Claude Code.

Or install handoff-task-loop, the plugin that ships this one along with the rest of its 1 skill, 4 commands, 16 agents.

Wrote 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.

agentmods badge for requirement-checker

README.md
[![agentmods](https://agentmods.dev/badge/agents/alphaelements/handoff-mcp/requirement-checker/github.svg)](https://agentmods.dev/agents/alphaelements/handoff-mcp/requirement-checker)
Your own site
<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.

agentmods 80×15 button for requirement-checker

Your own site · 80×15
<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>
Per session 55 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,231 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured yesterday against content hash 883d6d75a753, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

plugin-task-loop/agents/requirement-checker.md · 194 lines

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 a REDO.
  • 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_types selects which checks to run. Omitted = all three. Unknown values: report a MINOR finding 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.

Read the full file on GitHub · 194 lines

Changes

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.

  1. yesterday First seen · 194 lines · 55 tokens per session scan A 883d6d75a753

Subscribe to this mod's changes

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.