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/x-researchnpx skills add yologdev/yoyo-evolve --skill x-researchgit 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/x-research)<a href="https://agentmods.dev/skills/yologdev/yoyo-evolve/x-research"><img src="https://agentmods.dev/badge/skills/yologdev/yoyo-evolve/x-research.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.00027 | $0.02938 |
| Opus 5 | $0.00014 | $0.01469 |
| Sonnet 5 | $0.00005 | $0.00588 |
| Haiku 4.5 | $0.00003 | $0.00294 |
Grade A, and why
x-research 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.
- **General web research** — use the `research` skill instead (curl + DuckDuckGo) How it starts
The opening of the file, as written. The whole thing — 269 lines — stays where its author put it; the contents beside it link to each section on GitHub.
X Research
Read-only access to X (Twitter) through xurl. Use this when you need to know what people are saying on X about a topic, read a specific thread, check someone's recent posts, or read long-form X Articles.
When to Use
- Researching what people on X are saying about a topic (an API, a tool, a trend)
- Reading a specific thread or conversation for context
- Checking a profile's recent posts (e.g., what has @someone been saying about Rust?)
- Reading long-form X Articles
- Gathering community sentiment before making a decision
When NOT to Use
- General web research — use the
researchskill instead (curl + DuckDuckGo) - Posting, liking, following, DMing — this skill is read-only, always
- Bulk historical scraping — the API has rate limits and this isn't an archival tool
- Real-time monitoring or streaming — one-shot queries only
- Anything that modifies state on X — never, under any circumstances
Prerequisites
Two auth modes are supported. Detect which one applies first, then use the x_get helper for every request — never call xurl GET or curl directly inline, or CI mode will silently fail (xurl has no ~/.xurl on a runner).
# Auth mode detection — run this once at the top of the session:
if [ -n "$X_BEARER_TOKEN" ]; then
AUTH_MODE=ci
elif command -v xurl &>/dev/null && [ -d "$HOME/.xurl" ]; then
AUTH_MODE=local
else
have_xurl=$(command -v xurl >/dev/null 2>&1 && echo yes || echo no)
have_xurl_dir=$([ -d "$HOME/.xurl" ] && echo yes || echo no)
have_token=$([ -n "$X_BEARER_TOKEN" ] && echo yes || echo no)
echo "x-research: auth not configured; skill unavailable this session" >&2
echo " X_BEARER_TOKEN set: $have_token" >&2
echo " xurl on PATH: $have_xurl" >&2
echo " ~/.xurl exists: $have_xurl_dir" >&2
exit 1
fi
CI mode (AUTH_MODE=ci) — $X_BEARER_TOKEN is set (provisioned by the CI workflow as a repo secret). Calls go through curl with an Authorization: Bearer header. Tokens come from the X developer portal as App-only Bearer tokens, which are read-only (cannot post, like, DM, or act as a user). Don't paste a user OAuth2 access token into this secret — x_get won't validate token type, but a user token would expose write capability the skill is not designed to use.
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 · 269 lines · 27 tokens per session scan A e55347b99705
x-research is a skill published in the GitHub repository yologdev/yoyo-evolve (1,869 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 2,938 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
x-mcp
Connect a user's own X (Twitter) dev app (BYOK) for the official X API MCP (reads) plus X v2 REST writes — post, reply, like, retweet, DM. Use when the user wants to act on X with their OWN X account or app — search, read timeline/users/news/trends/bookmarks via MCP, and post/reply/like/retweet/DM via REST. Walks…
x_intel
Read X (Twitter) posts, search, timelines and user profiles via the official xurl CLI.
X Research
Research X/Twitter discourse with live search, profile reads, thread follow-up, and watchlists when the user wants sourced, current sentiment or expert takes without posting.
X
Operate on X/Twitter through the canonical Home23 X skill. Uses the logged-in bird browser session by default; official API access is explicit opt-in.
Read and post on X/Twitter from the CLI - fetch tweets, timelines, and search; post tweets, replies, threads, and media. Cookie-based auth via twikit, bootstrapped from the local Dia browser session, secrets stored in gopass. Auto-falls back to agent-browser when twikit hits internal-API drift or X's "looks automated"…
codex-interactive-capability-map
Turn a long-form article, thread, memo, or product narrative into a compact clickable capability map with a workflow loop, use-case matrix, and responsive detail panel.