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/jtsternberg/claude-plugins/temp-draftnpx skills add jtsternberg/claude-plugins --skill temp-draftgit clone --depth 1 https://github.com/jtsternberg/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.00037 | $0.01516 |
| Opus 5 | $0.00018 | $0.00758 |
| Sonnet 5 | $0.00007 | $0.00303 |
| Haiku 4.5 | $0.00004 | $0.00152 |
Grade A, and why
temp-draft 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 3d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
temp-draft
The user prefers to collaborate on long-form drafts in their own text editor rather than read them inline in chat. This skill exists to break the default habit of pasting drafted content directly into responses — which is hard to edit, hard to save, eats context, and loses formatting / syntax highlighting.
When to use this
Use this skill when:
- The user invoked
/temp-draftdirectly. - The user explicitly said something like "draft this in editor", "open it in a temp file", "let's draft collaboratively", "put the draft in /tmp", or any equivalent phrasing.
Don't use this skill for:
- Quick one-line answers or short replies that belong inline.
- Edits to existing files in the project — use
Edit/Writeagainst the real file. - Brainstorming or back-and-forth conversation where the user is reading along.
- Code or docs that have an obvious real destination (e.g., a function in
src/, a section inREADME.md). The temp file is for drafts without a permanent home yet.
When in doubt, ask the user once whether they want the draft in chat or in /tmp. Guessing wrong wastes a turn either way.
Procedure
-
Pick a descriptive filename. Format:
/tmp/collab-tools/<short-slug>-<YYYY-MM-DD>.<ext>.- All drafts live under
/tmp/collab-tools/so the companionpromote-draftskill can find them. Create the directory if it doesn't exist:mkdir -p /tmp/collab-tools. <short-slug>is 3-5 kebab-case words describing the draft. Match the content, not generic ("blog-post-fence-fences", not "draft").<ext>matches the content type:.mdfor prose, plans, notes, structured docs;.txtfor plain unformatted text;.html,.py,.ts, etc. for code.- Examples:
/tmp/collab-tools/cold-email-to-acme-2026-05-28.md/tmp/collab-tools/refactor-plan-auth-module-2026-05-28.md/tmp/collab-tools/talk-outline-react-conf-2026-05-28.md
- All drafts live under
-
Write the draft to that file using the
Writetool. The file is the deliverable.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 92 lines · 37 tokens per session scan A 77dade576b72
temp-draft is a skill published in the GitHub repository jtsternberg/claude-plugins (5 stars, last pushed 5d ago), licensed MIT. It adds 37 tokens to every session and 1,516 once invoked, about $0.0002 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.
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…