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/TheMrGU/Ai-Agent-Context-PassoffWrote 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/themrgu/ai-agent-context-passoff/list)<a href="https://agentmods.dev/commands/themrgu/ai-agent-context-passoff/list"><img src="https://agentmods.dev/badge/commands/themrgu/ai-agent-context-passoff/list/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/themrgu/ai-agent-context-passoff/list"><img src="https://agentmods.dev/badge/commands/themrgu/ai-agent-context-passoff/list.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.00019 | $0.00274 |
| Opus 5.5 | $0.00008 | $0.00110 |
| Sonnet 5.5 | $0.00004 | $0.00055 |
| Haiku 4.5 | $0.00002 | $0.00027 |
Grade A, and why
list 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.
What it actually says
Passoff List
Browse recent handoffs using the configured passoff_* MCP tools.
Preflight
- Confirm the passoff MCP tools are available in this session.
- Inspect any inline argument: a status filter (open, loaded, archived, all) or a project slug.
Plan
- Call
passoff_list. Default returns the 10 most recent handoffs in the current project across all statuses. - Pass
statusorprojectonly if the user named one. - Render the result so the user can choose what to load.
Commands
Call the passoff_list MCP tool with optional status, project, and limit.
Verification
- Confirm the tool call succeeded.
- If no handoffs match, state that explicitly and suggest creating one with
/passoff:createor loading the latest cross-project with/passoff:load.
Summary
For each row, show: id, title, status, from_client → to_client, and relative created_at.
Next Steps
- Do not auto-load any handoff. Wait for the user to pick one, then continue with
/passoff:loadusing the chosen id.
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 · 36 lines · 19 tokens per session scan A 98964b7382d4
list is a command published in the GitHub repository TheMrGU/Ai-Agent-Context-Passoff (0 stars, last pushed 5mo ago), licensed MIT. It adds 19 tokens to every session and 274 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-31.
Other commands, from other repositories
status
Display project status, active tracks, and next actions.
ijfw-status
Show IJFW state -- mode, routing, memory, recent activity, codebase index, settings. Use when you want the at-a-glance banner you'd otherwise get at session start.
prp-prd
Interactive PRD generator - problem-first, hypothesis-driven product spec with back-and-forth questioning.
pm-done
Close a todo (TODO-xxx), sync completed.md, refresh overview.
test-management
Organize, classify, and trace Katalon True Platform/TestOps test assets. Use when you need to structure test cases into folders and suites, move or reorganize cases, search and find existing assets at scale, link or unlink requirements to test cases, or produce a requirement-to-test traceability report (which…
feedback
Review comments on your display.dev artifacts, then apply them, reply, and resolve the threads after you approve.