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 skills/jerry0022/dotclaude/stale-changes-checknpx skills add Jerry0022/dotclaude --skill stale-changes-checkgit clone --depth 1 https://github.com/Jerry0022/dotclaudeWrote 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/jerry0022/dotclaude/stale-changes-check)<a href="https://agentmods.dev/skills/jerry0022/dotclaude/stale-changes-check"><img src="https://agentmods.dev/badge/skills/jerry0022/dotclaude/stale-changes-check.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.00028 | $0.00393 |
| Opus 5 | $0.00014 | $0.00197 |
| Sonnet 5 | $0.00006 | $0.00079 |
| Haiku 4.5 | $0.00003 | $0.00039 |
Grade A, and why
stale-changes-check 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 5d 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
Stale Changes Check
Runs automatically at every session start via hooks/session-start/ss.git.check.js.
Silent when everything is clean. Only surfaces a brief warning when issues are found.
What the hook checks
git status --porcelain— uncommitted changesgit log --branches --not --remotes --oneline— unpushed commitsgit stash list— stash entries
Always checks the current working directory. Optionally checks additional repos
defined in ~/.claude/scheduled-tasks/stale-changes-check/reference.md:
## Repos to monitor
- ~/IdeaProjects/my-app
- ~/IdeaProjects/my-other-app
Output behaviour
- Clean → hook exits silently, nothing shown to user.
- Issues found → hook writes a structured summary to stdout; Claude relays a brief inline warning to the user (no full report, no table).
Findings are never coupled to a question. The hook always emits them and
instructs the assistant to restate them in its final message, before any
completion card. When a workspace issue is also present, the AskUserQuestion
block is layered on top — so an interactive session asks, while a scheduled,
cron or headless session (which cannot answer a modal) still reports what was
found instead of dropping it with the skipped question. See
hooks/lib/git-check-output.js.
Constraints
- Read-only — hook never makes any git changes
- No cron registration — this is a direct SessionStart hook, not a scheduled task
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.
- 5d ago First seen · 46 lines · 28 tokens per session scan A 511e94cce6ec
stale-changes-check is a skill published in the GitHub repository Jerry0022/dotclaude (5 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 393 once invoked, about $0.0001 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…