Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add ashlrai/ashlr-plugin/plugin install ashlrWrote 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/commands/ashlrai/ashlr-plugin/ashlr-genome-init)<a href="https://agentmods.dev/commands/ashlrai/ashlr-plugin/ashlr-genome-init"><img src="https://agentmods.dev/badge/commands/ashlrai/ashlr-plugin/ashlr-genome-init.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.00040 | $0.00251 |
| Opus 5 | $0.00020 | $0.00125 |
| Sonnet 5 | $0.00008 | $0.00050 |
| Haiku 4.5 | $0.00004 | $0.00025 |
Grade A, and why
ashlr-genome-init 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.
What it actually says
Initialize a genome for the user's current project.
Run the following Bash command:
bun run ${CLAUDE_PLUGIN_ROOT}/scripts/genome-init.ts --dir "$(pwd)"
Pass --force only if the user explicitly asks to overwrite an existing genome.
Pass --minimal only if the user asks to skip the auto-populated architecture/conventions sections.
Pass --summarize if the user wants to use a local Ollama model to generate concise CLAUDE.md summaries instead of truncating. Requires Ollama running locally — falls back gracefully to truncation if unavailable.
After the command runs:
- Relay the script's stdout verbatim as the response.
- If the script exits non-zero because a genome already exists, tell the user to re-run with
/ashlr-genome-init --forceonly if they confirm they want to overwrite. - Do not read or modify any generated files unless the user asks.
No preamble, no trailing summary beyond the script's output.
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 · 25 lines · 40 tokens per session scan A 287238532f6b
ashlr-genome-init is a command published in the GitHub repository ashlrai/ashlr-plugin (3 stars, last pushed 6d ago), licensed MIT. It adds 40 tokens to every session and 251 once invoked, about $0.0002 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-31.
Other commands, from other repositories
apply
Apply a saved recipe — provision every provider in it and wire secrets + MCP entries. Usage — /stack:apply.
recommend
Recommend providers for a goal and save the result as a reusable recipe. Usage — /stack:recommend.
add
Provision a service and wire its secrets + MCP entry. Usage — /stack:add.
list
List services configured in this stack.
status
Show a one-screen overview of the current stack.
create-plugin
Guided end-to-end plugin creation workflow with component design, implementation, and validation.