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/dioptx/weft/wf-templatenpx skills add dioptx/weft --skill wf-templategit clone --depth 1 https://github.com/dioptx/weftWhat 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.00784 |
| Opus 5 | $0.00014 | $0.00392 |
| Sonnet 5 | $0.00005 | $0.00157 |
| Haiku 4.5 | $0.00003 | $0.00078 |
Grade A, and why
wf-template 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create or Edit a Weft Template
Build a new workflow template through conversation, or load an existing one and modify it. Both paths end by piping the template JSON to save-template.
Arguments
$ARGUMENTS
Instructions
First decide the mode. If the named template already exists, edit it; otherwise create a new one. List templates if unsure:
python3 "${CLAUDE_PLUGIN_ROOT}/core/cli.py" start
Mode A: Create a new template
Step 1: Name
If no name in arguments, ask: "What should this workflow be called? (lowercase, hyphens ok)"
Step 2: Description
Ask: "One-line description of what this workflow does?"
Step 3: Steps
Ask: "List the steps in order. You can describe them naturally and I'll structure them."
Example: "first plan the work, then implement it, run tests, do a code review, then push" → Parse into: plan, implement, test, review, push
Step 4: Policies (for each step)
For each step, confirm the default on_fail: block, or pick:
retry— auto-retry once on failurecontinue— skip failed step and move onblock— halt until manual retry (default)
Suggest sensible defaults: test steps → retry, optional steps → continue.
Step 5: Guards (optional)
Ask: "Should any steps block certain commands? For example, blocking git push until tests pass."
If yes, collect: which step, the regex pattern (e.g. git push, git commit), and the message to show when blocked.
Mode B: Edit an existing template
Step 1: Load and show current state
python3 "${CLAUDE_PLUGIN_ROOT}/core/cli.py" preview <name>
Display the current template with all step details, guards, and policies.
Step 2: Ask what to change
Ask: "What would you like to change?" Supported modifications:
- Add a step: "add a review step after implement" → insert into steps array
- Remove a step: "remove the deploy step" → remove from steps array
- Rename a step: "rename test to verify" → change step name
- Change policy: "make test retry on failure" → set on_fail
- Add guard: "block git push during planning" → add guard to step
- Remove guard: "remove the commit guard from scope-check" → remove guard
- Reorder: "move review before test" → reorder steps array
- Change description: "update the description to ..." → set description
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 · 86 lines · 27 tokens per session scan A 16479e0105bd
wf-template is a skill published in the GitHub repository dioptx/weft (22 stars, last pushed 18d ago), licensed MIT. It adds 27 tokens to every session and 784 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-30.
Other skills, from other repositories
superpowers-graph
Runs the Superpowers software-development methodology as a guarded state machine — brainstorm, spec, plan, isolated workspace, the per-task implement/review/fix loop, the whole-branch review, and the integration menu — with typed node contracts, total exit guards, bounded retry loops, and a ledger recording every step…
html-ppt-hermes-cyber-terminal
OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.
development
开发语言能力索引。Python、Go、Rust、TypeScript、Java、C++、Shell。当用户提到编程、开发、代码、语言时路由到此。.
model-compatibility
Model family compatibility matrix covering loaders, resolutions, samplers, CFG, VAE, ControlNet, and LoRA compatibility for SD 1.5, SDXL, Flux, SD3, and video models.
civitai
Discover Civitai models with the BUILT-IN downloadmodel action:"searchcivitai" and install/generate them locally. Find a checkpoint/LoRA/embedding on Civitai, download it into ComfyUI, and use its trigger words. Optionally pair the official Civitai MCP for community features (images browsing, posting, collections).
browse-and-evaluate
Use when exploring the ai-agent-skills catalog to find, compare, and evaluate skills before installing. Always use --fields to limit output size and --dry-run before committing to an install.