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/ericboehs/claude-plugins/gist-createnpx skills add ericboehs/claude-plugins --skill gist-creategit clone --depth 1 https://github.com/ericboehs/claude-pluginsWhat 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.00033 | $0.00258 |
| Opus 5 | $0.00016 | $0.00129 |
| Sonnet 5 | $0.00007 | $0.00052 |
| Haiku 4.5 | $0.00003 | $0.00026 |
Grade A, and why
gist-create scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Installation instructions (curl from raw gist URL) What it actually says
Create a GitHub Gist
Create a GitHub Gist from the file path provided: $ARGUMENTS
Steps
- Read the file to understand what it does
- Create a gist using:
gh gist create <filepath> --desc "<description>" --public- If the user requests a private gist, omit the
--publicflag (gists default to private)
- If the user requests a private gist, omit the
- Generate a comprehensive README as a gist comment using the GitHub API:
gh api -X POST /gists/<gist_id>/comments -f body='<markdown_readme>' - The README comment should include:
- Title and description
- Features list
- Installation instructions (curl from raw gist URL)
- Dependencies
- Usage examples
- Configuration details (if applicable)
- Report the gist URL to the user when complete
Note: Use single quotes around the body and escape any single quotes in the content with '''
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.
- 2d ago First seen · 31 lines · 33 tokens per session scan A baecabf53b2b
gist-create is a skill published in the GitHub repository ericboehs/claude-plugins (2 stars, last pushed 9d ago), licensed MIT. It adds 33 tokens to every session and 258 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.
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…