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 owrede/vault-memory --skill create-contractgit clone --depth 1 https://github.com/owrede/vault-memoryWrote 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/owrede/vault-memory/create-contract)<a href="https://agentmods.dev/skills/owrede/vault-memory/create-contract"><img src="https://agentmods.dev/badge/skills/owrede/vault-memory/create-contract/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/owrede/vault-memory/create-contract"><img src="https://agentmods.dev/badge/skills/owrede/vault-memory/create-contract.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.00235 | $0.02904 |
| Opus 5.5 | $0.00094 | $0.01162 |
| Sonnet 5.5 | $0.00047 | $0.00581 |
| Haiku 4.5 | $0.00023 | $0.00290 |
Grade A, and why
create-contract 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 1mo 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/create-contract — Author a task contract from intent
This skill takes a free-language description of a recurring search/assembly need and
walks it to a validated YAML contract written to the vault's _contracts/
directory. It is the interactive intent → design bridge.
It is the sibling of use-contracts: that skill runs
existing contracts; this one authors new ones. The full DSL reference,
the closed verb enum, the chaining rule, the onboarding gotchas, and a minimal
runnable example all live in
docs/v2/plugin/AUTHORING-CONTRACTS.md —
lean on that document, do not restate it here. This skill is the conversation
that turns intent into a contract that follows it.
When to invoke
Proactively, when the user reveals a recurring knowledge-assembly need:
- "I keep pulling the same notes together before every board meeting."
- "Every time someone joins a project I rebuild the same onboarding dossier."
- "We keep searching for the same risk notes across projects."
- German: "Ich stelle ständig dieselbe Frage zu …", "Wir suchen immer wieder nach …".
The tell is repetition of a question's shape, with one moving part. A one-off
("summarize this single note") is just search_hybrid — not a contract.
Explicitly, when the user says /create-contract, "create / design / author /
build a contract", "neuen Contract erstellen", "Contract entwerfen / bauen".
For discovery, when the user asks "what should I turn into a contract?" or when
use-contracts recently logged no-match gaps (see Discovery mode below).
Contrast with use-contracts: if the user wants to run
a recipe that already exists, that's use-contracts, not this skill.
Requirements
mcp__vault-memory__*tools available in the session- At least one vault registered; contracts live under
_contracts/*.yamland are hot-reloaded by the server (startContractRegistry)
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.
- 1mo ago First seen · 217 lines · 235 tokens per session scan A 61232c9db5e0
create-contract is a skill published in the GitHub repository owrede/vault-memory (0 stars, last pushed 25d ago), licensed MIT. It adds 235 tokens to every session and 2,904 once invoked, about $0.0009 per session on Opus 5.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
knowledge-ingest
Ingest documents, articles, conversations, or supplied text into Knowledge with retained originals, sourced claims, entity updates, timelines, and cross-links; also learn durable lessons from a set of conversations, transcripts, or past sessions (/learn), including the Learn from conversations and Learn from Memory…
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
Cortex
LifeOS memory, prior-session recall, and learning capture. USE WHEN capture this learning, document this learning, what did we learn recently, recent learnings, cortex, knowledge, knowledge base, search knowledge, what do we know about, archive, harvest, knowledge status, develop note, add to knowledge, add a people…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…