Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add johardi/claude-stack/plugin install cstack-collabWrote 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/skills/johardi/claude-stack/reclaim)<a href="https://agentmods.dev/skills/johardi/claude-stack/reclaim"><img src="https://agentmods.dev/badge/skills/johardi/claude-stack/reclaim/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/skills/johardi/claude-stack/reclaim"><img src="https://agentmods.dev/badge/skills/johardi/claude-stack/reclaim.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.00157 | $0.01074 |
| Opus 5.5 | $0.00063 | $0.00430 |
| Sonnet 5.5 | $0.00031 | $0.00215 |
| Haiku 4.5 | $0.00016 | $0.00107 |
Grade A, and why
reclaim 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reclaim
The complement to handoff. Where handoff is collaborative (live agent yields branch), reclaim is unilateral (human takes branch back without — or against — the agent's cooperation). Run from the primary repo, not from inside a worktree.
When to Use
Use when:
- The user types
/cstack-collab:reclaim <branch-or-agent-id>with optional flags. - The user describes a stuck agent worktree: "the agent crashed", "the worktree is locked but the session is dead", "I can't check out feature/X — git says it's used by another worktree".
- An orchestrate-tickets wave left an agent worktree behind that needs to be cleaned up before the next wave.
Skip when:
- The agent is alive and reachable. Tell the user to type
/cstack-collab:handoffin the agent's session instead — handoff preserves the agent's context and lets it write a meaningful commit message. Reclaim is the rescue tool, not the default. - The user just wants to list what's stuck — that's
/cstack-collab:list-worktrees.
Inputs
| Argument | Meaning |
|---|---|
<ref> (positional, required) |
Branch name (feature/66-x), agent id (agent-a81ac7c0…), or absolute path to the worktree. |
--force |
Remove even when the agent's PID is still alive. Kills the live agent's session. Only pass when the user has explicitly acknowledged this — e.g., "the agent is wedged, just kill it". |
--stash |
(default) preserve dirty state at refs/cstack-collab/reclaim/<agent-id>. |
--discard |
Throw the dirty state away. |
--checkout |
After removal, run git checkout <branch> in the primary repo. |
How to Run
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/reclaim.py" <ref> [flags]
The script:
- Locates the agent worktree. Refuses if the ref doesn't match exactly one.
- Refuses if the agent's PID is alive, unless
--forcewas passed. - Stashes any dirty state to
refs/cstack-collab/reclaim/<id>(unless--discard). The ref points at a real commit object, so it survivesgit worktree remove— recover withgit stash apply <ref>orgit cherry-pick <ref>. git worktree unlock+git worktree remove [--force].- Optional
git checkout <branch>in the primary repo. - Appends a
reclaimedevent tostate.jsonif an orchestration is active.
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 · 67 lines · 157 tokens per session scan A ff273e416a34
reclaim is a skill published in the GitHub repository johardi/claude-stack (2 stars, last pushed 5mo ago), licensed MIT. It adds 157 tokens to every session and 1,074 once invoked, about $0.0006 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 skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.