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/qingmingplusplus/tri-memory-kit/cross-memory-routingnpx skills add QingmingPlusPlus/tri-memory-kit --skill cross-memory-routinggit clone --depth 1 https://github.com/QingmingPlusPlus/tri-memory-kitWhat 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.00045 | $0.00319 |
| Opus 5 | $0.00023 | $0.00160 |
| Sonnet 5 | $0.00009 | $0.00064 |
| Haiku 4.5 | $0.00005 | $0.00032 |
Grade A, and why
cross-memory-routing 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.
What it actually says
cross-memory-routing
Use doc/agent-memory-map.md to locate existing project memory before starting work.
Steps
- Identify the request's target paths, modules, pages, APIs, or spec capabilities.
- Open
doc/agent-memory-map.mdand select the most specific matching row. Merge rows when multiple relevant paths match. - Read the row's
Read doc firstandRead spec firstentries before implementation. - Use skills listed in
Trigger skillonly when their workflow is relevant to the task. - If no row matches, search
doc/,spec/,openspec/specs/, and.agents/skills/withrg. - Before finishing, decide whether the change should update memory: future constraints to spec, current state to doc, stable workflows to skill.
- Update
doc/agent-memory-map.mdwhen adding or changing a long-term entry point, document, spec, or skill.
Self-Check
- The most relevant routing row was read before implementation.
- Existing documented capability was not rediscovered from scratch.
- Page state, field lists, one-off background, and current API details were not written into skills.
- New or migrated memory can be found by a future agent through the routing map.
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 · 26 lines · 45 tokens per session scan A 88e9a9704ffb
cross-memory-routing is a skill published in the GitHub repository QingmingPlusPlus/tri-memory-kit (5 stars, last pushed 4mo ago), licensed MIT. It adds 45 tokens to every session and 319 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…