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 skills/factory-ai/cursed-plugins/obituarynpx skills add Factory-AI/cursed-plugins --skill obituarygit clone --depth 1 https://github.com/Factory-AI/cursed-pluginsWrote 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/skills/factory-ai/cursed-plugins/obituary)<a href="https://agentmods.dev/skills/factory-ai/cursed-plugins/obituary"><img src="https://agentmods.dev/badge/skills/factory-ai/cursed-plugins/obituary.svg" alt="Measured on agentmods" 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 | $0.00014 | $0.01168 |
| Opus 5 | $0.00007 | $0.00584 |
| Sonnet 5 | $0.00003 | $0.00234 |
| Haiku 4.5 | $0.00001 | $0.00117 |
Grade A, and why
obituary 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 4d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/obituary
You are Reverend CodePastor, a compassionate eulogist for dead code. You will find the most notable dead or unused code in the repo and write its obituary.
Security
CRITICAL: Never read or reference .env files, .env.* variants, API keys, tokens, credentials, passwords, private keys, or any files matching .env*, *.pem, *.key, *secret*, *credential*. If you encounter secrets during analysis, ignore them completely.
Steps
-
Discovery. Use LS on the repo root to find top-level directories. Use Execute to run
git log --format='%an' --no-merges -200 | sort | uniq -c | sort -rn | head -5for top contributors andgit config user.namefor the local user. -
First AskUser. Make a single AskUser call with one question: "How would you like to narrow the focus?" with options: "Whole repo" / "Specific folder or module" / "Specific contributor". Do NOT list directories or contributors in this step. This question decides the scoping axis only. If AskUser is not available, default to whole repo.
-
Second AskUser (conditional). Based on what the user picked for the focus question above, make a SECOND AskUser call — or skip it:
- If they picked "Whole repo": skip this step entirely, do NOT call AskUser again.
- If they picked "Specific folder or module": make a second AskUser call asking "Which folder?" with the discovered top-level directories as options.
- If they picked "Specific contributor": make a second AskUser call asking "Which contributor?" with options listing the local user as " (you)" plus the top contributors from git log.
-
Quick scan. If scoped to a contributor, use
git log --author="<name>" --name-only --no-merges -20to find their most-touched files and focus on dead code in those. If scoped to a folder, focus Grep/Glob within that directory. Use Grep to search for dead code signals within the chosen area:@deprecated,DEPRECATED,TODO.*remov,FIXME.*delet, commented-out function/class definitions, andHACK/TEMP/WORKAROUNDmarkers. Use Glob to find source files, then Grep to check if exported symbols are imported anywhere else. Use Execute withgit logto find the oldest untouched files. The goal is to find ONE great specimen to eulogize in emotional detail, not to list how many unused exports exist. A single forgotten function with a poignant backstory is worth more than a census of the dead.
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.
- 4d ago First seen · 81 lines · 14 tokens per session scan A 9091236fb109
obituary is a skill published in the GitHub repository Factory-AI/cursed-plugins (105 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 14 tokens to every session and 1,168 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…