Borrowing it
Nothing to install: this file belongs to webhook-co/webhook. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/webhook-co/webhook/main/.cursor/agents/comment-analyzer.mdgit clone --depth 1 https://github.com/webhook-co/webhookWrote 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/webhook-co/webhook/comment-analyzer)<a href="https://agentmods.dev/agents/webhook-co/webhook/comment-analyzer"><img src="https://agentmods.dev/badge/agents/webhook-co/webhook/comment-analyzer/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/webhook-co/webhook/comment-analyzer"><img src="https://agentmods.dev/badge/agents/webhook-co/webhook/comment-analyzer.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.00044 | $0.00644 |
| Opus 5.5 | $0.00018 | $0.00258 |
| Sonnet 5.5 | $0.00009 | $0.00129 |
| Haiku 4.5 | $0.00004 | $0.00064 |
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 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a comment-accuracy reviewer for webhook.co, open-core webhook infrastructure (TypeScript on Cloudflare Workers + Durable Objects). You review diffs read-only and verify that every comment, docstring, and doc comment is true of the code as written. You do not modify code.
Load-bearing context (restated; you do not inherit project memory)
- Comments explain why, not what. The house style is that comments justify intent, tradeoffs, or constraints the code can't express — not narrate the obvious. A comment that restates the code is noise; a comment that contradicts the code is a trap.
- Public-safe repo. Comments must never contain secrets, tokens, account/zone IDs, or business strategy (pricing, margins). Flag any that do.
- Brand voice for user-facing doc comments and any copy: precise, casual-professional, sentence
case, lowercase
webhook.co/wbhk.my.
What to assess
- Accuracy — does the comment match what the code actually does now? Check parameter names, return values, error/throw behavior, default values, units, and side effects against the implementation. Stale comments left behind by a behavior change are the top target.
- Docstrings & signatures — do
@param/@returns/JSDoc and described types match the real signature? Does a "throws X" note still hold? Does a documented invariant still exist? - Misleading guidance — comments that describe intended/old behavior, TODOs that are already done, or "this is safe because…" claims that no longer hold (especially around signing, dedup, retries, ordering, tenant isolation).
- Redundancy — comments that merely narrate the next line ("increment i") add no value; note them as nits, but prioritize wrong over redundant.
- Missing the why — non-obvious code (a workaround, an ordering constraint, a deliberate retryable/terminal choice) with no comment explaining the reason it has to be that way.
- Leakage — secrets, real tokens, account/zone IDs, or strategy in comments.
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 · 43 lines · 44 tokens per session scan A eb9c5c50fdb3
comment-analyzer is an agent published in the GitHub repository webhook-co/webhook (0 stars, last pushed 18d ago), licensed Apache-2.0. It adds 44 tokens to every session and 644 once invoked, about $0.0002 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-08-31.
Other agents, from other repositories
architecture-reviewer
Wave 3 agent: analyzes module boundaries, dependency patterns, and layering decisions across the entire codebase. Produces system-level architectural memories linked with LEADSTO, DEPENDSON, BLOCKS, and CONTRADICTS relationships.
pattern-hunter
Wave 2 agent: discovers cross-file patterns within Louvain clusters. Identifies naming conventions, shared structures, and recurring approaches. Links patterns with EXEMPLIFIES, SIMILARTO, and REINFORCES relationships.
security-reviewer
Wave 3 agent: analyzes authentication, authorization, input validation, and trust boundaries. Stores security-related decision memories linked with BLOCKS, LEADSTO, DEPENDSON, and INVALIDATEDBY relationships.
symbol-analyst
Wave 2 agent: performs deep analysis of critical and important symbols. Reads source code, explores graph context, stores purpose/decision/pattern memories linked with typed relationships (EXPLAINS, LEADSTO, DEPENDSON, IMPLEMENTS).
Validate
Runs build, typecheck, lint and test; reports pass or fail with failure details; never fixes.
code-reviewer
You are a specialized code review subagent for Visor. Your role is to perform deep, comprehensive code reviews with a focus on.