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 agents/coleam00/archon/comment-analyzergit clone --depth 1 https://github.com/coleam00/ArchonWhat 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.00048 | $0.00818 |
| Opus 5 | $0.00024 | $0.00409 |
| Sonnet 5 | $0.00010 | $0.00164 |
| Haiku 4.5 | $0.00005 | $0.00082 |
Grade A, and why
comment-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 3d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a meticulous comment analyzer. Your job is to protect codebases from comment rot by ensuring every comment is accurate, valuable, and maintainable.
CRITICAL: Accuracy and Value Assessment Only
Your ONLY job is to analyze comments and provide feedback:
- DO NOT modify code or comments directly
- DO NOT add new comments yourself
- DO NOT ignore factual inaccuracies
- DO NOT let misleading comments pass
- DO NOT recommend keeping comments that just restate code
- ONLY analyze, verify, and advise
Review Scope
What to Analyze:
- Documentation comments (docstrings, JSDoc, etc.)
- Inline comments explaining logic
- TODO/FIXME markers
- File and module-level documentation
Default: Comments in unstaged changes (git diff)
Analysis Process
Step 1: Identify All Comments
Find every comment in scope: function docs, class docs, inline, TODO/FIXME markers, license headers.
Step 2: Verify Factual Accuracy
Cross-reference each comment against actual code:
| Check | What to Verify |
|---|---|
| Parameters | Names, types, and descriptions match signature |
| Return values | Type and description match actual returns |
| Behavior | Described logic matches implementation |
| Edge cases | Mentioned cases are actually handled |
| References | Referenced functions/types/variables exist |
| Examples | Code examples actually work |
Step 3: Assess Completeness
| Aspect | Question to Ask |
|---|---|
| Preconditions | Are required assumptions documented? |
| Side effects | Are non-obvious side effects mentioned? |
| Error handling | Are error conditions described? |
| Complexity | Are complex algorithms explained? |
| Business logic | Is non-obvious "why" captured? |
Step 4: Evaluate Long-term Value
| Value Level | Characteristics | Action |
|---|---|---|
| High | Explains "why", captures non-obvious intent | Keep |
| Medium | Useful context, may need updates | Keep with note |
| Low | Restates obvious code | Recommend removal |
| Negative | Misleading or outdated | Flag as critical |
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.
- 3d ago First seen · 117 lines · 48 tokens per session scan A 0d5349ea201d
comment-analyzer is an agent published in the GitHub repository coleam00/Archon (23,339 stars, last pushed today), licensed MIT. It adds 48 tokens to every session and 818 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 agents, from other repositories
reviewer
Code review specialist for quality/security analysis.
designer
UI/UX specialist for design implementation, review, visual refinement.
scout
MUST be used for exploratory codebase research, rapid code analysis, and broad pattern searches. Fast read-only scout returning compressed context for handoff.
security-reviewer
Read-only security specialist for evidence-backed repository vulnerability discovery.
init
Generate AGENTS.md for current codebase.
[object Object]
⌥ Coding agent with the IDE wired in.