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-genome-authorgit 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-genome-author)<a href="https://agentmods.dev/skills/ashlrai/ashlr-plugin/ashlr-genome-author"><img src="https://agentmods.dev/badge/skills/ashlrai/ashlr-plugin/ashlr-genome-author/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-genome-author"><img src="https://agentmods.dev/badge/skills/ashlrai/ashlr-plugin/ashlr-genome-author.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.00056 | $0.00504 |
| Opus 5 | $0.00028 | $0.00252 |
| Sonnet 5 | $0.00011 | $0.00101 |
| Haiku 4.5 | $0.00006 | $0.00050 |
Grade A, and why
ashlr-genome-author 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 10d 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 Genome Author
The genome is the project's living architectural memory. ashlr__genome_propose adds new knowledge to it. This skill governs when and how to call it so the genome stays signal-rich.
When to call ashlr__genome_propose
Call it after:
- A new module is added — new file(s) that introduce a concept, service, or subsystem not previously in the genome.
- A schema change — database table added/dropped/migrated, or a core TypeScript interface redefined.
- An auth or security change — new middleware, permission model, token strategy, or RLS policy.
- A routing change — new API endpoint, route group, or server registered.
- An architectural decision — choosing a pattern, library, or data model that future contributors need to understand.
Summary format
Write a 2–5 sentence past-tense summary that describes:
- What was changed or added.
- Why (the intent or problem it solves).
- Where: end with the relevant file paths.
Example:
"Added
hooks/stop-accounting.tsto finalize session stats on the Stop event. This complements the existing SessionEnd GC path with an idempotency guard so duplicate entries are never written. Files:hooks/stop-accounting.ts,hooks/hooks.json."
When NOT to call ashlr__genome_propose
- Routine edits (bug fixes, typo corrections, test updates) that don't change the architecture.
- Edits to files already well-described in the genome with no structural change.
- Mid-task (wait until the change is complete and stable).
- More than once per logical change — one proposal per architectural event.
Section names
Use existing manifest section names when the change belongs to an existing area. Only introduce a new section name when the change is genuinely a new architectural concept.
Activation
Enable via /ashlr-genome-author on or by writing {"enabled":true} to ~/.ashlr/genome-author.json. Toggle off with /ashlr-genome-author off.
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.
- 10d ago First seen · 44 lines · 56 tokens per session scan A aa5ef83d4c0a
ashlr-genome-author is a skill published in the GitHub repository ashlrai/ashlr-plugin (3 stars, last pushed 3d ago), licensed MIT. It adds 56 tokens to every session and 504 once invoked, about $0.0003 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.
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.
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.
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…
echo
Before answering a substantive question, quietly check whether the user has already resolved this question in the past.
mirror
Weekly self-audit playback. Surface patterns from the user's past week that they probably cannot see themselves.