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/importnpx skills add cliffren/swf --skill importgit 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.00025 | $0.01388 |
| Opus 5 | $0.00013 | $0.00694 |
| Sonnet 5 | $0.00005 | $0.00278 |
| Haiku 4.5 | $0.00003 | $0.00139 |
Grade A, and why
import 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.
How it starts
The opening of the file, as written. The whole thing — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Import Existing Project
Bring an existing research project into the SWF workflow without disrupting current work.
Workflow
-
Identify the project:
- Ask: repo 路径或 GitHub URL
- Read the repo to understand current state:
lstop-level structure- Check for existing CLAUDE.md, README, docs/
git log --oneline -10recent history- Check language/framework from files
-
Assess current phase:
- Analyze repo signals to infer phase:
- 有
src/但没有results/或实验记录 → 可能 Phase 1 - 有 benchmark 脚本或结果文件 → 可能 Phase 2
- 有 case study 分析脚本或结果 → 可能 Phase 3
- 有 figure 组装脚本、publication-quality 图片 → 可能 Phase 4
- 有
docs/paper/、论文 draft、.tex 文件 → 可能 Phase 5 - 有 cover letter、submission 相关文件 → 可能 Phase 6+
- 检查 git log 中的关键词(benchmark, figure, draft, revision 等)
- 有
- Present your assessment with evidence:
根据 repo 分析,我判断项目在 Phase 2(验证与 Benchmark): - src/ 下核心代码已完成(最近 commit 多是 bugfix 而非新功能) - 有 benchmarks/ 目录和部分结果 - 但还没有 case study 相关代码 你觉得准确吗? - Let the user confirm or correct
- Analyze repo signals to infer phase:
-
Gather project info:
- 项目简称(用于 Linear Project 名,通常和 repo 名一致)
- 一句话描述
- 技术栈
- GitHub repo URL(从
git remote -v自动获取)
-
Create Linear Project:
- Name: project name
- Team: Tao's Linear
- Description:
<one-line description> **GitHub:** <repo-url> **Tech Stack:** <tech stack> **Imported:** <date> **Imported at:** Phase <N>
-
Create Phase Milestones (read
${CLAUDE_SKILL_DIR}/../reference/phase-template.md):- Create all Phase 1~8 milestones
- Phases before current: leave empty (historical work not tracked)
- Current phase: will populate with issues next
-
Scaffold missing docs (non-destructive — never overwrite existing files):
File If exists If missing CLAUDE.md Keep as-is, suggest merging SWF conventions Generate from template docs/design.md Keep as-is Create placeholder, remind user to fill docs/adr/ Keep as-is Create directory docs/experiments/benchmark/ Keep as-is Create directory docs/experiments/case/ Keep as-is Create directory docs/paper/ Keep as-is Create directory configs/ Keep as-is Create directory results/ Keep as-is Create directory .gitignore Merge SWF entries (results/, *.h5ad, etc.) without deleting existing rules Generate from template
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 · 152 lines · 25 tokens per session scan A 569ff180d1a4
import is a skill published in the GitHub repository cliffren/swf (5 stars, last pushed 4mo ago), licensed MIT. It adds 25 tokens to every session and 1,388 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…