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 agentmods add skills/rust-works/succinctly/knowledge-mapnpx skills add rust-works/succinctly --skill knowledge-mapgit clone --depth 1 https://github.com/rust-works/succinctlyWhat 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 | $0.00047 | $0.00640 |
| Opus 5 | $0.00023 | $0.00320 |
| Sonnet 5 | $0.00009 | $0.00128 |
| Haiku 4.5 | $0.00005 | $0.00064 |
Grade A, and why
knowledge-map 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 2d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Knowledge Map Maintenance
The knowledge wiki lives in docs/ with docs/index.md as the entry point. Each core concept has its own page. When the codebase changes in ways that affect the wiki, update the relevant pages.
Page Structure
Every concept page follows this structure:
- Breadcrumb:
[Home](../../) > [Docs](../) > [Category](./) > PageName - What It Does — one-paragraph summary
- How It Works — key algorithms and data structures
- Depends On — links to wiki pages this concept uses
- Used By — links to wiki pages that use this concept
- Academic Papers — citations with links where available
- Source & Docs — links to implementation files and existing architecture/parsing docs
When to Update
New data structure or module
- Create the page in the appropriate subdirectory (e.g.
docs/parsing/,docs/optimizations/,docs/reference/) following the page structure above - Add a row to the Core Data Structures table in
docs/index.md - Update Depends On / Used By sections on related pages (keep these bidirectional)
- If the module has SIMD variants, add to
docs/optimizations/simd-strategy.md
New optimization
- Add a row to the relevant concept page's optimization table (e.g. the Optimization Journey table in
docs/parsing/yaml-index.md) - If it involves a new SIMD technique, update
docs/optimizations/simd-strategy.md
New academic paper reference
- Add to the Academic Foundations table in
docs/index.md - Add to the relevant concept page's Academic Papers section
- If the URL is on
doi.org, it's already excluded from link checking (returns 403 to bots)
New SIMD path
- Update the Platform Support table in
docs/optimizations/simd-strategy.md - Update the Per-Module SIMD Usage section in
docs/optimizations/simd-strategy.md - Update the SIMD Platform Support table in
docs/index.mdif a new platform is added
Formatting Rules
- Tables must use fixed-width columns with consistent padding (invoke the
format-md-tablesskill) - Use mermaid diagrams for flowcharts and dependency graphs, not ASCII art
- Use relative markdown links (not wikilinks)
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.
- 2d ago First seen · 60 lines · 47 tokens per session scan A 9d32e5908fba
knowledge-map is a skill published in the GitHub repository rust-works/succinctly (51 stars, last pushed 2d ago), licensed MIT. It adds 47 tokens to every session and 640 once invoked, about $0.0002 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…