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/yopedianpx skills add yologdev/yoyo-evolve --skill yopediagit 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/yopedia)<a href="https://agentmods.dev/skills/yologdev/yoyo-evolve/yopedia"><img src="https://agentmods.dev/badge/skills/yologdev/yoyo-evolve/yopedia.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.01399 |
| Opus 5 | $0.00013 | $0.00700 |
| Sonnet 5 | $0.00005 | $0.00280 |
| Haiku 4.5 | $0.00003 | $0.00140 |
Grade A, and why
yopedia scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sS "$BASE/api/wiki/search?q=<keyword>&scope=agent:$AGENT_ID" How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Yopedia — your second brain
Yopedia (https://yopedia.yolog.dev) is your personal, persistent knowledge vault. Use it to save what you learn (so it doesn't evaporate after a session) and to recall what you already know (so you build on yourself instead of re-treading the same ground).
Setup (from env)
BASE=https://yopedia.yolog.dev
AGENT_ID="${YOPEDIA_AGENT_TOKEN%%.*}" # the token text before the dot, e.g. alice--yoyo
VAULT="$YOPEDIA_VAULT_ID" # which vault to file into — passed on every ingest
If $YOPEDIA_AGENT_TOKEN or $YOPEDIA_VAULT_ID is unset, your second brain isn't wired up
yet — skip ingestion/recall silently and carry on. A yopedia call must never
fail your actual work.
Recall FIRST
Before researching a topic, check what you already know and build on it. Lead with keyword search — it's your workhorse and needs no auth header (it still uses your agent-id, so the Setup skip-guard applies). Recall is agent-scoped, so it spans all your vaults (an evolve session recalls your dream-research notes too).
# 1. Keyword search (no auth) — YOUR MAIN RECALL.
# Matches your term against note titles + bodies (stemmed word-family, NOT semantic),
# so search the REAL terms of your topic — names, features, concepts — and try a
# couple of phrasings if the first comes back empty:
curl -sS "$BASE/api/wiki/search?q=<keyword>&scope=agent:$AGENT_ID"
# 2. Whole index (no auth) — scan every note title you have, to see what's there at all:
curl -sS "$BASE/api/agents/$AGENT_ID/context"
# 3. Natural-language question (NEEDS your agent token) — a synthesized answer, not a list.
# /api/query is authenticated; send the same token you ingest with. (Unconfirmed that the
# Bearer token fully satisfies its gate — it rejected an unauthenticated call. If #3 errors,
# just fall back to #1/#2.) Use when you want a digested answer rather than raw matches:
curl -sS -X POST "$BASE/api/query" \
-H "Authorization: Bearer $YOPEDIA_AGENT_TOKEN" -H "Content-Type: application/json" \
-d "{\"question\":\"What have I learned about <topic>?\",\"scope\":\"agent:$AGENT_ID\"}"
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 · 104 lines · 25 tokens per session scan A 530f8c025efe
yopedia is a skill published in the GitHub repository yologdev/yoyo-evolve (1,869 stars, last pushed today), licensed MIT. It adds 25 tokens to every session and 1,399 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
save
Save a user-selected answer, decision, insight, or session summary into an Obsidian vault as one reviewed transaction. Use only when the user explicitly asks to preserve specific conversation content, not when they supply a file or URL to ingest. Triggers: /save, save this, save that answer, file this conversation…
wiki-retrieve
Build and query a vault-local contextual BM25 retrieval index with optional multilingual Nomic cosine reranking; use for retrieve, hybrid retrieval, BM25, rerank, contextual retrieval, chunk search, vault search, semantic search, find relevant passages, or retrieval diagnostics. Derived caches stay under .vault-meta…
obsidian-bases
Explain, draft, and validate Obsidian Bases .base files with filters, formulas, properties, summaries, and table, card, or list views. Use for Obsidian Bases, database-like vault views, dynamic tables, reading lists, task trackers, filters, formulas, summaries, and .base file edits.
wiki-fold
Create a bounded, extractive, structurally idempotent rollup of recent Obsidian wiki log entries, with dry-run preview by default and one optional transaction apply. Use for manual log compression without modifying child pages. Triggers: fold the log, run a fold, run wiki-fold, log rollup, roll up log entries, commit…
wiki-mode
Read or configure the vault filing methodology and suggest destinations for planned knowledge creation under Generic, LYT, PARA, or Zettelkasten. Use for wiki mode, methodology mode, what is my vault mode, set vault mode, switch to PARA, use LYT, Zettelkasten setup, change mode, configure mode, or methodology routing.…
wiki-cli
Detect and use the official Obsidian command-line interface for read-only vault access; use for wiki-cli, Obsidian CLI, Obsidian read, Obsidian search, vault transport, which transport, transport detection, backlinks, tags, or Obsidian command line. Mutations always go through the claude-obsidian transaction core.