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/cliffren/swf/nextnpx skills add cliffren/swf --skill nextgit clone --depth 1 https://github.com/cliffren/swfWhat 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.00021 | $0.00407 |
| Opus 5 | $0.00010 | $0.00204 |
| Sonnet 5 | $0.00004 | $0.00081 |
| Haiku 4.5 | $0.00002 | $0.00041 |
Grade A, and why
next 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 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.
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
Pick Up Next Task
Fetch the next available Todo issue from Linear and start executing it.
Input
$ARGUMENTS — optional label filter (e.g., dev, writing, agent:claude). If omitted, pick the highest priority Todo.
Workflow
-
Find the current project:
- Determine the Linear project from the current repo (match by name)
- If not in a project repo, ask the user which project
-
Query Todo issues:
- List issues with status Todo in this project
- If a label filter is provided, apply it
- Sort by priority, then by creation date
-
Present the candidate:
- Show the top issue: title, description, labels, priority
- Ask: "开始这个任务？还是看下一个？"
-
Start the task:
- Mark the issue as In Progress in Linear
- Assign to "me"
- Read the issue description for requirements/spec
-
Load context if needed:
- If the task involves code changes, read relevant source files
- If the task references design.md or ADRs, read those
-
Begin execution:
- Follow the requirements from the issue description
- Follow the project's CLAUDE.md conventions
- For dev tasks, consider using Superpowers workflow (
/superpowers:brainstormingor/superpowers:writing-plans)
Notes
- Only picks up one task at a time
- If there are no Todo issues, suggest running
/swf:plan-nextto create new ones - Respect executor labels: don't pick up
manualtasks, onlyagent:claudeor unlabeled
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 · 50 lines · 21 tokens per session scan A d62155dd7972
next is a skill published in the GitHub repository cliffren/swf (5 stars, last pushed 3mo ago), licensed MIT. It adds 21 tokens to every session and 407 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.
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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.