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-stats)<a href="https://agentmods.dev/commands/shaheerkhawaja/productionos/productionos-stats"><img src="https://agentmods.dev/badge/commands/shaheerkhawaja/productionos/productionos-stats/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-stats"><img src="https://agentmods.dev/badge/commands/shaheerkhawaja/productionos/productionos-stats.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.00032 | $0.00446 |
| Opus 5 | $0.00016 | $0.00223 |
| Sonnet 5 | $0.00006 | $0.00089 |
| Haiku 4.5 | $0.00003 | $0.00045 |
Grade A, and why
productionos-stats 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 12d 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.
What it actually says
/productionos-stats — System Dashboard
Display a comprehensive stats dashboard for the current ProductionOS installation.
Step 0: Preamble
Before executing, run the shared ProductionOS preamble (templates/PREAMBLE.md).
Step 1: Run Stats Dashboard
Execute the stats dashboard script:
bun run scripts/stats-dashboard.ts
The script computes and outputs all metrics in structured markdown format.
Metrics Computed
System Metrics
- Version — from
VERSIONfile - Agent count — total
.mdfiles inagents/with HIGH/MEDIUM/LOW stakes breakdown - Command count — total
.mdfiles in.claude/commands/ - Hook count — unique hook scripts referenced in
hooks/hooks.json - Template count — total
.mdfiles intemplates/ - Script count — total
.tsfiles inscripts/ - Test file count — total
.tsfiles intests/
Learning Metrics
- Project instincts — patterns learned for the current project
- Global instincts — cross-project patterns (confidence > 0.8)
- Session handoffs — auto-generated handoff documents
- Skill usage events — total events in analytics log
Git Activity
- Total commits —
git rev-list --count HEAD - Commits today —
git log --oneline --since=midnight - Last handoff — most recent session handoff document
Output Format
The dashboard outputs a markdown table for each category, suitable for display in Claude Code's conversation.
Use Cases
- Run after a sprint to see what was shipped (new agents, commands, hooks)
- Check learning progress (instinct accumulation across sessions)
- Verify installation completeness (all counts match expected values)
- Share stats in session handoff documents for continuity
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.
- 12d ago First seen · 56 lines · 32 tokens per session scan A 290e6e6b57d3
productionos-stats 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 446 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 quest state, 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.