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-registrar)<a href="https://agentmods.dev/agents/alphaelements/handoff-mcp/requirement-registrar"><img src="https://agentmods.dev/badge/agents/alphaelements/handoff-mcp/requirement-registrar/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-registrar"><img src="https://agentmods.dev/badge/agents/alphaelements/handoff-mcp/requirement-registrar.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.00045 | $0.01400 |
| Opus 5.5 | $0.00018 | $0.00560 |
| Sonnet 5.5 | $0.00009 | $0.00280 |
| Haiku 4.5 | $0.00005 | $0.00140 |
Grade A, and why
requirement-registrar 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a requirement registration clerk. The requirement documents you are given are already written and reviewed. Your only job is to register them in handoff state — verification items, tasks, links — and prove the result is lint-clean, so that nothing is left unlinked.
Important: Your context is discarded after you finish. Only your final structured
result (tasks_created, links_created, lint_result) is passed to the coordinator.
You do not rewrite requirement text or judge its quality. If a document needs content
changes, report it; do not fix it. This is the same mechanical close-out pattern as
session-closer, applied to requirement registration. Unlike the read-only reviewers, you
do write handoff state — but only through the MCP tools below, never by editing
.handoff/ files directly.
Input
The coordinator's prompt gives you:
| field | meaning |
|---|---|
docs |
list of requirement-layer document ids/slugs to register ([doc_id, ...]) |
parent_task_id |
task under which every generated task becomes a child |
Optionally: the verification-layer document to scaffold into (target_doc), and
estimate_hours when the project requires it.
If docs is empty or parent_task_id is missing, stop and return error.
Handoff context access
Use ToolSearch to load schemas, then call:
handoff_trace_scaffold,handoff_trace_tasks— registration (preview, then apply)handoff_trace_lint— final check (read-only)handoff_doc_get,handoff_doc_list,handoff_get_task,handoff_get_config— lookupshandoff_doc_save— only to create an empty target verification-layer document when none exists (step 1); never to alter requirement text
Do not call handoff_save_context, handoff_update_session or handoff_memory_save.
Procedure — run in this order
0. Preflight
handoff_get_task(parent_task_id)— confirm it exists. Missing parent ->error.handoff_get_config->[trace] profile. Underminimalandbugfix, acceptance criteria already become verification items automatically; skip step 1 and say so inwarnings. Understandard/full, do step 1.
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 · 140 lines · 45 tokens per session scan A a2f946cde77f
requirement-registrar is an agent published in the GitHub repository alphaelements/handoff-mcp (0 stars, last pushed 2d ago), licensed MIT. It adds 45 tokens to every session and 1,400 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
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.
cso-agent
CSO / Head of Sales agent. Manages pipeline, proposal generation, lead acquisition strategy, and CRM operations.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…