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/danielraffel/generous-corp-marketplaceWrote 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/danielraffel/generous-corp-marketplace/repair)<a href="https://agentmods.dev/commands/danielraffel/generous-corp-marketplace/repair"><img src="https://agentmods.dev/badge/commands/danielraffel/generous-corp-marketplace/repair/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/danielraffel/generous-corp-marketplace/repair"><img src="https://agentmods.dev/badge/commands/danielraffel/generous-corp-marketplace/repair.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.00006 | $0.00387 |
| Opus 5 | $0.00003 | $0.00193 |
| Sonnet 5 | $0.00001 | $0.00077 |
| Haiku 4.5 | $0.00001 | $0.00039 |
Grade A, and why
repair 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
Worktree Repair Command
Repair broken or corrupted worktree administrative files.
Usage
/worktree-manager:repair <worktree-path>
Instructions for Claude
When user invokes this command:
-
Parse arguments:
- Extract worktree path (required)
-
Call MCP tool:
- Use
mcp__worktree__worktree_repair - Pass
worktree_path
- Use
-
Display results:
- Show repair status:
- ✅ Worktree repaired:
- Explain that administrative files have been updated
- Suggest verifying with /worktree-manager:status
- Show repair status:
-
Error handling:
- Worktree doesn't exist → suggest using /worktree-manager:list
- Not broken → inform user worktree is already functional
- Permission errors → explain and suggest solutions
Examples
Repair worktree:
User: /worktree-manager:repair ~/worktrees/broken-feature
Claude: ✅ Worktree repaired: ~/worktrees/broken-feature
Administrative files have been updated
Verify with: /worktree-manager:status ~/worktrees/broken-feature
When to Use
Use this command when:
- Worktree was manually moved and git references broke
- Parent repository was moved
.gitfile is corrupted or has wrong paths- Git commands fail with "not a git repository" in a known worktree
- After manually copying/moving the parent repository
What It Does
Repairs the connection between:
- Worktree
.gitfile → Parent repository - Parent repository → Worktree location
- Updates all internal path references
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 · 65 lines · 6 tokens per session scan A 35e81e3543d6
repair is a command published in the GitHub repository danielraffel/generous-corp-marketplace (11 stars, last pushed 11d ago), licensed MIT. It adds 6 tokens to every session and 387 once invoked, about $0.0000 per session on Opus 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-30.
Other commands, from other repositories
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
handoff
Export a Waybill Bundle by default, or import one when requested.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.