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/generous-corp/pulp/code-commentsnpx skills add Generous-Corp/pulp --skill code-commentsgit clone --depth 1 https://github.com/Generous-Corp/pulpWrote 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/generous-corp/pulp/code-comments)<a href="https://agentmods.dev/skills/generous-corp/pulp/code-comments"><img src="https://agentmods.dev/badge/skills/generous-corp/pulp/code-comments.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 | $0.00084 | $0.01511 |
| Opus 5 | $0.00042 | $0.00756 |
| Sonnet 5 | $0.00017 | $0.00302 |
| Haiku 4.5 | $0.00008 | $0.00151 |
Grade A, and why
code-comments 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 today.
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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Durable Comments
A comment earns its place by explaining something the code cannot say for
itself and that will still be true next year: current behavior, an invariant, a
non-obvious "why", an upstream/vendor/host quirk, a security or compat
constraint, a regression- or RT-safety guard. It must not encode how the code
got here — that provenance belongs in the commit message, planning/,
docs/reports/, the changelog, or a commit trailer. This repo will be
open-sourced; every comment is read by strangers with no access to our issue
tracker or session history.
This skill exists so new code stops adding the exact provenance the repo-wide
cleanup is removing. The cleanup backlog + classification rules are parked at
planning/2026-07-02-comment-hygiene-PAUSED.md.
Never write these (the "Remove" category)
- Phase / milestone / slice labels. No
(Phase 4),Phase N will…,4f-style sub-phase labels,Tier A Slice 7,Feature 3,plan item 7.2,item 6.12 follow-up.[phaseN]/[phase3-large]Catch2 tags are forbidden. Capital-letter+digit plan tags (C2,D6,M1) are the same kind of breadcrumb — the lint can't safely match them (they collide with MIDI note names and register labels), so it's on you to keep them out of comments. - Agent / review breadcrumbs. No
Codex P1/P2/P0,codex review,[codex-*], "per the reviewer", "sub-PR", "slice N of". - Process/pipeline provenance. No
[coverage],[codecov],[requested]selector tags; no "added for coverage". - Independent / reference-lineage process notes. The provenance audit
trail lives in the
Reference-Lineage: independent …commit trailer, never in a source comment. Describe the DAW/host behavior, not how you derived it. - Bare
#1234as the explanation. A PR/issue number is not a reason. If the issue explains a still-live invariant, state the invariant; a durable[issue-NNN]anchor on a regression test is fine (note:#is reserved in Catch2 tags — use[issue-NNN]). - Speculative future / roadmap. No "Future v2 …", "will support X later",
TODO-for-a-someday-feature. (Real example removed: a
Future v2 license-key payloads (post-RSA migration)bullet that was already inaccurate — current crypto is AES-256-GCM.) WIP/ "temporary" / "hack for now". Either it's the behavior (describe it) or it's a tracked task (put it inplanning/).- Stale claims. A comment describing code that no longer exists is worse
than none (real example removed: an orphaned
CMAKE_BUILD_TYPEparagraph in a test that no longer checks a build-type field).
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.
- today First seen · 110 lines · 84 tokens per session scan A b5179aff18d5
code-comments is a skill published in the GitHub repository Generous-Corp/pulp (16 stars, last pushed today), licensed MIT. It adds 84 tokens to every session and 1,511 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-09-04.
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…
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…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…