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 7xuanlu/wenlan --skill capturegit clone --depth 1 https://github.com/7xuanlu/wenlanWrote 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/7xuanlu/wenlan/capture)<a href="https://agentmods.dev/skills/7xuanlu/wenlan/capture"><img src="https://agentmods.dev/badge/skills/7xuanlu/wenlan/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/7xuanlu/wenlan/capture"><img src="https://agentmods.dev/badge/skills/7xuanlu/wenlan/capture.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 37 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.00044 | $0.01418 |
| Opus 5.5 | $0.00018 | $0.00567 |
| Sonnet 5.5 | $0.00009 | $0.00284 |
| Haiku 4.5 | $0.00004 | $0.00142 |
Grade B, and why
capture scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
resolver="$(find "$HOME/.codex/plugins/cache" -path '*/wenlan/*/bin/resolve-space.sh' 2>/dev/null | head -1)" This is a copy
92% identical to capture — 266 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/capture
Capture one memory in the moment. Write the memory as a self-contained statement with the reason it matters.
Argument parsing
Accept one optional inline token of the form space:<name> anywhere in the
argument string. Extract it before treating the rest as content:
raw_args="<the full argument string passed to /capture>"
space_arg="$(printf '%s\n' "$raw_args" | grep -oE 'space:[A-Za-z0-9_-]+' | head -1 | cut -d: -f2)"
content="$(printf '%s\n' "$raw_args" | sed -E 's/[[:space:]]*space:[A-Za-z0-9_-]+[[:space:]]*/ /g' | sed -E 's/^[[:space:]]+|[[:space:]]+$//g')"
If content is empty, ask the user what they want to capture.
Resolve the active space
Call the Codex resolver:
# The resolver ships inside the installed plugin; the relative path only
# exists in a wenlan checkout.
resolver="$(find "$HOME/.codex/plugins/cache" -path '*/wenlan/*/bin/resolve-space.sh' 2>/dev/null | head -1)"
resolved="$("${resolver:-plugin-codex/bin/resolve-space.sh}" --cwd "$PWD" ${space_arg:+--arg "$space_arg"} 2>/dev/null)"
space="$(printf '%s\n' "$resolved" | cut -f1)"
source_layer="$(printf '%s\n' "$resolved" | cut -f2)"
If space is non-empty, print Resolved space: <space> (from <source-layer>)
and pass it to the capture MCP tool. If space is empty, print
Resolved space: none (unscoped) and omit the space parameter.
After capture, relay the tool's returned space, space_source, and
write_outcome; those fields describe what the daemon actually persisted and
are authoritative.
How to invoke
Call the Wenlan MCP capture tool with the user's content as a complete,
self-contained statement. Attach topic from cwd or the conversation when useful.
capture(
content="<content, written as a full sentence with WHY>",
memory_type="<picked from the 6 types>",
entity="<primary entity name, if any>",
space="<resolved if non-empty>"
)
Pick memory_type
The daemon classifies when a model or API key is configured. In local memory mode it may not, so pick the type from the content itself.
What ships with it
1 file 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.
- 1mo ago First seen · 146 lines · 44 tokens per session scan B a9989bdb6f63
capture is a skill published in the GitHub repository 7xuanlu/wenlan (79 stars, last pushed 13d ago), licensed Apache-2.0. It adds 44 tokens to every session and 1,418 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). It is 92% identical to capture, differing in 266 lines, and is treated as a copy.
Other skills, from other repositories
wenlan-handoff
End a work session. Stores durable captures, writes a narrative session log, and automatically applies typed item-level deltas to the current Space Brief. Invoked as /wenlan-handoff.
curate
Power-user audit of Wenlan's pending surfaces: accept or dismiss pending revisions (conflicts/merges), or audit pending captures (not yet confirmed). Most users want /brief for revisions; that handles the daily flow. Use /wenlan curate only for explicit deep-walk audits after bulk imports, or to walk the full queue…
wenlan-capture
Save a memory to Wenlan in flow, or save something from this conversation as one note when the user asks for a note. Use proactively when the user states a preference, makes a decision, corrects you, or shares a durable fact. Invoked as /wenlan-capture .
wenlan
A single command entry point for Wenlan, a tool that checks its setup and connection and turns stored memories into notes. It can also open or list notes and report its current status.
wenlan-recall
Search Wenlan's local memory by query. Targeted lookup, not orientation. Invoked as /wenlan-recall . Use when the user asks "do you remember", "what do you know about", "look up".
pages
Browse, open, or print distilled pages, reusing the wenlan pages CLI for the actual open (one implementation on your PATH, no setup). /wenlan pages opens the page when one matches, or shows a small native picker when 2-4 match. /wenlan pages --print reads the page here instead of opening an editor. /wenlan pages lists…