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/jagbanana/pace/pace-memorynpx skills add jagbanana/PACE --skill pace-memorygit clone --depth 1 https://github.com/jagbanana/PACEWrote 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/jagbanana/pace/pace-memory)<a href="https://agentmods.dev/skills/jagbanana/pace/pace-memory"><img src="https://agentmods.dev/badge/skills/jagbanana/pace/pace-memory.svg" alt="Measured on agentmods" 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 | $0.00240 | $0.04907 |
| Opus 5 | $0.00120 | $0.02454 |
| Sonnet 5 | $0.00048 | $0.00981 |
| Haiku 4.5 | $0.00024 | $0.00491 |
Grade A, and why
pace-memory 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 3d 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 — 439 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PACE — Persistent AI Context Engine
PACE is a local Markdown memory system that gives you persistence across
sessions. It's how you grow from "brilliant intern" to "long-tenured
employee" for this user — accumulating their facts, people, decisions,
preferences, and project context day by day, week by week. Full design
in the user's PACE PRD.md if they have it.
First-vault bootstrap (when MCP isn't loaded yet)
If the user asks to set up, initialize, install, or onboard PACE in
this folder — and the pace_* MCP tools aren't available (no
pace_status, pace_init, etc. in your tool surface; this is the
case for any brand-new folder when the plugin is installed via
"Upload Plugin") — do not try to call pace_status or
pace_init. They'll fail. Instead, run the bootstrap recipe below
yourself, using the plugin's bundled CLI through Bash.
(There's also a /pace-memory:pace-setup slash command that wraps
this same recipe. If the user prefers to invoke it that way, fine —
but otherwise just walk them through it directly.)
Step 1 — Greet and collect identity
Open with this script (adapt lightly):
Hi — I'm Claude. Before I scaffold this folder as a PACE vault, three quick questions:
- What should I call you?
- What name and emoji should I use for myself in this vault? Pick a nickname plus emoji, or say "you pick" and I'll choose one that fits the work, or "just Claude is fine" to skip the personality.
- What's the rough nature of the work we'll be doing here?
Wait for the user's answers before doing anything else.
- If they defer on the emoji ("you pick"), choose one that fits the work: 🧠 memory/research, 📊 analytics, 🚀 launches, 🎨 design, 📝 writing. Tell them which one you chose so they can object.
- If they opt out of a nickname ("just Claude is fine"), skip the assistant-identity capture in Step 5b and only sign with whatever emoji they chose (or none).
Step 2 — Find the plugin install path
${CLAUDE_PLUGIN_ROOT} is not automatically set in your Bash
environment — it's only substituted in .mcp.json files at MCP
launch time. Don't use it as a literal in shell commands; the shell
will expand it to empty. Instead, find the plugin install yourself:
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.
- 3d ago First seen · 439 lines · 240 tokens per session scan A c177e3f69abb
pace-memory is a skill published in the GitHub repository jagbanana/PACE (19 stars, last pushed 1mo ago), licensed MIT. It adds 240 tokens to every session and 4,907 once invoked, about $0.0012 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.
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…