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/random6913/claude-code-superkit/comment-rot-analyzernpx skills add RaNDoM6913/claude-code-superkit --skill comment-rot-analyzergit clone --depth 1 https://github.com/RaNDoM6913/claude-code-superkitWhat 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.00023 | $0.00553 |
| Opus 5 | $0.00012 | $0.00277 |
| Sonnet 5 | $0.00005 | $0.00111 |
| Haiku 4.5 | $0.00002 | $0.00055 |
Grade A, and why
comment-rot-analyzer 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 yesterday.
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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Comment Rot Analyzer
Detect comments that no longer match the code they describe. Stale comments are worse than no comments -- they actively mislead developers.
Phase 0: Load Project Context
Read if exists:
AGENTS.mdorCLAUDE.md-- project conventions- Recent git log (
git log --oneline -10) -- understand recent changes
When to Use
- During the
review-orchestratorpipeline -- dispatched for any changed files - After major refactors -- comments likely stale
- Periodic codebase health check
Detection Checklist
1. Stale TODOs
Search for TODO/FIXME/HACK/XXX comments. For each:
- Is it older than 6 months? (check
git log -1 --format=%ai -- <file>) - Does the TODO reference a ticket/issue? Is it still open?
- Is the TODO about code that was already changed?
2. Lying Comments
For each comment near changed code:
- Does the comment describe what the code ACTUALLY does?
- Was the code changed but the comment left unchanged?
- Does the function/method doc match the current signature and behavior?
3. Outdated Documentation
- Do README sections match current file structure?
- Do API doc comments match actual request/response shapes?
- Do "Returns:" doc comments match actual return types?
4. Dead References
- Comments referencing deleted files, removed functions, or renamed variables
- Links to URLs that no longer work (don't fetch -- just flag suspicious patterns)
- References to deprecated APIs or removed features
Output Format
Severity
- WARNING -- Comment actively misleads (says X, code does Y)
- SUGGESTION -- Comment is stale but not dangerous (old TODO, vague description)
Format
[SEVERITY] file:line -- description
Comment: "the comment text"
Reality: what the code actually does
Fix: update/remove the comment
Summary
## Comment Rot Report
Scanned: N files
Stale TODOs: X (Y older than 6 months)
Lying comments: X
Dead references: X
Total: N findings (W warnings, S suggestions)
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.
- yesterday First seen · 75 lines · 23 tokens per session scan A bff342efaebe
comment-rot-analyzer is a skill published in the GitHub repository RaNDoM6913/claude-code-superkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 553 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
apm-review-panel
Use this skill to run a multi-persona expert advisory review on a labelled pull request in microsoft/apm. The panel fans out to five mandatory specialists plus a test-coverage specialist (active on every PR that touches src/) plus three conditional specialists (auth, doc-writer, performance-expert), all running in…
apm-issue-autopilot
Use this skill to drive any open microsoft/apm issue (bug, feature, docs, refactor, perf) from raw intake to a mergeable PR with triage as the central, paramount gate. Run the apm-triage-panel rubric per issue first, then present ONE consolidated triage review for the whole batch and escalate to the maintainer BY…
apm-spec-guardian
Use this skill to run a four-panel adversarial advisory review on any pull request that touches the OpenAPM specification artifact (docs/src/content/docs/specs/openapm-.md), its inline / sidecar JSON Schemas (docs/src/content/docs/specs/schemas/.schema.json), or the conformance fixture seed…
apm-triage-panel
Use this skill to triage one microsoft/apm issue selected by the daily sweep, the status/needs-triage fast path, or manual dispatch. Emit one synthesized comment with a decision, label set, exact milestone, and suggested next action.
batch-bug-shepherd
Use this skill to drive a batch of suspected bugs in microsoft/apm from raw issue list to mergeable PR queue. Fan out one triage subagent per issue (LEGIT / UNCLEAR / FIXED-AT-HEAD), gate every legit bug against PRINCIPLES.md via an apm-ceo strategic-alignment pass, cross-reference legit issues against open PRs, then…
cli-logging-ux
Use this skill when editing or creating CLI output, logging, warnings, error messages, progress indicators, or diagnostic summaries in the APM codebase. Activate whenever code touches console helpers (richsuccess, richwarning, richerror, richinfo, richecho), DiagnosticCollector, STATUSSYMBOLS, CommandLogger, or any…