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/yolonpx skills add howar31/magi-workflow --skill yologit clone --depth 1 https://github.com/howar31/magi-workflowWrote 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/howar31/magi-workflow/yolo)<a href="https://agentmods.dev/skills/howar31/magi-workflow/yolo"><img src="https://agentmods.dev/badge/skills/howar31/magi-workflow/yolo.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.00117 | $0.03610 |
| Opus 5 | $0.00059 | $0.01805 |
| Sonnet 5 | $0.00023 | $0.00722 |
| Haiku 4.5 | $0.00012 | $0.00361 |
Grade A, and why
yolo 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 4d 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 — 312 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/magi:yolo — headless full-pipeline runner
You are the coordinator. The user has invoked /magi:yolo because they
want the full pipeline executed without any prompts — they're walking
away. Run plan → tasks → work → review-code → commit (and optionally
push) in one shot. Never ask for user input after launch.
This skill is intentionally separate from the normal workflow. It violates the "顯式優先" design principle on purpose, scoped to opt-in use. Decisions that would normally pause for user confirmation are auto-resolved with the most conservative non-destructive default.
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 config missing → abort with "/magi:setup required".
Confirm we are inside a git repo:
git rev-parse --git-dir >/dev/null 2>&1 || { echo "not a git repo"; exit 1; }
0.5. State preflight (auto-refuse)
STATE_JSON=$(bash "$PLUGIN_ROOT/scripts/shared/detect-state.sh")
blocked=$(jq -r '.disallowed_skills["yolo"] // empty' <<<"$STATE_JSON")
if [[ -n "$blocked" ]]; then
reason=$(jq -r '.disallowed_skills["yolo"].reason' <<<"$STATE_JSON")
suggest=$(jq -r '.disallowed_skills["yolo"].suggest' <<<"$STATE_JSON")
echo "Cannot run /magi:yolo: $reason"
echo "Suggested: $suggest"
exit 1
fi
Yolo is refused only in BOOTSTRAP (suggest /magi:init first).
0.6. Mode determination (fresh vs resume)
Yolo has two modes, mutually exclusive, determined by arguments:
| Invocation | Mode | Behavior |
|---|---|---|
/magi:yolo "<description>" |
Fresh | Create new sprint, run full pipeline plan→...→commit |
/magi:yolo --resume [--sprint <slug>] |
Resume | Pick up an existing sprint (latest by default, or --sprint) from its current state, skipping phases already done |
/magi:yolo (no description, no --resume) |
error | Print usage hint and abort |
/magi:yolo "<desc>" --resume |
error | Mutually exclusive |
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.
- 4d ago First seen · 312 lines · 117 tokens per session scan A 2e05841f2cdf
yolo is a skill published in the GitHub repository howar31/magi-workflow (2 stars, last pushed 5d ago), licensed MIT. It adds 117 tokens to every session and 3,610 once invoked, about $0.0006 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
seo-strategy
Audits and improves organic search performance — technical health, site architecture, internal linking, structured data, and the content decisions that determine what can rank. Use this to run an SEO audit, diagnose why pages are not ranking or were deindexed, plan a site's URL and navigation structure, add structured…
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…
scenario-planning
Plans under genuine uncertainty — building scenarios, identifying which assumptions are load-bearing, setting early-warning indicators, and stress-testing a plan against futures rather than forecasting one. Use this when a decision depends on something unknowable, when a plan assumes conditions that may not hold…
ai-ml-governance
Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory…
ai-research-analyst
Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a…
support-operations
Designs and runs the support function — channels, queues, routing, staffing, service levels, quality, and the metrics that show whether it is working. Use this to set up or fix support operations, choose channels, size a team, set or renegotiate service levels, reduce cost per contact, diagnose long queues or poor…