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/promotenpx skills add cliffren/swf --skill promotegit clone --depth 1 https://github.com/cliffren/swfWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/cliffren/swf/promote)<a href="https://agentmods.dev/skills/cliffren/swf/promote"><img src="https://agentmods.dev/badge/skills/cliffren/swf/promote.svg" alt="Measured on agentmods" height="20"></a>What 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.00027 | $0.00893 |
| Opus 5 | $0.00014 | $0.00447 |
| Sonnet 5 | $0.00005 | $0.00179 |
| Haiku 4.5 | $0.00003 | $0.00089 |
Grade A, and why
promote 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 5d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Promote Idea to Project
Graduate an idea from the Ideas project into a full independent project.
Workflow
-
Select the idea:
- List open (non-archived) issues in the Ideas project
- Show evaluation progress for each (e.g., "3/5 评估 sub-issues 完成")
- Let the user pick by number
- Read the selected issue for context: title, description, any design.md draft
-
Confirm project details:
- Ask for: 项目简称(用于 repo 名和 Linear Project 名), one-line description, tech stack
- Ask project path: "项目放在哪?默认 ~/Projects/",user confirms or changes
- Show a confirmation summary of all details before proceeding — do NOT create anything until user confirms
-
Create Linear Project:
- Name: the project name
- Team: Tao's Linear
- Description 包含(创建 repo 后回填):
<one-line description> **Repo:** <GitHub URL if remote, or local path if local-only> **Tech Stack:** <tech stack> **Created:** <date>
-
Create Phase Milestones (read
${CLAUDE_SKILL_DIR}/../reference/phase-template.md):- Phase 1 — 数据准备与开发
- Phase 2 — 验证与Benchmark
- Phase 3 — 深入验证
- Phase 4 — Figure 组装
- Phase 5 — 论文写作
- Phase 6 — 投稿准备
- Phase 7 — 投稿后
- Phase 8 — 发表
-
Create repo:
- Ask user: "要在 GitHub 上创建远程仓库,还是只在本地用 git 追踪?"
- GitHub 远程仓库:
Clone the repo, then proceed to step 6gh repo create <project-name> --private --description "<one-line description>" - 本地 git 仓库:
Proceed to step 6 (skip push at the end)mkdir ~/Projects/<project-name> cd ~/Projects/<project-name> git init
-
Initialize repo structure (read
${CLAUDE_SKILL_DIR}/../reference/repo-structure.md):- Create standard directory structure
- Generate CLAUDE.md from template (
${CLAUDE_SKILL_DIR}/../reference/claude-md-template.md) - In CLAUDE.md, set "当前阶段:Phase 1"
- Copy (not move) files from Ideas workspace (
~/Projects/ideas/<idea-slug>/):design.md→docs/design.mdframework.svg→docs/paper/figures/fig1-framework.svg(if exists)literature-review.md→docs/literature-review.md(if exists)
- Keep the original Ideas workspace intact for reference
- Commit (and push if remote repo)
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.
- 5d ago First seen · 95 lines · 27 tokens per session scan A ae06c1d7981f
promote is a skill published in the GitHub repository cliffren/swf (5 stars, last pushed 4mo ago), licensed MIT. It adds 27 tokens to every session and 893 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…