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 commands/yrebrac/stuart/setupgit clone --depth 1 https://github.com/yrebrac/stuartWhat 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.00015 | $0.00334 |
| Opus 5 | $0.00008 | $0.00167 |
| Sonnet 5 | $0.00003 | $0.00067 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
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 yesterday.
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
Run the Stuart configuration utility to manage which tool servers and permissions are active.
Dependency check (always run first)
Before anything else, check that the mcp Python package is installed:
python3 -c "import mcp" 2>/dev/null
If this fails (non-zero exit), tell the user:
Stuart requires the
mcpPython package. Install it with:pip install mcpThen restart Claude Code.
Do not proceed with any other setup commands until this passes.
With arguments
If the user provided arguments (e.g. /setup list, /setup enable container), run the command directly:
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/setup.py $ARGUMENTS
Present the output to the user.
Without arguments (interactive)
If no arguments were provided:
- Run
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/setup.py listand present the output - Ask the user which items they'd like to enable or disable using AskUserQuestion (multi-select)
- For each change, run
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/setup.py enable <item>ordisable <item> - Tell the user to restart Claude Code for changes to take effect
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.
- yesterday First seen · 50 lines · 15 tokens per session scan A 23f1cee18ddb
setup is a command published in the GitHub repository yrebrac/stuart (1 stars, last pushed 5mo ago), licensed MIT. It adds 15 tokens to every session and 334 once invoked, about $0.0001 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 commands, from other repositories
release
Merge PR, tag release, and create GitHub release with changelog notes using the release skill.
changelog
Generate a Keep a Changelog entry from git commits using the changelog skill.
pr
Commit changes, bump version, update changelog, and open a PR using the pr skill.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.