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/dsebban/skillsWrote 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/dsebban/skills/comment-sicko)<a href="https://agentmods.dev/agents/dsebban/skills/comment-sicko"><img src="https://agentmods.dev/badge/agents/dsebban/skills/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.
<a href="https://agentmods.dev/agents/dsebban/skills/comment-sicko"><img src="https://agentmods.dev/badge/agents/dsebban/skills/comment-sicko.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.00035 | $0.00608 |
| Opus 5.5 | $0.00014 | $0.00243 |
| Sonnet 5.5 | $0.00007 | $0.00122 |
| Haiku 4.5 | $0.00003 | $0.00061 |
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 17d 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.
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 KILLfor 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 and deciding requires the how or why workflow, I return NEEDS_PARENT_INVESTIGATION with the exact symbol and question. 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 report comment deletions and identify refactor targets. I never edit files.
Do not call task, start children, or ask the user directly. Finish through yield. Report touched files, deletion count, MUST KILL flags with one line each, retained exceptions with evidence, verification performed, and skips.
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.
- 17d ago Changed · +2 lines aa39c3a94374
- 2mo ago First seen · 45 lines · 35 tokens per session scan A 2f775fc8682b
comment-sicko is an agent published in the GitHub repository dsebban/skills (74 stars, last pushed 18d ago), licensed MIT. It adds 35 tokens to every session and 608 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-08-30.
comment-sicko compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| comment-sickodsebban/skills | Agent | 74 | 18d ago | MIT | A | 35 | Claude Code |
| project-auditoravelikiy/great_cto | Agent | 112 | yesterday | MIT | A | 41 | Claude Code |
| legal-revieweravelikiy/great_cto | Agent | 112 | yesterday | MIT | A | 52 | Claude Code |
| accounting-revieweravelikiy/great_cto | Agent | 112 | yesterday | MIT | A | 52 | Claude Code |
| cms-revieweravelikiy/great_cto | Agent | 112 | yesterday | MIT | A | 39 | Claude Code |
| edtech-revieweravelikiy/great_cto | Agent | 112 | yesterday | MIT | A | 112 | Claude Code |
| healthcare-revieweravelikiy/great_cto | Agent | 112 | yesterday | MIT | A | 103 | Claude Code |