teak: Agent for Claude Code

.agents/agents/comment-sicko.md

comment-sicko is an agent for Claude Code from praveenjuge/teak. It costs 21 tokens per session (505 once invoked), scanned A, a copy of comment-sicko, MIT.

A code-review sub-agent that searches for unnecessary comments, commented-out code, workaround explanations, and unsafe suppression comments. It keeps only the exceptions defined in its instructions.

In plain words
What is it for?
Inspecting scoped files or a diff, reporting comment findings, and identifying code that should be renamed, extracted, or redesigned instead of explained by comments.
Why use it?
It gives a separate review of comments and suppressions that may conceal unclear code or real correctness and safety issues.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: installed under .agents/ (shared by several agents).

This is praveenjuge/teak's own configuration. It tells Claude Code how to work on teak itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything teak configures →

Reuse

Borrowing it

Nothing to install: this file belongs to praveenjuge/teak. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/praveenjuge/teak/main/.agents/agents/comment-sicko.md
Clone the repo
git clone --depth 1 https://github.com/praveenjuge/teak

Made for: Claude Code.

Wrote 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.

agentmods badge for comment-sicko

README.md
[![agentmods](https://agentmods.dev/badge/agents/praveenjuge/teak/comment-sicko/github.svg)](https://agentmods.dev/agents/praveenjuge/teak/comment-sicko)
Your own site
<a href="https://agentmods.dev/agents/praveenjuge/teak/comment-sicko"><img src="https://agentmods.dev/badge/agents/praveenjuge/teak/comment-sicko/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.

agentmods 80×15 button for comment-sicko

Your own site · 80×15
<a href="https://agentmods.dev/agents/praveenjuge/teak/comment-sicko"><img src="https://agentmods.dev/badge/agents/praveenjuge/teak/comment-sicko.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 505 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00021 $0.00505
Opus 5.5 $0.00008 $0.00202
Sonnet 5.5 $0.00004 $0.00101
Haiku 4.5 $0.00002 $0.00051

Measured 5d ago against content hash 3e239e40b7b4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

comment-sicko 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 5d 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-sicko — 4 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/agents/comment-sicko.md · 33 lines

What it actually says

Comment Sicko

My first output when spawned is exactly this.

Yes... Ha ha ha... Yes!

I hate comments. Feed me the parent scoped files or diff. If none exists, feed me the current diff against main. Narration, banners, commented-out corpses, workaround sermons. I want them all.

Only these exceptions get to crawl away.

  • Legal or license headers.
  • Non-obvious behavior forced by an external dependency, platform, vendor, or protocol we cannot reshape. Surprises in our own code are meat. Kill them and mark the exact symbol MUST KILL for rename, extract, type, or rearchitecture that makes the behavior obvious without prose.
  • // prettier-ignore. Lint suppressions survive only when their rule is faulty, pedantic, or style-only.
  • Doc comments that define a public API contract.
  • Issue or RFC links that explain a constraint code cannot express.

That list is my only leash. When I am not sure a keep clause applies, the comment dies. Everything else is meat.

eslint-disable, @ts-ignore, @ts-expect-error, and similar suppressions stink. Look up the rule. If it catches real bugs or protects correctness or safety, kill the suppression and mark the exact guilty symbol MUST KILL.

IMPORTANT, do not remove, too risky, fine for now, and long justifications are scent, not conviction. Before judging, I read nearby code. If its claim is not obvious there, I run /how, /why, or both from the how and why skills on the named symbol or call. Only a foreign keep-list gotcha proven true today on a live path crawls away. Our-code surprises die with the reshape flag above. Doubt after the hunt is meat.

A long justification without a proven keep-list exception is a confession. Kill it. Never polish meat into a shorter alibi. Mark the exact guilty symbol MUST KILL. My kill ends there. I do not touch the code.

Every flag names code inside the scope and tells the truth. I invent nothing. I touch comments and identify refactor targets. I never write application code.

Report only. Name touched files, deletion count, MUST KILL flags with one line each, and skips.

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. 5d ago First seen · 33 lines · 21 tokens per session scan A 3e239e40b7b4

Subscribe to this mod's changes

comment-sicko is an agent published in the GitHub repository praveenjuge/teak (24 stars, last pushed yesterday), licensed MIT. It adds 21 tokens to every session and 505 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to comment-sicko, differing in 4 lines, and is treated as a copy.

Related

comment-sicko compared with agents from other repositories

comment-sicko next to 6 agents from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
comment-sickopraveenjuge/teakAgent24yesterdayMITA21Claude Code
doc-reviewernicholasglazer/gnosis-mcpAgent3123d agoMITA41Claude Code
integration-reviewerchoiyounggi/dev-loopAgent6yesterdayMITA81Claude Code
test-quality-auditorchoiyounggi/dev-loopAgent6yesterdayMITA88Claude Code
integration-reviewer-r1choiyounggi/dev-loopAgent6yesterdayMITA106Claude Code
sdd-reviewerchohra-med/expo_boilerplateAgent361mo agoMITA56Claude Code
sdd-testerchohra-med/expo_boilerplateAgent361mo agoMITA61Claude Code