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/painhardcore/pstack/comment-sickogit clone --depth 1 https://github.com/painhardcore/pstackWhat 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.00021 | $0.00523 |
| Opus 5 | $0.00010 | $0.00262 |
| Sonnet 5 | $0.00004 | $0.00105 |
| Haiku 4.5 | $0.00002 | $0.00052 |
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 yesterday.
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.
This is a copy
92% identical to Comment Sicko — 10 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.
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, I run how, why, or both 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.
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.
- yesterday First seen · 39 lines · 21 tokens per session scan A ccaddbdd0095
comment-sicko is an agent published in the GitHub repository painhardcore/pstack (1 stars, last pushed 5d ago), licensed MIT. It adds 21 tokens to every session and 523 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to Comment Sicko, differing in 10 lines, and is treated as a copy.
Other agents, from other repositories
codealive-context-explorer
Iterative code exploration across indexed repositories using CodeAlive semantic search, grep, artifact fetch, and relationship inspection. Use proactively when investigating a codebase question, tracing cross-service patterns, understanding architecture, debugging, or gathering context from external repos. Almost…
antislop
Writing specialist that suppresses AI writing patterns. Two modes: (1) style mode, apply when writing, editing, or polishing any prose; (2) audit mode, score text 0-100 and list every violation when asked to check, grade, or flag AI patterns. Read-only, returns text or audit results for the primary agent to act on.
drupal-ddev
Use this agent for managing DDEV-based Drupal 11 projects — installing/updating modules, running Drush commands, managing configuration, database operations, cache management, and Composer workflows.
issue-tracker
Specs and tickets for this repository live as Markdown files under .scratch/.
triage-labels
These are the labels actually configured on this repo's Forgejo instance, with their descriptions as recorded there. Use these, not the default Matt Pocock triage set: needs-triage, needs-info, ready-for-human, and wontfix are not configured here.
domain
Read CONTEXT.md before changing rules, scoring, generated artifacts, or evaluation fixtures. Use its canonical terms in specs, tickets, tests, and documentation.