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/offgit 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.00063 | $0.01166 |
| Opus 5 | $0.00032 | $0.00583 |
| Sonnet 5 | $0.00013 | $0.00233 |
| Haiku 4.5 | $0.00006 | $0.00117 |
Grade A, and why
off 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
never-stale — pause this project (off)
off and /never-stale:on are a reversible toggle. off is the light switch:
it sets the governing marker's "enabled" to false, so the gate goes silent for new
sessions — but it keeps the marker file, your recorded spoken/written
languages, and the sentinel-fenced CLAUDE.md block. Nothing is deleted. To turn it
back on, run /never-stale:on (the languages come back exactly as they were).
Pausing is not removing. If you want the marker and the
CLAUDE.mdrules block gone, use/never-stale:removeinstead.
Project root = the path in $ARGUMENTS if given, else the current working
directory. Call it <ROOT>.
Step 1 — Find the governing marker
The gate resolves a project by walking up from the launch dir to the nearest
ancestor that carries a marker, bounded by the git repo root. Reproduce that walk to
find which marker governs <ROOT>:
- Start at
<ROOT>. At each directoryD, check forD/.claude/never-stale.local.jsonthenD/.claude/never-stale.json. - If either exists, that directory governs — stop here. (A
localmarker present atDoverrides ateammarker at the sameD.) - Otherwise, if
D/.gitexists, stop (the repo root bounds the walk — no marker). - Else go up to the parent and repeat, until a marker is found, a
.gitis hit, or the filesystem root is reached.
Read whichever marker(s) the governing directory carries. Call the governing
directory <GOV>.
Step 2 — Decide what to flip, then confirm
- No governing marker found → this project is not opted in, so there is nothing to
pause. Tell the user to run
/never-stale:setupto opt in, and stop. - Marker already
enabled: false→ already paused. Say so (and that/never-stale:onresumes it), and stop. - A
localmarker governs (<GOV>/.claude/never-stale.local.json) → flip that file's"enabled"tofalse. This is purely local; the repo is unaffected. Confirm with AskUserQuestion (Pause / Cancel), then apply. - Only a
teammarker governs (<GOV>/.claude/never-stale.json, no local at<GOV>) → editing the committed marker would, once committed, pause it for the whole team. Use AskUserQuestion to offer:- Pause just for me (recommended) — create a
localoverride at<GOV>: write<GOV>/.claude/never-stale.local.jsonwith"enabled": false(copyspoken/writtenfrom the team marker for reference), and ensure.claude/never-stale.local.jsonis gitignored (append to<GOV>/.gitignore, or create it). The committed team marker is untouched; a local marker overrides it, so the gate seesenabled: falseand stays silent — for this checkout only. - Pause for the whole team — set the committed
<GOV>/.claude/never-stale.json"enabled"tofalse. Warn that this only takes effect for teammates once it is committed and pulled. - Cancel — do nothing.
- Pause just for me (recommended) — create a
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 · 81 lines · 0 tokens per session scan A 2f036acfa71f
off is a command published in the GitHub repository biznuts/never-stale (2 stars, last pushed 1mo ago), licensed MIT. It adds 63 tokens to every session and 1,166 once invoked, about $0.0003 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.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.