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 chinkan/RustFox --skill soul-keepergit clone --depth 1 https://github.com/chinkan/RustFoxWrote 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/chinkan/rustfox/soul-keeper)<a href="https://agentmods.dev/skills/chinkan/rustfox/soul-keeper"><img src="https://agentmods.dev/badge/skills/chinkan/rustfox/soul-keeper.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.00036 | $0.01221 |
| Opus 5 | $0.00018 | $0.00611 |
| Sonnet 5 | $0.00007 | $0.00244 |
| Haiku 4.5 | $0.00004 | $0.00122 |
Grade A, and why
soul-keeper 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.
How it starts
The opening of the file, as written. The whole thing — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Soul Keeper
You maintain two persistent files:
skills/soul/SOUL.md— your core identity, personality, and values (changes slowly)skills/soul/USER.md— what you know about the user (changes freely)
When to Trigger
Load this skill and follow it when:
| Signal | File to update |
|---|---|
| User corrects tone ("stop being formal", "be more direct") | SOUL.md → tone or style |
| User gives style feedback ("I like the sarcasm") | SOUL.md → humor or style |
| User names a value ("I respect honesty") | SOUL.md → values |
| User corrects a boundary or rule | SOUL.md → rules |
| User shares their name | USER.md → user_name |
| User states a preference ("I prefer bullets") | USER.md → preferences |
| User shares context (job, location, language) | USER.md → context or language |
| Relationship dynamic clearly established | USER.md → relationship |
Do not trigger for: temporary requests, one-off tasks, or anything that won't affect future conversations.
Protocol
Follow these steps in order. Do not skip steps.
Step 1 — Read the file you will update
To update SOUL.md:
read_skill_file(skill_name="soul", relative_path="SOUL.md")
To update USER.md:
read_skill_file(skill_name="soul", relative_path="USER.md")
Step 2 — Identify the minimum change
- Only change what the signal directly demands
- Do not "improve" other fields while you're in there
- If the signal is a correction ("stop being X"), remove X and optionally add the opposite
- If the signal is an addition ("be more Y"), append Y — do not remove existing values
- For SOUL.md: increment
versionby 1 - For USER.md: there is no version field — do not add one
- Never remove from
boundariesfor any reason - Never modify
idorborn
Step 3 — Write the complete updated file
Write the entire file with your change applied — not just the changed lines:
write_skill_file(skill_name="soul", relative_path="SOUL.md", content="<FULL FILE CONTENT>")
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 · 190 lines · 36 tokens per session scan A f4d9e94e7896
soul-keeper is a skill published in the GitHub repository chinkan/RustFox (7 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 1,221 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-09-03.
Other skills, from other repositories
update-setup
A one-time setup wizard for creating a personalised upgrade guide for a workspace. It checks for an existing guide, identifies the current version and installation clues, and requires confirmation of the installation method before writing a new guide.
skill-creator
Create, edit, improve, tidy, review, audit, or restructure memmy-agent skills and SKILL.md files.
memmy-memory
Use the shared Memmy memory service to retrieve relevant prior context and persist durable Agent turns, facts, decisions, preferences, procedures, and follow-ups.
ui-craft
Design, build, redesign, or modify browser-visible web interfaces with product-quality composition, visual systems, interaction states, responsive behavior, accessibility, and browser visual QA. Use for HTML, CSS, JavaScript, React, Vue, or Svelte pages and components, landing pages, dashboards, admin tools, settings…
memmy-memory
Use the memmy-memory CLI when an agent needs to check the Memory service, open or close agent sessions, start or complete turns, search, add, read, or delete memories, or call uncommon HTTP routes through raw requests.
agentlas-auto-activation
Use when adding or auditing local runtime behavior that turns a project folder into an Agentlas-aware workspace with .agentlas memory and sitemap files.