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 collindjohnson/manas --skill manas-capturegit clone --depth 1 https://github.com/collindjohnson/manasWrote 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/collindjohnson/manas/manas-capture)<a href="https://agentmods.dev/skills/collindjohnson/manas/manas-capture"><img src="https://agentmods.dev/badge/skills/collindjohnson/manas/manas-capture/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/collindjohnson/manas/manas-capture"><img src="https://agentmods.dev/badge/skills/collindjohnson/manas/manas-capture.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.00025 | $0.00221 |
| Opus 5.5 | $0.00010 | $0.00088 |
| Sonnet 5.5 | $0.00005 | $0.00044 |
| Haiku 4.5 | $0.00003 | $0.00022 |
Grade A, and why
manas-capture 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 today.
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.
What it actually says
Use memory.remember with text, idempotencyKey, provenance, and appropriate visibility labels. A direct request to remember an assertion authorizes that capture. Automatic extraction requires the user's opt-in setting; encountering interesting material alone does not authorize capture.
Keep assertions scoped and include uncertainty and relevant validity dates. Record sourceType and available sessionId, turnId, sourceId, or observedAt. Use the same idempotency key and identical input when retrying a lost response. Derive a stable key from session, turn, and assertion identity when those identifiers are available.
Return the stable memory ID and memory revision from the receipt. Check currentStatus on a replay: an older capture receipt does not reactivate a withdrawn memory. Do not manufacture provenance, strip visibility labels, or use generic page writes to bypass the memory lifecycle.
CLI equivalent: manas remember --input <JSON>. Missing local models do not prevent explicit memory capture.
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.
- today First seen · 13 lines · 25 tokens per session scan A 9df7e05dd813
manas-capture is a skill published in the GitHub repository collindjohnson/manas (0 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 221 once invoked, about $0.0001 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-10-23.
Other skills, from other repositories
kb
Set up, evolve, or operate a hraness/kb local-first Markdown knowledge base for coding-agent memory. Use when a user asks to design KB conventions or a recurring KB ritual; search or query a KB or Obsidian vault; load or recover repository context, plans, decisions, concepts, backlinks, semantic search, or Git…
knowledge-base
Build and maintain a company knowledge base as a wiki of interlinked markdown notes in the workspace — a private, compounding Wikipedia. Use when the user wants to start or organize a knowledge base / wiki, ingest sources (URLs, documents, pasted notes) into it, ask questions answered from it, or audit (lint) it.…
my-wiki
A skill for managing a local Markdown knowledge vault that stores captured webpages, PDFs, Office files, notes, images, folders, and ZIP files. It links preserved source material, called References, to durable topic pages, called Concepts.
obsidian-vault-workflow
Use this skill when a user asks an agent to inspect, organize, summarize, or update an Obsidian vault through this MCP server.
vault-for-llm
Connect OpenClaw to Vault Agent Memory as a local-first governed project memory layer. Search first, then bounded-read cited source ranges; propose new memories as candidates instead of writing directly into active memory.
stats
Show Captain Memo's corpus statistics (chunks per channel, observation counts, indexing progress, embedder info). Use when the user types /captain-memo:stats.