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 larsboes/Axon --skill trimgit clone --depth 1 https://github.com/larsboes/AxonWrote 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/larsboes/axon/trim)<a href="https://agentmods.dev/skills/larsboes/axon/trim"><img src="https://agentmods.dev/badge/skills/larsboes/axon/trim/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/larsboes/axon/trim"><img src="https://agentmods.dev/badge/skills/larsboes/axon/trim.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.00136 | $0.01532 |
| Opus 5 | $0.00068 | $0.00766 |
| Sonnet 5 | $0.00027 | $0.00306 |
| Haiku 4.5 | $0.00014 | $0.00153 |
Grade A, and why
trim 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 9d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
trim
Every byte in an always-on file is paid on every session, forever. This skill measures that cost, removes what is provably dead, and then makes the judgment calls one at a time in front of the person whose rules they are.
Adapted from the Trim skill in LifeOS by Daniel Miessler (https://github.com/danielmiessler/LifeOS), MIT.
Procedure
Copy this checklist and track progress:
- [ ] 1. Measure
- [ ] 2. Make the edit reversible
- [ ] 3. Remove what is provably dead
- [ ] 4. Propose the semantic moves, one at a time
- [ ] 5. Run the safety gate
- [ ] 6. Re-measure and report
1 — Measure. Never start from an impression of which file is too big.
bun scripts/measure-context.ts --root "$PWD"
It resolves the always-on set — ~/.claude/CLAUDE.md, the project CLAUDE.md and AGENTS.md,
every @-import they pull in, and the memory index for this project — and reports bytes, an
approximate token count, the largest sections, dead pointers and directives duplicated across two
always-on files. Show the totals to the user before proposing anything. Without a target size,
"smaller" has no end.
2 — Make it reversible. Before the first edit:
- The file is in a git repository — check
git status --shorton that path. Clean means the repository is the undo. Dirty means say so and ask before touching it; a trim mixed into somebody else's uncommitted work cannot be reverted on its own. - The file is not in a repository — this is the normal case for
~/.claude/CLAUDE.md. Copy it to<file>.bak-<UTC timestamp>and print the exactcpcommand that restores it. Do this once, before the first edit, not per move.
3 — Remove what is provably dead. These need no judgment, so they are free. Take them all before proposing anything that costs attention:
- Dead pointers. A rule that points at a file which no longer exists has no reader. Delete the rule, or repair the pointer when the file merely moved — say which, and how you checked.
- Duplicated directives. A line loaded by two always-on files is paid twice. Keep the copy in the narrower scope, delete the other, and say which one survived.
- Rules about things that no longer exist. A tool, a path, a service, a workflow that is gone.
Check before claiming it:
ls, the repository, the deployment ledger. An unverified "this looks obsolete" is not a deterministic removal, it is a semantic one, and it belongs in step 4.
What ships with it
2 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.
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.
- 9d ago First seen · 116 lines · 136 tokens per session scan A 593575ddd936
trim is a skill published in the GitHub repository larsboes/Axon (1 stars, last pushed yesterday), licensed MIT. It adds 136 tokens to every session and 1,532 once invoked, about $0.0007 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-09-07.
Other skills, from other repositories
reflect
Use Recall Reflect to review AI coding workflow history as a conversation-first timeline and discuss observed patterns before changing behavior. Trigger when the user asks to reflect on a project, review AI coding workflow, inspect workflow friction, discuss repeated corrections, review handoffs, or explore possible…
notion
Read, create, and update Notion pages and databases via the Notion REST API.
any-mcp
Use when an agent needs to read, search, create, edit, organize, upload, or chat with Anytype through the bounded any-mcp server. Covers safe tool selection, exact identifier chaining, optional toolsets, common PKM workflows, and the narrow anyr fallbacks for chat subscriptions and rich chat blocks.
yaps-dictation
Set up, use, diagnose, or recover system-wide Yaps voice dictation for Claude Code, Codex, and other desktop apps. Trigger for voice typing, speech input, hands-free writing, dictating into an AI client, routing dictation through Yaps, fixing a Yaps microphone/shortcut/paste problem, or recovering a recent Yaps…
recap
Summarize the last N agent sessions for the current project, grouped by date, with highlight observations per session. Use when the user asks "recap", "what have we been doing", "today", "this week", or wants a rollup of recent work.
alcove-hub
Use when working from the Alcove hub workspace or routing personal knowledge, pins, projects, prompts, tasks, mounts, connectors, or managed KB operations.