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 skills add PaulRBerg/agent-skills --skill stale-comments-auditgit clone --depth 1 https://github.com/PaulRBerg/agent-skillsWrote 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/paulrberg/agent-skills/stale-comments-audit)<a href="https://agentmods.dev/skills/paulrberg/agent-skills/stale-comments-audit"><img src="https://agentmods.dev/badge/skills/paulrberg/agent-skills/stale-comments-audit/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/paulrberg/agent-skills/stale-comments-audit"><img src="https://agentmods.dev/badge/skills/paulrberg/agent-skills/stale-comments-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00032 | $0.01187 |
| Opus 5 | $0.00016 | $0.00593 |
| Sonnet 5 | $0.00006 | $0.00237 |
| Haiku 4.5 | $0.00003 | $0.00119 |
Grade A, and why
stale-comments-audit 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 11d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stale Comments Audit
Audit source comments against the code they describe, then fix every confirmed mismatch or source of noise in the same run. Limit edits to comments; never change executable code merely to make a comment true.
Scope
Accept zero or more file or directory paths. With no arguments, use the current repository root. Resolve every path from the current working directory and report any path that cannot be read.
Discover JavaScript, JSX, TypeScript, TSX, and Go source files. By default exclude:
- tests, testdata, fixtures, snapshots, and stories;
- generated, vendor, dependency, coverage, cache, and build-output directories;
- minified JavaScript and generated Go files.
An explicitly named test file or test directory overrides only the test exclusion. Generated, vendored, minified, and build-output files remain excluded unless the user explicitly requests them.
Use repository-aware discovery when available (git ls-files or rg --files) and preserve the user's path order. Do
not impose an arbitrary result cap.
Analysis
Split discovered files into non-overlapping batches of about ten. Delegate independent batches to read-only subagents when supported; otherwise inspect them directly. Continue useful work while delegated batches run.
For every line, block, and documentation comment, compare the claim with adjacent code, referenced symbols, callers, configuration, and relevant repository history when current code alone is inconclusive. Classify only clear findings:
STALE: describes behavior the code no longer has;ORPHANED: references a symbol, path, flag, or concept that no longer exists;MISLEADING: materially suggests behavior different from the implementation;REDUNDANT: merely narrates self-explanatory code and carries no intent, constraint, or context.
Do not report style preferences, imperfect wording, useful rationale, or uncertainty as findings.
Behavior-Bearing Go Comments
Treat these as part of program behavior or required documentation, not ordinary prose:
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 124 lines · 32 tokens per session scan A dd882b34f066
stale-comments-audit is a skill published in the GitHub repository PaulRBerg/agent-skills (70 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 1,187 once invoked, about $0.0002 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-30.
Other skills, from other repositories
no-bare-casts
Writing as in TypeScript or TSX production code, modifying a file that contains a bare as cast, silencing a type error with a cast, encountering as unknown as, or reviewing a cast site.
ax-go-gen
Use when writing Go code with github.com/ax-llm/ax/packages/go for AxGen programs, forward calls, indexed multi-sampling, result pickers, streaming, tools, assertions, traces, usage, and output parsing.
ax-go-llm
Use when writing Go code with github.com/ax-llm/ax/packages/go for using the generated Ax package, factory functions, package docs, examples, and API reference.
ax-go-audio
Use when writing Go code with github.com/ax-llm/ax/packages/go for audio input/output, OpenAI Responses audio mapping, realtime event folding, and generated package audio examples.
ax-go-agent-optimize
Use when writing Go code with github.com/ax-llm/ax/packages/go for agent optimization, verified agent-playbook evolution, evaluators, judges, optimizer artifacts, BootstrapFewShot, and GEPA.
go-concurrency-safety
L1 supplement - audits Go-specific concurrency hazards in node client code: map iteration non-determinism, goroutine leaks, mutex ordering, panic boundaries, context cancellation.