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/floomhq/moto/vaultnpx skills add floomhq/moto --skill vaultgit clone --depth 1 https://github.com/floomhq/motoWrote 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/floomhq/moto/vault)<a href="https://agentmods.dev/skills/floomhq/moto/vault"><img src="https://agentmods.dev/badge/skills/floomhq/moto/vault.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.00072 | $0.00701 |
| Opus 5 | $0.00036 | $0.00351 |
| Sonnet 5 | $0.00014 | $0.00140 |
| Haiku 4.5 | $0.00007 | $0.00070 |
Grade A, and why
vault 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 5d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vault
Context vault at <VAULT_PATH>. A mono-repo for all non-code context: strategy, legal, taxes, pitches, brand, projects.
Sensitivity Rules
| Level | Folders | Rule |
|---|---|---|
| CRITICAL | legal/, taxes/ |
NEVER echo content. Acknowledge existence only. |
| HIGH | cv/, team/ |
Summarize; no verbatim PII (DOB, ID numbers, salaries) |
| MEDIUM | secretary/, strategy/, projects/ |
Read and share freely; redact API keys/passwords |
| LOW | brand/, content/, research/ |
Read and share freely |
Never echo: API keys, passwords, legal PII, contract amounts, tax figures.
Commit Rules
- Prefix:
context-agent:(e.g.,context-agent: update todos) - Never include sensitive data in commit messages
- Always push after committing
Operations
1. Update Todos
cd <VAULT_PATH> && git pull
# Read current state
cat secretary/todos.md
# Edit: add/remove/update items with Edit tool
git add secretary/todos.md
git commit -m "context-agent: update todos"
git push
2. Add Log Entry
Target file: secretary/logs/YYYY-MM.md
cd <VAULT_PATH> && git pull
# Append timestamped entry: ## YYYY-MM-DD HH:MM UTC\n\n<entry text>\n
git add secretary/logs/$(date +%Y-%m).md
git commit -m "context-agent: add log entry"
git push
3. Search Vault
grep -r "keyword" <VAULT_PATH>/ --include="*.md" -l
# Then read matching files (respecting sensitivity rules above)
4. Read Strategy / Projects
ls <VAULT_PATH>/strategy/
cat <VAULT_PATH>/strategy/<file>.md
5. Update Project Docs
cd <VAULT_PATH> && git pull
# Edit file with Edit tool
git add projects/<file>.md
git commit -m "context-agent: update <project> docs"
git push
Workflow Template
For any vault write operation:
cd <VAULT_PATH> && git pull(always pull first)- Read the target file (understand current state)
- Edit with Edit tool
git add <file> && git commit -m "context-agent: <action>" && git push- Confirm to user without echoing CRITICAL 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.
- 5d ago First seen · 96 lines · 72 tokens per session scan A ef3c463afab2
vault is a skill published in the GitHub repository floomhq/moto (32 stars, last pushed 2mo ago), licensed MIT. It adds 72 tokens to every session and 701 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-30.
Other skills, from other repositories
compact
Strategic compaction skill: suggests context compression at logical breakpoints. Use to suggest compaction at logical intervals during development sessions.
session
Session lifecycle management. Parent skill for session-related skills: learning (pattern extraction) and compact (context compression).
tdd-rust
TDD workflow for RTK filter development. Red-Green-Refactor with Rust idioms. Real fixtures, token savings assertions, snapshot tests with insta. Auto-triggers on new filter implementation.
digital-brain
This skill should be used when the user asks to "write a post", "check my voice", "look up contact", "prepare for meeting", "weekly review", "track goals", or mentions personal brand, content creation, network management, or voice consistency.
moai-foundation-context
Manages context window optimization, session state persistence, and token budget allocation for multi-agent workflows. Use for token budget management, context limits, or session handoff across agents.
session-management
Context preservation, tiered summarization, resumability.