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 danielmeppiel/genesis --skill genesis-evalsgit clone --depth 1 https://github.com/danielmeppiel/genesisWrote 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/danielmeppiel/genesis/genesis-evals)<a href="https://agentmods.dev/skills/danielmeppiel/genesis/genesis-evals"><img src="https://agentmods.dev/badge/skills/danielmeppiel/genesis/genesis-evals/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/danielmeppiel/genesis/genesis-evals"><img src="https://agentmods.dev/badge/skills/danielmeppiel/genesis/genesis-evals.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.00195 | $0.02561 |
| Opus 5.5 | $0.00078 | $0.01024 |
| Sonnet 5.5 | $0.00039 | $0.00512 |
| Haiku 4.5 | $0.00019 | $0.00256 |
Grade A, and why
genesis-evals 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 1mo 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 — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
genesis-evals: maintainer-side eval runner
Run the genesis self-eval suite. Steers the parent LLM session to orchestrate cold sub-agent spawns, capture responses, score deterministically, and report convergence.
Why this lives outside .apm/
Genesis ships to USERS via npx / apm install. Eval scenarios LOOK
LIKE real user requests (that is the point). Colocating them under
skills/genesis/evals/ would risk DISPATCH CONTAMINATION (an
over-eager harness loader pulling scenario prompts into the active
context) and PAYLOAD BLOAT for users who never run evals.
We also keep this OUTSIDE .apm/ because APM treats .apm/ as the
publishable source root: its local-content scanner picks up anything
under .apm/skills/ regardless of dev-marker, so apm pack --format plugin would leak this maintainer-only skill into the
shipped artifact. Living under dev/skills/ keeps it scanner-invisible
while still letting apm install --dev deploy it via the local-path
devDependency in the root apm.yml.
This is the inverse of PHANTOM DEPENDENCY (referenced-but-not-bundled):
BUNDLE LEAKAGE (bundled-but-not-consumed-at-runtime). See
skills/genesis/assets/composition-substrate.md "Anti-patterns
flagged at this step".
When to activate
- Validating a genesis PR before merge
- Any change to a file under
skills/genesis/(catalogue or SKILL.md) - Operator says "run evals", "regenerate eval matrix", "score on Opus"
- Adding a new scenario (run validate first)
Hard rules
- The
model:field in every scenario YAML is REQUIRED. The runner REFUSES to spawn if missing. No silent default. The model is the single biggest variable in eval results. - Pre-spawn: ALWAYS call
spawn_record.pyto write the immutable<id>__<half>.spawn.jsonBEFORE invoking the harness's task tool. This is the source of truth for "what we asked for". - Cold spawn: each (scenario, half) is a SEPARATE task-tool call with fresh context. Never reuse a session across scenarios.
- Determinism: scoring is python (
score_run.py), not LLM-judged. Pass gates are substring matches against the schema. - Scenarios are FROZEN once landed. Removing a scenario requires
setting
retired_in: <version>(never deletion). - After 3 iteration loops without convergence, escalate via B10 HUMAN CHECKPOINT. Do NOT loop indefinitely.
What ships with it
21 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.
- .gitignore 7 B
- requirements.txt 28 B
- runs/.gitignore 29 B
- scenarios/n-001-debug-bug.yml 1012 B
- scenarios/n-002-write-doc.yml 895 B
- scenarios/n-003-explain-concept.yml 619 B
- scenarios/n-004-cost-near-miss.yml 1008 B
- scenarios/p-001-a10-recognition.yml 874 B
- scenarios/p-002-soc-extraction.yml 1.1 KB
- scenarios/p-003-panel-fanout.yml 908 B
- scenarios/p-004-a12-gradient-workflow.yml 1.1 KB
- scenarios/p-005-b13-cache-invalidator.yml 1.1 KB
- scenarios/p-006-r5-cost-prune.yml 991 B
- scenarios/p-007-cost-stance-projection.yml 1019 B
- scenarios/p-008-b12-model-router.yml 1.0 KB
- scenarios/r-001-substrate-validation.yml 1022 B
- scenarios/r-002-substrate-implied-not-github.yml 936 B
- schema/scenario.schema.json 2.4 KB
- scripts/score_run.py 5.6 KB runs code
- scripts/spawn_record.py 2.7 KB runs code
- scripts/validate_scenarios.py 2.2 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.
- 1mo ago First seen · 259 lines · 195 tokens per session scan A c5fa0d887470
genesis-evals is a skill published in the GitHub repository danielmeppiel/genesis (77 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 195 tokens to every session and 2,561 once invoked, about $0.0008 per session on Opus 5.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
adept-writing-tests
How to write tests in the adept Go codebase — table-driven tests with testify, golden fixtures under testdata/, the cmd/adept e2e harness, temp-dir/HOME isolation, and coverage gates. Apply when adding or changing Go tests here. (matches: /test.go).
foundry-hosted-agent-validation
Step-by-step process for validating a Python Foundry hosted agent sample (under python/samples/04-hosting/foundry-hosted-agents/) end to end — running it locally (native runtime and azd ai agent run) and after deploying it to an Azure AI Foundry project with azd. Use this when asked to validate a hosted agent sample.
build-and-test
How to build and test .NET projects in the Agent Framework repository. Use this when verifying or testing changes.
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
ios-simulator
Verify and debug native, React Native, Expo, or Flutter apps on an iOS Simulator with agent-device. Use when an agent needs to launch an app, inspect its live UI, tap, type, scroll, validate a code change, collect failure evidence, or reproduce a workflow on an iPhone or iPad Simulator.