A setup command for creating a PACE vault in the current folder. A vault is a project folder prepared for storing and using PACE's work-related memory.

Collecting basic project and identity details, bootstrapping the vault, and creating the project configuration needed for later PACE tools.

It handles the initial setup when the normal project tools are not yet available in the current session.

pace-setup — Command for Claude Code by jagbanana/PACE

Install

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.

Claude Code

/plugin marketplace add jagbanana/PACE

Claude Code

/plugin install pace-memory

Made for: Claude Code.

Or install pace-memory, the plugin that ships this one along with the rest of its 1 skill, 1 command, 1 MCP server.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/jagbanana/pace/pace-setup/github.svg)](https://agentmods.dev/commands/jagbanana/pace/pace-setup)

Your own site

<a href="https://agentmods.dev/commands/jagbanana/pace/pace-setup"><img src="https://agentmods.dev/badge/commands/jagbanana/pace/pace-setup/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/jagbanana/pace/pace-setup"><img src="https://agentmods.dev/badge/commands/jagbanana/pace/pace-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,529 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00009	$0.01529
Opus 5.5	$0.00004	$0.00612
Sonnet 5.5	$0.00002	$0.00306
Haiku 4.5	$0.00001	$0.00153

Measured 2mo ago against content hash 4397af6eec86, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

pace-setup 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 2mo 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.

plugin/commands/pace-setup.md · 149 lines

How it starts

The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.

The user just typed /pace-setup. They want to bootstrap a PACE vault in the current folder.

Why this command exists. When the pace-memory plugin is installed via Claude Desktop's "Upload Plugin" UI (the only install path today), its MCP server isn't auto-loaded in Claude Code project sessions. That means pace_status, pace_init, and the other pace_* MCP tools aren't available for first-vault setup. This slash command sidesteps that by invoking the plugin's bundled Python CLI directly via Bash. After bootstrap, a project-level .mcp.json gets written and PACE loads normally on the next session start.

Step 1 — Greet and collect identity

Open with this script (adapt lightly to the conversation):

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 when you reply 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 replies with whatever emoji they chose (or none).

Step 2 — Find the plugin install path

${CLAUDE_PLUGIN_ROOT} is not set in your Bash environment — it's only substituted in .mcp.json files at MCP launch time. Don't use it literally in shell commands; the shell expands it to empty. Find the plugin install yourself:

PLUGIN_ROOT=$(ls -d ~/.claude/plugins/marketplaces/*/pace-memory 2>/dev/null | head -n 1)
echo "PLUGIN_ROOT=$PLUGIN_ROOT"

Verify the path is non-empty and contains both .claude-plugin/plugin.json and server/. If the glob returns nothing, ask the user where the pace-memory plugin is installed. Use $PLUGIN_ROOT for the rest of this command.

Read the full file on GitHub · 149 lines

Changes

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.

2mo ago First seen · 149 lines · 9 tokens per session scan A 4397af6eec86

Subscribe to this mod's changes

pace-setup is a command published in the GitHub repository jagbanana/PACE (19 stars, last pushed 3mo ago), licensed MIT. It adds 9 tokens to every session and 1,529 once invoked, about $0.0000 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.

Memory and context

pace-setup next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
pace-setupjagbanana/PACE	Command	19	3mo ago	MIT	A	9	Claude Code
minutes-ideassilverstein/minutes	Command	1.6k	yesterday	MIT	A	48	Claude Code, OpenCode
learnReflexioAI/claude-smart	Command	791	3d ago	Apache-2.0	A	14	Claude Code
memory-storeverygoodplugins/mcp-automem	Command	66	yesterday	MIT	A	10	Claude Code
analyze-contextRohiRIK/OpenLtm	Command	29	8d ago	MIT	A	39	Claude Code
cc-memoryTheLobbi/claude	Command	21	7d ago	MIT	A	0	Claude Code
lians-recallLians-ai/Lians	Command	17	5d ago	Apache-2.0	A	19	Claude Code