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.
git clone --depth 1 https://github.com/CoriChui/yoloWrote 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/plugins/corichui/yolo/yolo)<a href="https://agentmods.dev/plugins/corichui/yolo/yolo"><img src="https://agentmods.dev/badge/plugins/corichui/yolo/yolo/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/plugins/corichui/yolo/yolo"><img src="https://agentmods.dev/badge/plugins/corichui/yolo/yolo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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 1mo 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.
What it actually says
{
"name": "yolo",
"description": "Reasoning-first, feature-aware development workflow for Claude Code. Git is the source of truth; status is derived, never stored. Turns 'I want X' into a planned, executed, verified, and landed change through eleven yolo-* skills Claude routes to from plain intent.",
"version": "0.4.0",
"author": { "name": "Konstantin Tsoy" },
"homepage": "https://github.com/CoriChui/yolo",
"repository": "https://github.com/CoriChui/yolo",
"license": "MIT",
"keywords": ["workflow", "claude-code", "spec-driven", "feature-development", "git", "agent", "skills"],
"skills": "./.claude/skills/",
"commands": "./.claude/commands/"
}
What it installs
The manifest is a name and a version. 11 skills, 1 command travel with it, and installing the plugin installs all of them — 799 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill yolo-plan A 55 tokens
- Skill yolo-feature A 60 tokens
- Skill yolo-finish A 82 tokens
- Skill yolo-debug A 68 tokens
- Skill yolo-status A 47 tokens
- Skill yolo-decide A 55 tokens
- Skill yolo-init A 78 tokens
- Skill yolo-intake A 118 tokens
- Skill yolo-verify A 62 tokens
- Skill yolo-research A 69 tokens
- Skill yolo-roadmap A 70 tokens
- Command yolo-validate A 35 tokens
What ships with it
1 file beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 13 lines scan A 9880a9a4b98a
yolo is a plugin published in the GitHub repository CoriChui/yolo (9 stars, last pushed 3mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
rami
AI code review for Claude Code and Codex. Reviews every PR, fixes issues via MCP, you decide what merges.
dark-factory
Curie's default dark factory agent: one labelled GitHub issue in, one reviewed pull request or one stated reason out. One agent reads the issue through the platform's getissue tool, pins acceptance criteria, plans, gets the plan reviewed by an Opus plan-reviewer subagent, writes a failing test where feasible, implemen.
github-activity
Read-only GitHub activity reporter for program managers. One hosted connector reads merged pull requests, opened and closed issues, and milestone movement across several repositories since a point in time. It holds no write tool, the tool policy allows only the read tool so anything else fails closed, and the…
privacy-guard
Keeps private infrastructure details out of public repositories. Ships the privacy-guard skill: session rules for what must never cross the public boundary, plus a per-repo pre-commit gate built on a gitignored local denylist and gitleaks. The denylist is never committed, so the hook is a no-op for external…
github-workflow
Git commit, PR creation, review, and merge skills following Conventional Commits.
issue-to-pr
Take a GitHub issue (bare, or tracked on a Project board) from triage to a merge-ready PR through a gated, worktree-isolated pipeline that scales its depth to the task and asks at most one batched question. The gates hold every run: design hardening, tests green, code review clean. Once you approve the PR in-session…