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 agentmods add skills/zircote-plugins/rlm-rs-plugin/rlmnpx skills add zircote-plugins/rlm-rs-plugin --skill rlmgit clone --depth 1 https://github.com/zircote-plugins/rlm-rs-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/zircote-plugins/rlm-rs-plugin/rlm)<a href="https://agentmods.dev/skills/zircote-plugins/rlm-rs-plugin/rlm"><img src="https://agentmods.dev/badge/skills/zircote-plugins/rlm-rs-plugin/rlm.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 | $0.00080 | $0.02172 |
| Opus 5 | $0.00040 | $0.01086 |
| Sonnet 5 | $0.00016 | $0.00434 |
| Haiku 4.5 | $0.00008 | $0.00217 |
Grade A, and why
rlm 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 3d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What ships with it
1 file 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.
- 3d ago First seen · 253 lines · 80 tokens per session scan A e4fd606e160c
rlm is a skill published in the GitHub repository zircote-plugins/rlm-rs-plugin (3 stars, last pushed 1mo ago), with no licence file. It adds 80 tokens to every session and 2,172 once invoked, about $0.0004 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
vault
Generate an Obsidian LLM wiki vault from a project's source code and any static documents in raw/.
revise-structure
Revisional skill: repair a document's structure while holding meaning constant. Use when the user says "fix the structure of this document", "re-group / re-order / re-summarize these points", "the arrangement is wrong", once a structural defect is known. Common phrasings: "restructure this", "reorganize the argument"…
research-archivist
Use this skill when the user asks to ingest, organize, archive, or update research source materials, wiki pages, evidence packs, or information packs.
advanced-evaluation
This skill should be used when the user asks to "implement LLM-as-judge", "compare model outputs", "create evaluation rubrics", "mitigate evaluation bias", or mentions direct scoring, pairwise compari.
review-feasibility
Stress-teste un brouillon (PRD ou roadmap) sous l'angle faisabilité technique. Croise les claims techniques du brouillon avec les pages wiki/decision- et wiki/feature- pour surfacer les conflits avec l'architecture documentée. Conçue pour un propriétaire côté produit qui prépare une discussion ingénierie. Applique les…
roadmap-update
Produit un document de roadmap dans output/ en croisant l'état actuel des epics beads avec les décisions et priorités documentées dans le wiki. Applique les règles anti-lissage — ne jamais compléter avec des connaissances d'entraînement, citer le wiki pour chaque affirmation de scope ou de priorité. Triggers — mettre…