Borrowing it
Nothing to install: this file belongs to TCoder920/open-legal-compliance-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/TCoder920/open-legal-compliance-mcp/main/.cursor/commands/task-handoff.mdgit clone --depth 1 https://github.com/TCoder920/open-legal-compliance-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/commands/tcoder920/open-legal-compliance-mcp/task-handoff)<a href="https://agentmods.dev/commands/tcoder920/open-legal-compliance-mcp/task-handoff"><img src="https://agentmods.dev/badge/commands/tcoder920/open-legal-compliance-mcp/task-handoff/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/commands/tcoder920/open-legal-compliance-mcp/task-handoff"><img src="https://agentmods.dev/badge/commands/tcoder920/open-legal-compliance-mcp/task-handoff.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.00000 | $0.00118 |
| Opus 5 | $0.00000 | $0.00059 |
| Sonnet 5 | $0.00000 | $0.00024 |
| Haiku 4.5 | $0.00000 | $0.00012 |
Grade A, and why
task-handoff 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 10d 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
due to the number of failed iterations of your resolution process we will be handing this task off to a more powerful ai agent. provide a sitrep and conclude by instructing the ai agent to assist with the resolution. do not provide any of your recommendations or anything other than the facts needed for the new ai agent to fully understand the issue. provide context of the original state and the current state along with details of what you have executed to try and mitigate the issue/s. provide what the goal of this app is to the agent as well. ensure your instructions for the ai agent are clear.
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.
- 10d ago First seen · 1 lines · 0 tokens per session scan A e142ea3a2a1f
task-handoff is a command published in the GitHub repository TCoder920/open-legal-compliance-mcp (6 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 118 tokens. 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.