yoyo-evolve is a terminal coding agent that reads and changes its own Rust source code, runs tests, and commits its improvements. It is for users who want an autonomous agent that can navigate codebases, edit multiple files, run tests, manage Git, and recover from failures. The catalogue entries are skills for working with this coding agent.
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/yologdev/yoyo-evolve/blindspotnpx skills add yologdev/yoyo-evolve --skill blindspotgit clone --depth 1 https://github.com/yologdev/yoyo-evolveWrote 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/yologdev/yoyo-evolve/blindspot)<a href="https://agentmods.dev/skills/yologdev/yoyo-evolve/blindspot"><img src="https://agentmods.dev/badge/skills/yologdev/yoyo-evolve/blindspot.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.1 | $0.00025 | $0.02137 |
| Opus 5 | $0.00013 | $0.01069 |
| Sonnet 5 | $0.00005 | $0.00427 |
| Haiku 4.5 | $0.00003 | $0.00214 |
Grade A, and why
blindspot 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 6d 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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Blindspot
You are performing a structured critique of code, architecture, or systems. Your job is to find what the author can't see — the gaps that familiarity hides, the risks that daily use normalizes, the debt that accumulates silently.
This is not a linter. Linters catch syntax and style. You catch design decisions that will hurt later — the unwrap() that will panic in production, the O(n²) that's fine with 10 items but fatal with 10,000, the API that can't evolve without breaking clients.
When to use
- During evolution self-assessment (proactive self-critique)
- On-demand via
/skill run blindspotwith a target - When reviewing unfamiliar code before modifying it
- After a feature is "done" — the last-mile audit
- When a community issue reports a class of problem (search for siblings)
When NOT to use
- For style/formatting issues (use clippy/rustfmt)
- When you need to understand code before critiquing it (use
explore-codebasefirst) - For single-line fixes you can see directly (just fix them)
Parameters
Target
What to analyze. One of:
- A file path:
src/tools.rs - A directory:
src/format/ - A module or concept: "error handling in the REPL"
self— yoyo's own codebase (defaults tosrc/)
Roast level
Controls the threshold for reporting:
- gentle — Critical and Warning only. For when you want actionable items without noise.
- standard (default) — Critical + Warning + Smell. The balanced default.
- brutal — Everything, including nitpicks. For when you want the full picture.
Analysis Dimensions
Examine the target through these lenses:
1. Error handling gaps
unwrap()/expect()on fallible operations in non-test code- Functions that return
Ok(())but swallow errors silently - Missing error context (bare
?without.context()or.map_err()) - Panic paths reachable from user input
- Error types that lose information (stringly-typed errors)
2. Security blind spots
- Hardcoded secrets, tokens, or credentials
- User input passed to shell commands without sanitization
- Path traversal vulnerabilities (unchecked
../) - Unsafe blocks without safety comments
- Dependencies with known vulnerabilities
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.
- 6d ago First seen · 223 lines · 25 tokens per session scan A 7617e6c70993
blindspot is a skill published in the GitHub repository yologdev/yoyo-evolve (1,870 stars, last pushed today), licensed MIT. It adds 25 tokens to every session and 2,137 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…