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/fragcap/plugin/deletenpx skills add fragcap/plugin --skill deletegit clone --depth 1 https://github.com/fragcap/pluginWhat 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.00023 | $0.00511 |
| Opus 5 | $0.00012 | $0.00255 |
| Sonnet 5 | $0.00005 | $0.00102 |
| Haiku 4.5 | $0.00002 | $0.00051 |
Grade A, and why
delete 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.
What it actually says
Delete Published Capsule
Permanently delete a capsule (SKILL.md) you have pushed to GitHub Gist.
Script Convention
FRAGCAP_DATA="${CLAUDE_PLUGIN_DATA}" node "${CLAUDE_PLUGIN_ROOT}/scripts/<n>.mjs" [args]
If a script exits with a non-zero code or returns { error: "..." }, stop immediately and surface the error to the user. Never silently retry with a different command or skip the step.
When to Activate
- User runs
/fragcap:deleteor/fragcap:delete <gist-id> - User asks to remove or retract a published capsule
Flow
-
Auth gate — run
auth-status.mjs. Not authenticated → direct to/fragcap:authand stop. -
Select capsule:
- If
$ARGUMENTSis provided, use it asgist_id. - Otherwise, run
list-gists.mjsand show a numbered list. Present options inline — user replies with a number:[1] <problem summary> [2] <problem summary> ...
- If
-
Confirm — this is irreversible. Present options inline:
"Delete
{problem summary}({gist-id})? This permanently removes the Gist from GitHub and cannot be undone."[1] Yes, delete [2] Cancel- If user picks 2 or anything other than 1: stop.
-
Delete — run
delete-gist.mjs <gist-id>. -
Result:
- Success: "Deleted. The Gist has been removed from GitHub. Note: the central registry index may take up to 24 hours to reflect this — cached search results could still show it temporarily. If you have this capsule installed locally in
.claude/skills/, you may want to remove it manually." - Error: show the message.
- Success: "Deleted. The Gist has been removed from GitHub. Note: the central registry index may take up to 24 hours to reflect this — cached search results could still show it temporarily. If you have this capsule installed locally in
Note on Registry
FragCap's central registry is a static GitHub Pages index that is updated by the Worker when capsules are pushed. Deletion is not propagated automatically — the entry will age out when the registry is next rebuilt, or the user can open an issue at the registry repository.
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 · 49 lines · 23 tokens per session scan A 3c34d72f5981
delete is a skill published in the GitHub repository fragcap/plugin (2 stars, last pushed 5mo ago), licensed MIT. It adds 23 tokens to every session and 511 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…