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/AmirSoleimani/claude-stashWrote 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/amirsoleimani/claude-stash/drop)<a href="https://agentmods.dev/commands/amirsoleimani/claude-stash/drop"><img src="https://agentmods.dev/badge/commands/amirsoleimani/claude-stash/drop.svg" alt="Measured on agentmods" 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.00008 | $0.00273 |
| Opus 5 | $0.00004 | $0.00137 |
| Sonnet 5 | $0.00002 | $0.00055 |
| Haiku 4.5 | $0.00001 | $0.00027 |
Grade A, and why
drop 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 6d 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
Delete an item from .claude/stash.md without acting on it. The removal is logged for historical reference.
Steps:
-
Read
.claude/stash.md. If empty or missing, respond:Stash is empty.and stop. -
Parse
$ARGUMENTSas a positive integerN. If missing or invalid, respond:Usage: /stash:drop Nand stop. -
Find the item at position
N(1-indexed across-lines). If out of range, respond with the current count and stop. -
Capture the line's content and parse the item text.
-
Remove the line from
.claude/stash.md. Save. -
Append a log entry to
.claude/stash.log.md. Create the file with header# Stash logif missing. Then append:- [YYYY-MM-DD HH:MM] DROPPED <item text>(Use today's date and current time, 24h, local.)
-
Respond:
Dropped: <item text> (N items remaining)
Do not start working on the item. This is the explicit "skip this" path.
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.
- 6d ago First seen · 32 lines · 8 tokens per session scan A edfc8f58b320
drop is a command published in the GitHub repository AmirSoleimani/claude-stash (10 stars, last pushed 3mo ago), licensed MIT. It adds 8 tokens to every session and 273 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-31.
Other commands, from other repositories
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
changelog
Generate a changelog entry from git commits since the last tag using conventional commit format.
deploy
Deploy application with pre/post-deploy checks.
auto-claude
Invoke Auto-Claude autonomous coding framework for complex feature implementation.
versioning
Universal version file discovery and sync. Works with any project structure.
merge
You are executing the /hydra:merge command. Merge a worktree branch back into the current branch.