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 briefgit 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/brief)<a href="https://agentmods.dev/skills/7xuanlu/wenlan/brief"><img src="https://agentmods.dev/badge/skills/7xuanlu/wenlan/brief.svg" alt="Measured on agentmods" 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 26 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.00050 | $0.00839 |
| Opus 5 | $0.00025 | $0.00419 |
| Sonnet 5 | $0.00010 | $0.00168 |
| Haiku 4.5 | $0.00005 | $0.00084 |
Grade B, and why
brief 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 8d 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)" How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/brief
Read one Space's current project snapshot. The daemon Brief is authoritative;
~/.wenlan/sessions/_status/*.md is only a one-way human-readable receipt and must
never be read as product state.
1. Resolve the Space
raw_args="<the full argument string passed to /brief>"
space_arg="$(printf '%s\n' "$raw_args" | grep -oE 'space:[A-Za-z0-9_-]+' | head -1 | cut -d: -f2)"
topic_arg="$(printf '%s\n' "$raw_args" | sed -E 's/[[:space:]]*space:[A-Za-z0-9_-]+[[:space:]]*/ /g' | sed -E 's/^[[:space:]]+|[[:space:]]+$//g')"
# 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)"
Print Resolved space: <space> (from <source-layer>). If no Space resolves,
print Resolved space: none (unscoped) and omit space.
2. Read the Brief
Call:
mcp__wenlan__brief(
topic="<topic_arg only when the user supplied one>",
space="<resolved only when non-empty>"
)
Do not invent or infer a topic when the argument is absent. No topic means the
complete Brief alone. A topic means the same complete Brief plus a separate
Related Context section scoped to that Space.
Brief reads never create state. If the state is brief_not_created, explain
that the first /handoff update will create it. If the state is
space_not_resolved, ask for a Space only when the working directory and
configuration cannot resolve one safely.
Render the last-session summary, Active, Backlog, then Related Context only
when returned. Keep stable item IDs and versions available for later
/handoff reconciliation, but omit them from the normal user-facing list.
3. Pending revisions
Call:
mcp__wenlan__list_pending_revisions(limit=10)
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.
- 8d ago First seen · 81 lines · 50 tokens per session scan B 25b2a1c2cf41
brief is a skill published in the GitHub repository 7xuanlu/wenlan (64 stars, last pushed today), licensed Apache-2.0. It adds 50 tokens to every session and 839 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
day-log
Quick timestamped log entry — no conversation, just capture.
period-summary
Period summary (w/m/q/y) — reflect on the period, score it, close it out.
day-start
Day briefing — deliver context, capture what's happened, get moving.
drive-me
Diagnose personal execution friction and convert a vague, stalled, or over-scoped goal into one bounded next-action plan with explicit scope, non-goals, acceptance criteria, and a lightweight feedback loop. Use when the user asks for help restarting work, overcoming procrastination, choosing what to do next, reducing…
recap
Summarize the last N agent sessions for the current project, grouped by date, with highlight observations per session. Use when the user asks "recap", "what have we been doing", "today", "this week", or wants a rollup of recent work.
day-summary
Evening summary — reflect on the day, score it, close it out.