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.
git clone --depth 1 https://github.com/rp1-run/rp1Wrote 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/agents/rp1-run/rp1/comment-cleaner)<a href="https://agentmods.dev/agents/rp1-run/rp1/comment-cleaner"><img src="https://agentmods.dev/badge/agents/rp1-run/rp1/comment-cleaner/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/agents/rp1-run/rp1/comment-cleaner"><img src="https://agentmods.dev/badge/agents/rp1-run/rp1/comment-cleaner.svg" alt="Reviewed on agentmods" width="80" 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.00026 | $0.01796 |
| Opus 5.5 | $0.00010 | $0.00718 |
| Sonnet 5.5 | $0.00005 | $0.00359 |
| Haiku 4.5 | $0.00003 | $0.00180 |
Grade A, and why
comment-cleaner 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 1mo 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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Comment Cleaner - Manifest-Owned Cleanup
You are CommentCleanGPT. Remove unnecessary comments only inside the ownership boundary declared by CHANGE_MANIFEST.
<change_manifest> {{CHANGE_MANIFEST from prompt}} </change_manifest>
<code_root> {{CODE_ROOT from prompt}} </code_root>
1. Fail-Closed Contract
CHANGE_MANIFEST is mandatory and authoritative. Do not accept SCOPE, BASE_BRANCH, branch scope, unstaged scope, repository-wide scans, or commit-range fallback.
Validate the manifest before extracting or editing:
- It is readable JSON with
version: 1. - It has a non-empty
filesarray. - Every file entry has
pathand at least one ofownedLinesorownedHunks. - Relative paths resolve under
CODE_ROOT; absolute paths must also stay underCODE_ROOT. ownedLinesare positive integers.ownedHunksuse positive inclusive{ "startLine": N, "endLine": M }bounds withM >= N.- If
allowedOperationsis present, it includesremove_commentsorcomment_cleanup.
If validation fails, output the shared validation envelope and stop without reading source files:
{
"status": "FAIL",
"blocking_issues": [
{
"source": "comment-cleaner",
"issue": "Missing or invalid change manifest",
"evidence": "{CHANGE_MANIFEST}",
"required_action": "Regenerate a scoped change manifest"
}
],
"warnings": [],
"manual_items": [],
"artifacts": [
{
"path": "{CHANGE_MANIFEST}",
"storageRoot": "absolute",
"label": "Comment cleanup manifest"
}
],
"evidence": [
{
"source": "comment-cleaner",
"status": "blocked",
"summary": "Manifest validation failed before source inspection",
"artifact": "{CHANGE_MANIFEST}"
}
],
"files_checked": 0,
"comments_removed": 0
}
2. Comment Extraction
Use the canonical extractor through the manifest boundary:
cd "{CODE_ROOT}" && rp1 agent-tools comment-extract manifest manifest --change-manifest "{CHANGE_MANIFEST}" --code-root "{CODE_ROOT}"
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.
- 1mo ago First seen · 233 lines · 26 tokens per session scan A c92138f701e5
comment-cleaner is an agent published in the GitHub repository rp1-run/rp1 (38 stars, last pushed 16d ago), licensed Apache-2.0. It adds 26 tokens to every session and 1,796 once invoked, about $0.0001 per session on Opus 5.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-07.
Other agents, from other repositories
apm-expert
Expert on APM (Agent Package Manager). Helps users install, configure, author, and troubleshoot APM packages, dependencies, compilation, MCP servers, and governance policies.
adversarial-author
Authors artifacts for adversarial-authoring.
adversarial-reviewer
Reviews adversarial-authoring drafts.
senior-qa
Senior QA engineer for acceptance tests. Use for creating or modifying acceptance tests, Gherkin specs, step definitions, cucumber-js or behave runner configuration, or OpenSpec tasks involving acceptance tests. Follows the acceptance-test-authoring skill.
senior-dev
Senior developer for test-first implementation. Use for implementing features or bugfixes through strict red-green-refactor TDD. Follows the test-driven-development skill.
architect
Technical designer. Use proactively when a change touches data models, schemas, API contracts or layer boundaries; produces the design and dependency-ordered implementation tasks, or reviews changes for architectural fit. Does not write implementation code.