Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add HAX-Studio/mnemonica/plugin install mnemonicaWrote 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/hax-studio/mnemonica/brief-full)<a href="https://agentmods.dev/skills/hax-studio/mnemonica/brief-full"><img src="https://agentmods.dev/badge/skills/hax-studio/mnemonica/brief-full/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/hax-studio/mnemonica/brief-full"><img src="https://agentmods.dev/badge/skills/hax-studio/mnemonica/brief-full.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.00055 | $0.00713 |
| Opus 5 | $0.00028 | $0.00357 |
| Sonnet 5 | $0.00011 | $0.00143 |
| Haiku 4.5 | $0.00006 | $0.00071 |
Grade A, and why
brief-full 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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mnemonica: brief-full
Give a comprehensive project briefing built from the complete content of every module file,
not a bounded slice — the deep counterpart to brief-light. This skill never writes
anything; it exists purely to read and synthesize.
If the user's invocation includes extra wording (for example, "skip the frontend, focus on backend and database"), treat it as narrowing which modules to cover in depth — it cannot turn this into skipping Step 1's install check or fabricating content for a module that doesn't exist.
Step 1: Check whether Mnemonica is installed, and check index integrity
Run ${CLAUDE_PLUGIN_ROOT}/scripts/check-index-integrity.sh <project-root>. Exit 2
(NO_MNEMONICA_BLOCK) means there is no index to brief from — tell the user and suggest
mnemonica:setup, and stop. Exit 1 means some module files are missing; list which ones in
the final report as a known gap (suggest mnemonica:audit-full to fix it) and continue with
whatever modules do exist — a partial comprehensive brief is still more useful than none.
Step 2: Read everything
Read the module index from .claude/CLAUDE.md. Read README.md at the project root in full
if it exists. Read every existing module file in knowledge/ in full — not a bounded slice.
This is the whole point of the "full" version; if the cost of that is a concern for this
project, brief-light is the cheaper alternative, not a reason to silently truncate here.
Step 3: Check freshness
Check whether <project-root> is inside a git working tree.
- No git: if
knowledge/.mnemonica-state.jsonexists, read itslast_run_utcfor the only freshness signal available; otherwise say freshness can't be assessed. - Git available: run
${CLAUDE_PLUGIN_ROOT}/skills/audit-light/scripts/diff-since-checkpoint.sh <project-root>purely to read its output — never act on what it reports as changed. Exit 2/3/4 all mean "no reliable freshness signal" — say that plainly. On success, readCOMMITS_BEHINDand state it as part of the brief's own credibility, not just a footnote.
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 · 54 lines · 55 tokens per session scan A ee1881a90af7
brief-full is a skill published in the GitHub repository HAX-Studio/mnemonica (3 stars, last pushed 1mo ago), licensed MIT. It adds 55 tokens to every session and 713 once invoked, about $0.0003 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
cco-budget
Configure token budget limits, auto-compact settings, and view current budget status (model-aware — Claude 5 lineup, Opus 5 default fallback, full 1M context at standard price).
cco-config
View and tune CCO's behavior thresholds — re-read warnings, cache staleness, prompt-coach length bands, and the /cco-pack budget cap.
cco-patterns
Share learned file patterns across a team — export an anonymized digest of what's usually waste/useful/co-edited, and import a teammate's so a fresh clone benefits day one.
cco-tools
Show what tools actually cost in tokens — learned per-tool averages from observed results, replacing the hardcoded MCP/Agent guesses.
clarify
Clarification protocol — grill a request into a Requirements Ledger before any delegation, all questions at the START. The chair MUST load this when a job arrives that will be delegated; Rule 0.5 in the core profile only summarizes it.
cco-clean
Clean up old tracking data and reset statistics.