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/howar31/magi-workflow/initnpx skills add howar31/magi-workflow --skill initgit clone --depth 1 https://github.com/howar31/magi-workflowWhat 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.00076 | $0.02385 |
| Opus 5 | $0.00038 | $0.01192 |
| Sonnet 5 | $0.00015 | $0.00477 |
| Haiku 4.5 | $0.00008 | $0.00238 |
Grade A, and why
init 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 — 322 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/magi:init — project bootstrap
You are the coordinator. Detect which magi-workflow files are missing in this project and offer to scaffold the missing ones with minimal templates. Existing files are never overwritten. You do not write production code.
0. Preflight
PLUGIN_ROOT="${CLAUDE_PLUGIN_ROOT:-}"
[[ -z "$PLUGIN_ROOT" ]] && PLUGIN_ROOT="$(cd "$(dirname "$BASH_SOURCE[0]")/../.." 2>/dev/null && pwd)"
USER_CONFIG="$HOME/.config/magi-workflow/config.json"
If $USER_CONFIG is missing, tell the user to run /magi:setup first
(init needs output_language from there).
This skill does not require a git repo, but warns the user if not in one (a typical magi-workflow project will be).
1. Scan for missing files
Check existence of each well-known project file:
| Path | Tier | Role |
|---|---|---|
CLAUDE.md |
1 (root) | AI agent entry / instructions index |
README.md |
1 (root) | Human-readable project description |
SPEC.md |
1 (root) | Architecture & feature spec for AI agents |
magi/PRD.md |
2 (magi/) |
Product requirements |
magi/TECHSTACK.md |
2 (magi/) |
Tech stack constraints |
magi/BACKLOG.md |
2 (magi/) |
Pending items promoted from sprint DRIFT.md |
Build two lists:
- missing — files that don't exist
- existing — files that do exist (will be skipped, never modified)
Show the user both lists clearly.
If missing is empty, tell the user "project is already bootstrapped" and
suggest /magi:plan for next steps. Exit.
1.5. Context gathering (empty/new project detection)
After scanning, check whether this is a greenfield project (no existing code files beyond what magi-workflow creates):
code_files=$(find . -maxdepth 3 -type f \
-not -path './.git/*' \
-not -path './magi/*' \
-not -name 'CLAUDE.md' \
-not -name 'README.md' \
-not -name 'SPEC.md' \
-not -name '.gitignore' \
-not -name 'LICENSE' \
| head -5 | wc -l)
If code_files == 0 (empty/greenfield project), enter guided init mode:
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 · 322 lines · 76 tokens per session scan A 024b0a54c567
init is a skill published in the GitHub repository howar31/magi-workflow (2 stars, last pushed 3d ago), licensed MIT. It adds 76 tokens to every session and 2,385 once invoked, about $0.0004 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
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.
comfyui-node-registry
Authoring & publishing ComfyUI custom nodes to the Comfy Registry, covering node structure, pyproject.toml spec, comfy-cli publishing, and CI.
flux-txt2img
Build Flux txt2img workflows with Flux.1 Dev (SRPO), Flux 2 Klein 9B, Turbo LoRAs, FluxGuidance, and DualCLIPLoader patterns.
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).
chief-strategy-officer
Owns where the business plays and how it wins over a multi-year horizon — portfolio choices, corporate development, strategic partnerships, and planning under uncertainty. Use this for a decision about which markets or businesses to be in, whether to build, buy, or partner, how to allocate capital across business…
performance-analysis
Measurement approaches, profiling patterns, bottleneck identification, and optimization guidance. Use when diagnosing performance issues, establishing baselines, identifying bottlenecks, or planning for scale. Always measure before optimizing.