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 carsteneu/yesmem --skill yesmem-cap-buildergit clone --depth 1 https://github.com/carsteneu/yesmemWrote 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/carsteneu/yesmem/yesmem-cap-builder)<a href="https://agentmods.dev/skills/carsteneu/yesmem/yesmem-cap-builder"><img src="https://agentmods.dev/badge/skills/carsteneu/yesmem/yesmem-cap-builder/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/carsteneu/yesmem/yesmem-cap-builder"><img src="https://agentmods.dev/badge/skills/carsteneu/yesmem/yesmem-cap-builder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
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 →
- high Agent Snooping · line 282 Skill reads from agent configuration directories (.claude/, .codex/, .gemini/). These directories may contain API keys, personal settings, and other credentials that the skill has no legitimate need to access.Fix: Remove all code or instructions that access agent configuration directories (.claude/, .codex/, .gemini/). If configuration values are needed, pass them explicitly as parameters or environment variabl
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.00081 | $0.04551 |
| Opus 5 | $0.00041 | $0.02276 |
| Sonnet 5 | $0.00016 | $0.00910 |
| Haiku 4.5 | $0.00008 | $0.00455 |
Grade B, and why
yesmem-cap-builder scanned grade B with 2 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 9d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
| Source disagrees with disk after `make deploy` | DB-vs-disk write-back conflict. Diagnostic: `sha256sum caps/bundled-caps/<name>/CAP.md` vs `sha256sum ~/.claude/caps/<name>/CAP.md`; `grep '^version:' ~/.claude/caps/<na Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
const raw = await sh(`curl -s --max-time 15 "${URL}"`, 20000); How it starts
The opening of the file, as written. The whole thing — 337 lines — stays where its author put it; the contents beside it link to each section on GitHub.
YesMem Cap Builder
A cap is a CAP.md file (YAML frontmatter + ## Purpose + ## Scripts + optional ## Database + optional ## Actions) that yesmem persists as a learnings row, deploys to ~/.claude/caps/<name>/CAP.md, and re-injects into future sessions via the proxy. Caps are how an ad-hoc REPL command becomes a session-spanning, queryable tool.
This skill is the discovery surface. Side-files in this directory hold the depth — open them when you actually need them.
Side-files (open on demand)
| File | Open when |
|---|---|
recipes.md |
You're about to build a cap and want a working template to copy |
api-reference.md |
You're calling save_cap/get_caps/activate_cap/cap_store/cap_proposal_decide and need the exact param shape |
gotchas.md |
A cap fails on activate, save_cap silently stores garbage, sh() returns truncated output, or anything else surprises you |
External references
- Cap-Spec (canonical format):
https://github.com/carsteneu/cap-spec— treat as authoritative for CAP.md structure, frontmatter rules, and the v1.1 multi-script format. Note: spec.md is at v1.1-draft, butcap-spec/examples/*/CAP.mdare still v1.0 — seegotchas.md"Cap-spec format drift" before copying. - Working caps to copy from:
caps/bundled-caps/wiki_export/CAP.md(current, v1.1, ~16 KB embedded base64) andcaps/bundled-caps/reddit_fetch/are the freshest in-repo references. - yesmem CLI for caps:
yesmem query --format objects(read-only SQL acrossyesmem.db/messages.db/caps.db/runtime.db, projection-wrapped JSON),yesmem json(gojq-style filter pipeline, no--slurpfile),yesmem cap-blob-put(chunked blob ingest, bypasses the 30 KBsh()wall). Bash-runtime caps wire these together — seerecipes.md"Cap that pipesyesmem queryintoyesmem json" andapi-reference.md"yesmem CLI surface for caps".
When to build a cap
- Working command/script the user will reach for again next week
- Multi-step REPL sequence likely to recur
- Output deserves to be queryable later (search, aggregate, meta-analyze)
- Trigger phrases: "save this", "build a cap", "make this reusable", "/build-tool"
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 337 lines · 81 tokens per session scan B 34f2c9580ecb
yesmem-cap-builder is a skill published in the GitHub repository carsteneu/yesmem (41 stars, last pushed 7d ago), licensed Apache-2.0. It adds 81 tokens to every session and 4,551 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 2 findings (reads agent configuration directories, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
jiaojie
A human-first method for handing ongoing work from one chat, AI model, device, or language to another. It creates or reads a small handoff document, or a package with files when the receiver needs them.
learn-procedure
Capture a repeatable task procedure from the just-completed work as a durable, queryable memory node, so the steps are recalled automatically next time instead of re-derived. Triggers on "learn this procedure", "remember how to do this", "save this as a procedure", "/learn-procedure".
jumbo-add-guideline
Use liberally when the user expresses a preference about how work should be done — coding style, process, testing approach, communication style. Captures the guideline so future sessions follow it without being told again.
vault-audit
Vault health check. Validates structure, detects stale reasoning artifacts by priority level, processes inbox, and suggests cleanup. Triggers: "vault audit", "check vault", "clean up vault", "process inbox", "what's stale", "vault health".
inner-life
Keeps a dated record of how an agent's work has been going — an evening journal, free thinking at night, and a way to read it back. Use when asked to run the inner-life evening or night routine, to note something in state, or to recall how a stretch went. Writes under inner-life/ and replaces a short summary in native…
pf-handoff
A Russian-language checkpoint and session-closing procedure that records the verified state of ongoing work in a HANDOFF file. A HANDOFF file is a written task record containing what is done, what remains, blockers, statuses, and journal entries.