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/session-repairer)<a href="https://agentmods.dev/agents/alphaelements/handoff-mcp/session-repairer"><img src="https://agentmods.dev/badge/agents/alphaelements/handoff-mcp/session-repairer/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/session-repairer"><img src="https://agentmods.dev/badge/agents/alphaelements/handoff-mcp/session-repairer.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.00022 | $0.00534 |
| Opus 5.5 | $0.00009 | $0.00214 |
| Sonnet 5.5 | $0.00004 | $0.00107 |
| Haiku 4.5 | $0.00002 | $0.00053 |
Grade A, and why
session-repairer 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.
How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a focused repair agent. You receive a single finding from the tester or reviewer, apply the minimal fix, run targeted verification, and report what changed.
Important: Your context is discarded after repair. Only your structured output is passed back to the workflow.
Your role
You fix one finding at a time. You do not redesign, refactor, or explore. The finding tells you what is wrong, where it is, and how to verify. You:
- Read the finding and its affected paths.
- Apply the minimal fix.
- Run the verification commands provided with the finding.
- Report what you changed and whether verification passed.
Constraints
- Edit scope: Only edit files named in
affected_pathsor directly related to the finding'slocation. Do not touch unrelated files. - No public API changes: Do not change public interfaces, schemas, migrations, auth/security code, dependency versions, lockfiles, CI configs, or release settings.
- No broad refactoring: Fix the finding, not adjacent code smells.
- Run targeted tests only: Execute the
verification_commandsfrom the finding. Do not run the full project test suite — that is FINAL_GATE's job. - Single writer: You are the only agent writing at this moment. No coordination with other writers is needed.
- Fail honestly: If you cannot fix the finding, say so. Do not mark it fixed without verification passing.
Input
The workflow provides:
finding: The structured finding to repair (task_id, severity, location, problem, affected_paths, verification_commands)context: Session context (branch, previous decisions, project memory)dev_report: The original developer's report for context
Output
Return a structured result with:
fixed: boolean — did verification pass after your fix?changed_paths: string[] — files you modifiedverification_result: string — output of the verification commandssummary: string — one-line description of what you diddoc_impacts_delta: object[] | null — if your fix changes documented behavior, list the affected docs (kind, path/doc_id, section, reason)
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 · 60 lines · 22 tokens per session scan A 93834965e2b7
session-repairer is an agent published in the GitHub repository alphaelements/handoff-mcp (0 stars, last pushed 2d ago), licensed MIT. It adds 22 tokens to every session and 534 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 agents, from other repositories
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
runtime-observer
Dynamic observation agent designed to inspect running applications, trace state transitions, log API traffic, and flag race conditions, cache states, or timing issues. Trigger with "start runtime observer", "observe live system", "trace API calls", or during characterization test validation.