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 swarmclawai/swarmclaw --skill swarmvaultgit clone --depth 1 https://github.com/swarmclawai/swarmclawWrote 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/swarmclawai/swarmclaw/swarmvault)<a href="https://agentmods.dev/skills/swarmclawai/swarmclaw/swarmvault"><img src="https://agentmods.dev/badge/skills/swarmclawai/swarmclaw/swarmvault/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/swarmclawai/swarmclaw/swarmvault"><img src="https://agentmods.dev/badge/skills/swarmclawai/swarmclaw/swarmvault.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 14 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 61 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00037 | $0.01290 |
| Opus 5 | $0.00018 | $0.00645 |
| Sonnet 5 | $0.00007 | $0.00258 |
| Haiku 4.5 | $0.00004 | $0.00129 |
Grade A, and why
swarmvault 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 10d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SwarmVault
Use when the agent has a SwarmVault MCP server enabled (transport stdio, command npx -y @swarmvaultai/cli mcp) pointed at a vault directory.
A SwarmVault workspace is a three-layer knowledge system:
raw/— immutable source inputs (PDFs, transcripts, code, emails, URLs, sheets). Never edit.wiki/— generated markdown owned by the agent and the SwarmVault compiler. Pages carry frontmatter (page_id,source_ids,node_ids,freshness,source_hashes).state/— generated indexes, graphs, and approvals. Treat as opaque output ofcompile.
The vault contract lives in swarmvault.schema.md at the workspace root. The vault config lives in swarmvault.config.json.
Rules
- Read
swarmvault.schema.mdfirst before any compile or query work. It defines categories, naming, freshness rules, and grounding conventions for this specific vault. - Read
wiki/graph/report.mdbefore broad file searching when it exists; otherwise start withwiki/index.md. Both summarize the vault structure so you don't re-scan everything. - Treat
raw/as immutable. Never edit, rename, or delete files there. New sources go throughingest. - Treat
wiki/as compiler-owned. Edits should preserve frontmatter fields exactly:page_id,source_ids,node_ids,freshness,source_hashes. If those drift, the nextcompilewill overwrite or flag the page. - Prefer graph queries over grep/glob for "how does X relate to Y" or "what depends on Z" questions. The vault's typed graph is more reliable than text search.
- Save high-value answers to
wiki/outputs/(use thequeryorexploretools) instead of leaving them only in chat. That way they become first-class vault content for next time.
Tool Palette
The SwarmVault MCP server exposes the following tools (names are prefixed by SwarmClaw with mcp_<sanitized server name>_, e.g. mcp_SwarmVault_query_vault). Match the user's intent to the closest tool:
Vault inspection:
workspace_info— return current vault paths and high-level counts. Use this first when you've never seen this vault.list_sources— list source manifests underraw/.search_pages— full-text search across compiled wiki pages.read_page— read a specific wiki page by itswiki/-relative path.
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.
- 10d ago First seen · 84 lines · 37 tokens per session scan A e786467d0107
swarmvault is a skill published in the GitHub repository swarmclawai/swarmclaw (668 stars, last pushed 2mo ago), licensed MIT. It adds 37 tokens to every session and 1,290 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-08-30.
Other skills, from other repositories
orchestration
Multi-agent orchestration authority — agent memory protocols, task delegation, SOUL/AGENTS patterns, session startup, inter-agent communication, OpenClaw workspace coordination, and agent lifecycle management.
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…
crewai-multi-agent
Multi-agent orchestration framework for autonomous AI collaboration. Use when building teams of specialized agents working together on complex tasks, when you need role-based agent collaboration with memory, or for production workflows requiring sequential/hierarchical execution. Built without LangChain dependencies…
python-package-management
Guide for managing packages in the Agent Framework Python monorepo, including creating new connector packages, versioning, and the lazy-loading pattern. Use this when adding, modifying, or releasing packages.
foundry-hosted-agent-validation
Step-by-step process for validating a Python Foundry hosted agent sample (under python/samples/04-hosting/foundry-hosted-agents/) end to end — running it locally (native runtime and azd ai agent run) and after deploying it to an Azure AI Foundry project with azd. Use this when asked to validate a hosted agent sample.
verify-samples-tool
How to use the verify-samples tool to run, verify, and manage sample definitions in the Agent Framework repository. Use this when adding, updating, or running sample verification.