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 skills add CyrusNuevoDia/gepa-research --skill discovergit clone --depth 1 https://github.com/CyrusNuevoDia/gepa-researchWrote 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/cyrusnuevodia/gepa-research/discover)<a href="https://agentmods.dev/skills/cyrusnuevodia/gepa-research/discover"><img src="https://agentmods.dev/badge/skills/cyrusnuevodia/gepa-research/discover/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/skills/cyrusnuevodia/gepa-research/discover"><img src="https://agentmods.dev/badge/skills/cyrusnuevodia/gepa-research/discover.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.00084 | $0.06510 |
| Opus 5 | $0.00042 | $0.03255 |
| Sonnet 5 | $0.00017 | $0.01302 |
| Haiku 4.5 | $0.00008 | $0.00651 |
Grade A, and why
discover 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 12d 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 — 397 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Discover
Internal procedure for gepa-research:discover. The user only sees the user-facing prompts, the dashboard URL, and the baseline score -- everything else is the agent's choreography.
Host conventions
This skill runs on any host that implements the Agent Skills spec. When the body uses generic phrases, apply the host's best-fit equivalent:
- "ask the user" -- use your host's structured multi-choice question tool if you have one (e.g.
AskUserQuestion,request_user_input). If the host has none, phrase the question as plain text in your next reply and wait for the user's answer. - File paths like
references/...-- relative to thisSKILL.md; resolve from the skill directory. - Slash commands shown in user-facing copy (e.g.
/gepa-research:discover) -- translate to your host's mention syntax when speaking to the user (e.g.$gepa-research discoveron Codex -- plugin namespace then skill name, separated by a space).
0. Verify the gepa-research CLI is available and in sync with the plugin
Before anything else, run:
gepa-research-version-check
This wraps gepa-research --version and additionally asserts the installed CLI matches the plugin manifest version (hosts refetch the plugin on version bumps, but do not reinstall the globally-installed CLI -- drift between the two breaks skills silently).
Four outcomes to handle:
- Exit 0,
gepa-research-version-check: OK (plugin=X, cli=X)-- continue to step 1. - Exit 1, "plugin manifest and installed CLI disagree" -- stop and show the user the script's stderr verbatim; it tells them the
uv tool install --force "git+https://github.com/CyrusNuevoDia/gepa-research@v<version>#subdirectory=plugins/gepa-research"command to run. Then re-invoke this skill. - Exit 2, "gepa-research CLI not on PATH" -- stop and tell the user:
gepa-research-cliisn't on your PATH. Install it once from GitHub:uv tool install "git+https://github.com/CyrusNuevoDia/gepa-research#subdirectory=plugins/gepa-research"(or substitutepipx installforuv tool install). Then re-invoke this skill. gepa-research-version-check: command not found-- the host's plugin install is incomplete (missing thebin/wrapper). Fall back to runninggepa-research --versiondirectly and check forgepa-research-cliin the output; if it's a different package, tell the user to uninstall it and installgepa-research-clifrom GitHub in its place (uv tool install "git+https://github.com/CyrusNuevoDia/gepa-research#subdirectory=plugins/gepa-research").
What ships with it
7 files beside SKILL.md 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.
- references/constructing-benchmark.md 11 KB
- references/inline_instrumentation.js 2.4 KB runs code
- references/inline_instrumentation.py 2.9 KB runs code
- references/proposing-dimensions.md 4.2 KB
- references/sdk_node.js 954 B runs code
- references/sdk_python.py 1.1 KB runs code
- scripts/validate_stdout.py 2.0 KB runs code
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.
- 12d ago First seen · 397 lines · 84 tokens per session scan A c3970d4b1f12
discover is a skill published in the GitHub repository CyrusNuevoDia/gepa-research (100 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 84 tokens to every session and 6,510 once invoked, about $0.0004 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
autocontext-consumer
Use when an agent needs to USE knowledge Autocontext already produced - find which scenarios have knowledge, read the playbook and lessons for one, understand the on-disk file and folder layout, and move knowledge between checkouts. Host-agnostic; requires only the autoctx CLI and the filesystem.
autocontext-creator
Use when an agent needs to CREATE knowledge with Autocontext - run a scenario or plain-language task through the improvement loop, judge or improve a single output, and inspect what the run produced. Host-agnostic; requires only the autoctx CLI.
create-notes
Write a note to {shareddir}/notes/ that future agents can actually act on. Use after every coral eval, when a heartbeat (reflect / consolidate / pivot) asks for a note, or when you discover a grader / build / runtime issue that future agents will hit. Covers 4 note variants (experiment / infra / focus / synthesis)…
skill-creator
Autonomously create, test, and optimize skills by detecting reusable patterns in your own work. Use when you notice repeated tool sequences, recurring code patterns across attempts, or insights that should be captured as a packaged skill. Also use to benchmark and iterate on existing skills.
arbor-research-agent
Public entrypoint for the Arbor skill suite. Use when a user wants to run an Arbor-style autonomous research or optimization workflow from a natural-language goal, including initial clarification of objective, target project, data, metric, evaluation, permissions, budget, run mode, and then automatic bootstrapping…
deep-research
Research the problem domain before coding. Web search for techniques, save raw sources, write structured findings, update the index.