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/shaheerkhawaja/productionos/devtoolsgit clone --depth 1 https://github.com/ShaheerKhawaja/ProductionOSWhat 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.00032 | $0.00729 |
| Opus 5 | $0.00016 | $0.00365 |
| Sonnet 5 | $0.00006 | $0.00146 |
| Haiku 4.5 | $0.00003 | $0.00073 |
Grade A, and why
devtools 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ProductionOS DevTools — Mission Control
Step 0: Preamble
Before executing, run the shared ProductionOS preamble (templates/PREAMBLE.md) to confirm the active install root and session context.
Execute the requested action for Claude DevTools within the ProductionOS ecosystem.
Action: $ARGUMENTS.action
Step 1: Check DevTools installation and status
DEVTOOLS_APP="/Applications/claude-devtools.app"
if [ ! -d "$DEVTOOLS_APP" ]; then
echo "DEVTOOLS_NOT_INSTALLED"
echo "Install with: brew install --cask claude-devtools"
else
DEVTOOLS_PID=$(pgrep -f "claude-devtools" 2>/dev/null | head -1)
if [ -n "$DEVTOOLS_PID" ]; then
echo "DEVTOOLS_RUNNING (PID: $DEVTOOLS_PID)"
else
echo "DEVTOOLS_STOPPED"
fi
fi
If not installed, tell the user to run brew install --cask claude-devtools and stop.
Step 2: Execute action
launch (default):
- If DevTools is NOT running, launch it:
open /Applications/claude-devtools.app - If already running, bring to foreground:
osascript -e 'tell application "claude-devtools" to activate' - Then show the full dashboard (Step 3)
status:
- Run the dashboard script for the full report:
python3 "${CLAUDE_PLUGIN_ROOT:-$HOME/.claude/plugins/marketplaces/productionos}/hooks/devtools-dashboard.py" --full - Display the output to the user as-is (it's already formatted)
focus:
- Bring DevTools window to foreground:
osascript -e 'tell application "claude-devtools" to activate'
quit:
- Gracefully quit DevTools:
osascript -e 'tell application "claude-devtools" to quit'
Step 3: Full Dashboard (runs on launch and status)
Run the dashboard script:
python3 "${CLAUDE_PLUGIN_ROOT:-$HOME/.claude/plugins/marketplaces/productionos}/hooks/devtools-dashboard.py" --full
This shows:
- Session metrics (edits, agents, security events)
- Cost tracking (session delta, all-time total)
- Eval convergence (latest score, sparkline trend, data points)
- Agent dispatch breakdown by type
- Hot files (cross-session churn with bar charts)
- Event breakdown
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 · 94 lines · 32 tokens per session scan A 5665b00c6280
devtools is a command published in the GitHub repository ShaheerKhawaja/ProductionOS (8 stars, last pushed 4mo ago), licensed MIT. It adds 32 tokens to every session and 729 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 commands, from other repositories
rekindle
Recover a fellowship after a session crash. Scans worktrees and state files, presents a recovery dashboard, and re-spawns Gandalf with recovered quest context. Use when returning to a crashed or expired fellowship session.
settings
View or edit fellowship configuration (/.claude/fellowship.json). Run /settings to see current settings, change values, or reset to defaults.
validate-docs
Validate that site and README documentation is current. Report-only — flags issues without modifying anything.
chronicle
One-time codebase onboarding — interactively extracts your team's conventions, identifies reference files, and generates CLAUDE.md sections so Claude codes the way your team does. Run once per project.
guide
Interactive guide to fellowship. Walks you through a real task using the structured research-plan-implement flow, then shows you what's next.
red-book
Use after receiving PR review feedback. Extracts conventions from reviewer comments and offers to add them to CLAUDE.md. Closes the convention learning loop.