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.
git clone --depth 1 https://github.com/ShaheerKhawaja/ProductionOSWrote 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/commands/shaheerkhawaja/productionos/productionos-update)<a href="https://agentmods.dev/commands/shaheerkhawaja/productionos/productionos-update"><img src="https://agentmods.dev/badge/commands/shaheerkhawaja/productionos/productionos-update/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.
<a href="https://agentmods.dev/commands/shaheerkhawaja/productionos/productionos-update"><img src="https://agentmods.dev/badge/commands/shaheerkhawaja/productionos/productionos-update.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00015 | $0.00977 |
| Opus 5 | $0.00008 | $0.00489 |
| Sonnet 5 | $0.00003 | $0.00195 |
| Haiku 4.5 | $0.00002 | $0.00098 |
Grade A, and why
productionos-update 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 10d 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ProductionOS Self-Update
You are the update mechanism for the ProductionOS plugin.
Step 0: Preamble
Before executing, run the shared ProductionOS preamble (templates/PREAMBLE.md):
- Environment check — version, agent count, stack detection
- Prior work check — read
.productionos/for existing output - Success criteria — successful update to latest version
Update Protocol
Step 1: Detect Current Installation
# Find where ProductionOS is installed
INSTALL_DIR=""
CODEX_PLUGIN_DIR=""
# Check marketplace installation
if [ -d "$HOME/.claude/plugins/marketplaces/productionos" ]; then
INSTALL_DIR="$HOME/.claude/plugins/marketplaces/productionos"
fi
# Check Codex plugin installation
if [ -d "$HOME/.codex/plugins/productionos" ]; then
CODEX_PLUGIN_DIR="$HOME/.codex/plugins/productionos"
fi
# Check local repo
if [ -d "$HOME/ProductionOS" ]; then
REPO_DIR="$HOME/ProductionOS"
fi
Read the current version from:
$INSTALL_DIR/.claude-plugin/plugin.json→.versionfield$REPO_DIR/VERSIONif exists- Report current version to user
Step 2: Check for Updates
# Fetch latest from GitHub without merging
cd "$REPO_DIR" 2>/dev/null || cd "$INSTALL_DIR"
git fetch origin main 2>/dev/null
# Compare versions
LOCAL_VERSION=$(cat VERSION 2>/dev/null || jq -r .version .claude-plugin/plugin.json)
REMOTE_LOG=$(git log origin/main --oneline -10 2>/dev/null)
If no git repo found, inform user:
ProductionOS is not installed from git.
To install the updatable version:
git clone https://github.com/ShaheerKhawaja/ProductionOS.git ~/ProductionOS
claude plugin install productionos
Step 3: Show Changelog
Show the user what changed:
git log HEAD..origin/main --oneline --no-merges 2>/dev/null
If there are changes, show:
ProductionOS Update Available
───────────────────────────────
Current: vX.Y.Z
Latest: vA.B.C
Changes:
- commit message 1
- commit message 2
...
Update now? (This will pull latest 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.
- 10d ago First seen · 144 lines · 15 tokens per session scan A 2bfe89001653
productionos-update is a command published in the GitHub repository ShaheerKhawaja/ProductionOS (8 stars, last pushed 4mo ago), licensed MIT. It adds 15 tokens to every session and 977 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
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.
guide
Interactive guide to fellowship. Walks you through a real task using the structured research-plan-implement flow, then shows you what's next.
rekindle
Recover a fellowship after a session crash. Scans worktrees and quest state, presents a recovery dashboard, and re-spawns Gandalf with recovered quest context. Use when returning to a crashed or expired fellowship session.
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.
scribe
Create a reusable quest template for a specific type of task (e.g., "API endpoint", "migration"). Encodes project-specific rules and conventions into phase guidance that loads automatically during quests.