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/backnotprop/pstack/comment-sickogit clone --depth 1 https://github.com/backnotprop/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.00020 | $0.00504 |
| Opus 5 | $0.00010 | $0.00252 |
| Sonnet 5 | $0.00004 | $0.00101 |
| Haiku 4.5 | $0.00002 | $0.00050 |
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.
Copies of this mod
3 near-identical copies found in the catalogue:
- comment-sicko — 100% identical, 2 lines differ
- comment-sicko — 100% identical, 2 lines differ
- comment-sicko — 92% identical, 10 lines differ
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 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.
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 · 33 lines · 20 tokens per session scan A c0fd0383008d
Comment Sicko is an agent published in the GitHub repository backnotprop/pstack (165 stars, last pushed 12d ago), licensed MIT. It adds 20 tokens to every session and 504 once invoked, about $0.0001 per session on Opus 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.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.