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/adrnpx skills add cliffren/swf --skill adrgit 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.00015 | $0.00450 |
| Opus 5 | $0.00008 | $0.00225 |
| Sonnet 5 | $0.00003 | $0.00090 |
| Haiku 4.5 | $0.00002 | $0.00045 |
Grade A, and why
adr 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
Write ADR
Create a new Architecture Decision Record in the project's docs/adr/ directory.
Input
$ARGUMENTS — the ADR title (e.g., "使用 sparse matrix 存储表达矩阵"). If not provided, ask.
Workflow
-
Auto-number:
- Scan
docs/adr/for existing ADRs - Next number = max existing + 1, zero-padded to 3 digits
- Scan
-
Gather context:
- Ask the user:
- What decision was made?
- What alternatives were considered?
- Why was this option chosen?
- Read
docs/design.mdfor related context
- Ask the user:
-
Write the ADR:
File:
docs/adr/<NNN>-<slug>.md# ADR-<NNN>: <Title> **Date:** <today> **Status:** Accepted ## Context <What problem or question prompted this decision> ## Decision <What was decided> ## Alternatives Considered <Other options and why they were rejected> ## Consequences <What this means going forward — positive and negative> ## References <Links to issues, papers, docs if relevant> -
Commit:
git add docs/adr/<NNN>-<slug>.md- Commit with message:
docs: add ADR-<NNN> <title>
-
Prompt for design update:
- Check if the decision affects
docs/design.md - If yes: "这个决策影响到 design.md，要运行
/swf:update-design更新吗？"
- Check if the decision affects
Rules
- ADRs are append-only: never modify existing ADRs
- If a decision supersedes a previous one, note it in Context and update the old ADR's status to "Superseded by ADR-NNN"
- Must be run from within a project repo directory
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 · 68 lines · 15 tokens per session scan A 9b96ac79ee95
adr is a skill published in the GitHub repository cliffren/swf (5 stars, last pushed 4mo ago), licensed MIT. It adds 15 tokens to every session and 450 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.
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…