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 ashlrai/ashlr-plugin --skill ashlr-codex-genome-refreshgit clone --depth 1 https://github.com/ashlrai/ashlr-pluginWrote 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/ashlrai/ashlr-plugin/ashlr-codex-genome-refresh)<a href="https://agentmods.dev/skills/ashlrai/ashlr-plugin/ashlr-codex-genome-refresh"><img src="https://agentmods.dev/badge/skills/ashlrai/ashlr-plugin/ashlr-codex-genome-refresh/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/ashlrai/ashlr-plugin/ashlr-codex-genome-refresh"><img src="https://agentmods.dev/badge/skills/ashlrai/ashlr-plugin/ashlr-codex-genome-refresh.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.00036 | $0.00152 |
| Opus 5 | $0.00018 | $0.00076 |
| Sonnet 5 | $0.00007 | $0.00030 |
| Haiku 4.5 | $0.00004 | $0.00015 |
Grade A, and why
ashlr-codex-genome-refresh 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 8d 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
Ashlr Codex Genome Refresh
After meaningful architecture changes, refresh project memory:
ashlr genome-refresh --json
When an MCP genome tool is available, prefer the direct tool:
ashlr__genome_statusto inspect current genome stateashlr__genome_proposefor a concise update proposalashlr__genome_consolidateafter reviewing pending proposals
Do not propose routine typo fixes or test-only changes. One proposal per logical architectural change is enough.
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.
- 8d ago First seen · 21 lines · 36 tokens per session scan A c277a286b22a
ashlr-codex-genome-refresh is a skill published in the GitHub repository ashlrai/ashlr-plugin (3 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 152 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 skills, from other repositories
cco-patterns
Share learned file patterns across a team — export an anonymized digest of what's usually waste/useful/co-edited, and import a teammate's so a fresh clone benefits day one.
mirror
Weekly self-audit playback. Surface patterns from the user's past week that they probably cannot see themselves.
overheard
Find commitments the user made in the last two weeks and did not follow through on. A promises audit.
dream
Prunes and consolidates the project's auto-memory to keep it minimal — deletes stale, wrong, or redundant memories, merges overlapping ones into existing files, and trims the index. Strong bias against growth: never creates new memory files and never stores new facts. Verifies staleness against the current codebase…
team-memory-protocol
A shared-memory process for teams of coding agents working on the same build. It stores project knowledge, shared context, and task progress in separate files or repositories.
knowledge-wiki
A tool that turns useful lessons from coding sessions into general articles for a team wiki. A wiki is a collection of linked reference pages, and this one can be kept locally or shared through a Git repository.