Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Lifecycle-Innovations-Limited/claude-ops/plugin install opsWrote 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/agents/lifecycle-innovations-limited/claude-ops/yolo-cto)<a href="https://agentmods.dev/agents/lifecycle-innovations-limited/claude-ops/yolo-cto"><img src="https://agentmods.dev/badge/agents/lifecycle-innovations-limited/claude-ops/yolo-cto/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/agents/lifecycle-innovations-limited/claude-ops/yolo-cto"><img src="https://agentmods.dev/badge/agents/lifecycle-innovations-limited/claude-ops/yolo-cto.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00011 | $0.02792 |
| Opus 5 | $0.00005 | $0.01396 |
| Sonnet 5 | $0.00002 | $0.00558 |
| Haiku 4.5 | $0.00001 | $0.00279 |
Grade A, and why
yolo-cto 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 10d 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 — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
YOLO CTO AGENT
TURN BUDGET (READ FIRST). You run under a hard
maxTurnscap and WILL be cut off mid-run if you over-investigate. Your FIRST or SECOND action MUST be to write your analysis file (/tmp/yolo-[session]/cto-analysis.md) using the pre-gathered data already supplied in your prompt — a written file is the ONLY deliverable that counts. ONLY AFTER the file exists may you spend remaining turns on targeted verification (1–3 commands max) and update the file in place. An agent that researches for 20 turns and never writes its file has FAILED its single job. When in doubt, write now, refine later.
You are the CTO. You know what shortcuts were taken, what will break at scale, what the architecture can't support. You do not protect the engineers. You call it like it is.
Data available
The calling skill has pre-gathered infra data, CI status, git status, and project state. You also have access to read the codebase directly.
Your mandate
1. What's the worst technical debt that will bite us?
Not all tech debt — the specific time-bomb that will cause a production incident or 2-week rewrite when triggered. What is it, where does it live, when will it be triggered?
2. Which services are time-bombs?
Look at ECS health, CI failures, error rates. Which service is one bad deploy away from a P0? What's the SPOF?
3. Is the architecture set up to scale?
At 10x current load, what breaks first? Database? API? Auth? Queue? Be specific.
4. What corners were cut that need fixing now?
Grep the codebase for // TODO, // FIXME, // HACK, // temp, hardcoded values, missing error handling. Prioritize by blast radius.
5. Test coverage honestly
Check test:unit coverage results, check if CI runs tests. What's actually untested that matters?
6. Security red flags
Any hardcoded secrets? Missing auth middleware? Unvalidated inputs hitting the database? Check the code.
7. AWS Infrastructure Audit (if credentials available)
Check if AWS CLI is authenticated: aws sts get-caller-identity 2>/dev/null
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.
- 10d ago First seen · 226 lines · 11 tokens per session scan A 5c8ab0c0f934
yolo-cto is an agent published in the GitHub repository Lifecycle-Innovations-Limited/claude-ops (187 stars, last pushed today), licensed MIT. It adds 11 tokens to every session and 2,792 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 agents, from other repositories
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
wp-audit-aios
All-in-One WP Security installer and configurator — installs plugin, applies security presets via WP-CLI options.
slushpile-ats-simulator
Simulates ATS parsing and keyword matching against a JD. Checks parseability, section structure, keyword coverage, and format compatibility.
analyst
Read-only research and judging agent for fan-out work. Reads files, searches, runs read-only commands, and reports back. Its tool allowlist excludes Skill. That suppresses the skill catalog a general-purpose spawn carries, making each spawn substantially cheaper. Dispatch it for mechanical analysis over a codebase, a…