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 chicken-noodle-chris/tome --skill capturegit clone --depth 1 https://github.com/chicken-noodle-chris/tomeWrote 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/chicken-noodle-chris/tome/capture)<a href="https://agentmods.dev/skills/chicken-noodle-chris/tome/capture"><img src="https://agentmods.dev/badge/skills/chicken-noodle-chris/tome/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/chicken-noodle-chris/tome/capture"><img src="https://agentmods.dev/badge/skills/chicken-noodle-chris/tome/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.00033 | $0.00492 |
| Opus 5 | $0.00016 | $0.00246 |
| Sonnet 5 | $0.00007 | $0.00098 |
| Haiku 4.5 | $0.00003 | $0.00049 |
Grade A, and why
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 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.
What it actually says
Optional input: the thing to remember, in the user's own words.
Capture exists because memory systems live or die on capture being nearly free. This is
the cheap half of the capture → compile flow in wiki/SCHEMA.md: this skill drops a note
in inbox/; the retrospect skill is the one that later triages it into the wiki. Don't
do triage here — that's the whole point of splitting the two.
-
Check it's the right weight class. A full external source (a paper, an article, a transcript) is
ingest's job, not this one — hand off instead. A small fact, decision context, preference, or link is this skill's job. -
Distill, don't transcribe. One to three self-contained sentences — enough context that a future triage pass (which won't have this conversation) understands it cold. Name the project if there is one.
-
Capture it.
tome inbox "<distilled note>"(fall back topython "$TOME_PLUGIN_ROOT/scripts/tome.py" inbox "..."iftomeisn't on PATH). Skip the schema-read / index-read ceremony other skills do — that's what keeps this under ~15 seconds of session time. -
Close with one line. Tell the user it's in the inbox and will be routed at the next retrospect triage. If the thing is plainly page-worthy on its own and the user is clearly engaged right now, you may offer the direct
tome newroute as an alternative — but default to the inbox, not a judgment call.
Anti-patterns: running the schema/index-read ceremony (defeats the point — that's what
ingest and write-a-plan are for); triaging or filing the note into a real page here
(that's retrospect's job); capturing something that's really a full external source.
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 · 35 lines · 33 tokens per session scan A 802b4472daaf
capture is a skill published in the GitHub repository chicken-noodle-chris/tome (6 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 492 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-31.
Other skills, from other repositories
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
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…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.