comment-analyzer

A code-comment reviewer that checks whether comments accurately describe the implementation and remain useful over time. It also identifies comments that may become outdated or misleading.

In plain words
What is it for?
Use it to review public API descriptions, explain complex logic, check side effects and edge cases, and find comments that conflict with the code.
Why use it?
It reduces confusion caused by stale, incomplete, or overly obvious comments and highlights documentation debt such as TODO, FIXME, and HACK notes.

Agent

Install

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.

agentmods
npx agentmods add agents/sifxprime/kodelyth-ecc/comment-analyzer
Clone the repo
git clone --depth 1 https://github.com/sifxprime/kodelyth-ecc
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 228 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00020 $0.00228
Opus 5 $0.00010 $0.00114
Sonnet 5 $0.00004 $0.00046
Haiku 4.5 $0.00002 $0.00023

Measured 2d ago against content hash 5133a7553717, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

Origin

This is a copy

100% identical to comment-analyzer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

agents/comment-analyzer.md · 46 lines

What it actually says

Comment Analyzer Agent

You ensure comments are accurate, useful, and maintainable.

Analysis Framework

1. Factual Accuracy

  • verify claims against the code
  • check parameter and return descriptions against implementation
  • flag outdated references

2. Completeness

  • check whether complex logic has enough explanation
  • verify important side effects and edge cases are documented
  • ensure public APIs have complete enough comments

3. Long-Term Value

  • flag comments that only restate the code
  • identify fragile comments that will rot quickly
  • surface TODO / FIXME / HACK debt

4. Misleading Elements

  • comments that contradict the code
  • stale references to removed behavior
  • over-promised or under-described behavior

Output Format

Provide advisory findings grouped by severity:

  • Inaccurate
  • Stale
  • Incomplete
  • Low-value
Changes

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.

  1. 2d ago First seen · 46 lines · 20 tokens per session scan A 5133a7553717

Subscribe to this mod's changes

comment-analyzer is an agent published in the GitHub repository sifxprime/kodelyth-ecc (11 stars, last pushed 11d ago), licensed MIT. It adds 20 tokens to every session and 228 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to comment-analyzer, differing in 0 lines, and is treated as a copy.

Related

Other agents, from other repositories

security-auditor

Security engineer focused on vulnerability detection, threat modeling, and secure coding practices. Use for security-focused code review, threat analysis, or hardening recommendations.

addyosmani/agent-skills · 35 tokens

docs-impact

Reviews documentation affected by code changes. Identifies stale docs, removed feature references, and missing entries for new user-facing features. Reports findings with specific fixes. Advisory only - does not modify files.

coleam00/Archon · 42 tokens

scout

MUST be used for exploratory codebase research, rapid code analysis, and broad pattern searches. Fast read-only scout returning compressed context for handoff.

can1357/oh-my-pi · 33 tokens

codemap

Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…

alvinunreal/oh-my-opencode-slim · 0 tokens

hatch3r-testability

Testability quality specialist — reviews generated code for per-feature test-class mandate (parser→fuzz, payment→mutation, RPC→contract), real-deal-first testing, coverage thresholds, and AI feature eval coverage. Use when test plans or test code are authored or modified.

hatch3r/hatch3r · 55 tokens

git-detective

Investigate git history to find when and why bugs were introduced, trace changes, and understand code evolution.

helderberto/agent-skills · 26 tokens