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.
git clone --depth 1 https://github.com/OPTIMETA/PAIDEIAWrote 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/commands/optimeta/paideia/weakmap)<a href="https://agentmods.dev/commands/optimeta/paideia/weakmap"><img src="https://agentmods.dev/badge/commands/optimeta/paideia/weakmap/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/commands/optimeta/paideia/weakmap"><img src="https://agentmods.dev/badge/commands/optimeta/paideia/weakmap.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.00038 | $0.01199 |
| Opus 5.5 | $0.00015 | $0.00480 |
| Sonnet 5.5 | $0.00008 | $0.00240 |
| Haiku 4.5 | $0.00004 | $0.00120 |
Grade A, and why
weakmap 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 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.
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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Arguments: $ARGUMENTS
Output language
Read INTERFACE_LANG from .course-meta (default en). All user-facing prose — chat output and the narrative portions of the report MD — must be in that language. Keep in English regardless: file paths, slash command names, pattern IDs (P1, P2…), YAML keys, tier markers (🔥🔥/🔥/🟡/⚪), the report's literal section anchors (# Weakmap — <ts>, ## Error histogram, ## Top 5 weaknesses, ## User-declared weaknesses, ## Exam-hot zones not yet drilled, ## One-line verdict) and the table column headers (Pattern/topic, Latest error type, Date, §) — downstream tools regex on these.
Purpose
Use when the user notices "I think I'm weak at this point" while studying — they record it with /weakmap <concept> and it accumulates in the report. Called without arguments, it takes a fresh snapshot from the latest error log.
Storage rules
- Report directory:
weakmap/ - File name:
weakmap/weakmap_<YYYY-MM-DD_HHmm>.md - Top heading:
# Weakmap — <YYYY-MM-DD HH:mm> - Never overwrite. Always save a new timestamped file (preserve history).
- "Latest report" = the file in
weakmap/with the most recent mtime.
Branches
Case A — no argument (fresh snapshot)
- Read
errors/log.md. Group YAML entries bypattern. - Within each pattern, keep only the entry with the most recent
date. Older errors may have already been corrected, so "current weakness snapshot" = latest only. - Cross-reference with
course-index/coverage.md's reverse map — the 🔥 exam tiers and any⚠weakflags. - (If present) the prior weakmap's "User-declared weaknesses" section is not re-included. A no-argument call is an error-log-driven re-snapshot, so user-declared stays empty in this mode.
- Write to
weakmap/weakmap_<ts>.mdin the format below and print a chat summary.
Case B — with argument (concept patch)
"Read the latest report → append the new concept to user-declared (cumulative: A, B + C) → rewrite the whole report against {A, B, C} → save under a new timestamp."
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 · 94 lines · 38 tokens per session scan A de28dbb7768f
weakmap is a command published in the GitHub repository OPTIMETA/PAIDEIA (91 stars, last pushed 3mo ago), licensed MIT. It adds 38 tokens to every session and 1,199 once invoked, about $0.0002 per session on Opus 5.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-30.
Other commands, from other repositories
design-tutorial
Interactive guided tour of Naksha — learn commands through real exercises, discover workflows, and get oriented in under 10 minutes.
naksha-help
Quick-reference for any Naksha command — browse by category or look up a specific command.
annex-a-deep-dive
Deep dive analysis of ISO 27001 Annex A control domains with implementation guidance.
code-explainer
Use when a designer needs to understand code that already works. What a file does, what a line means, which parts are safe to change. Plain language with Figma analogies, no developer jargon.
recap
Get a summary of everything you learned this session — concepts, quizzes, and progress.
review
Cold re-quiz on code that already shipped — your own session commits, not the change in front of you.