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.
npx agentmods add commands/biznuts/never-stale/removegit clone --depth 1 https://github.com/biznuts/never-staleWhat 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 | $0.00077 | $0.01251 |
| Opus 5 | $0.00039 | $0.00626 |
| Sonnet 5 | $0.00015 | $0.00250 |
| Haiku 4.5 | $0.00008 | $0.00125 |
Grade A, and why
remove 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 2d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
never-stale — remove it from this project
Inverse of /never-stale:setup: remove never-stale's footprint from this project and
nothing else. This is the destructive verb — it deletes the marker and strips the
CLAUDE.md rules block.
Just want to silence the reminders for a while? Use
/never-stale:offinstead — it pauses without deleting anything, and/never-stale:onbrings it back.
Project root = the path in $ARGUMENTS (ignoring any flag) if given, else the
current working directory. Call it <ROOT>.
Dry-run. If $ARGUMENTS contains --dry-run, only print the removal plan, then
STOP without removing anything.
Safety contract. Remove ONLY never-stale's own artifacts. The marker is 100%
never-stale-owned (no user prose) so it is always safe to delete. For CLAUDE.md,
remove by sentinel fence, never by guessing boundaries. Never touch foreign
hooks, the user's own CLAUDE.md prose outside the fence, other settings, or
settings.local.json (read it for awareness, never modify it). Show a plan and get
confirmation before removing anything.
Step 1 — Detect never-stale's artifacts
- Marker(s) —
<ROOT>/.claude/never-stale.jsonand/or<ROOT>/.claude/never-stale.local.jsonpresent → REMOVE (delete file). Path- based, always reliable, no content matching. If alocalmarker was gitignored, also offer to remove its.gitignoreline. - CLAUDE.md fence — locate the
<!-- never-stale:begin … -->/<!-- never-stale:end -->pair:- well-formed pair → REMOVE the whole span (including the sentinels and one trailing blank line), regardless of how the body was edited. If the body hash no longer matches the hash in the begin sentinel, note "you edited this since scaffold — removing discards your edits" and offer a Keep option, but never let an edit block removal.
- begin without a matching end (or end without begin) → remove nothing; flag "malformed never-stale block — manual review" with the line number. Never guess a boundary.
- multiple well-formed pairs (a botched double-run) → remove each; flag any unmatched sentinel.
- nested / overlapping sentinels → refuse and flag.
- Legacy v0.5.0 residue —
<ROOT>/.claude/hooks/never-stale-reminder.jsand anysettings.jsonhook whosecommandcontainsnever-stale-reminder.js→ plan to REMOVE (migration teardown).settings.local.jsonis never edited; flag a legacy hook there for manual removal.
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.
- 2d ago First seen · 93 lines · 0 tokens per session scan A 1d5ca42bd30d
remove is a command published in the GitHub repository biznuts/never-stale (2 stars, last pushed 1mo ago), licensed MIT. It adds 77 tokens to every session and 1,251 once invoked, about $0.0004 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.