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-resume)<a href="https://agentmods.dev/commands/shaheerkhawaja/productionos/productionos-resume"><img src="https://agentmods.dev/badge/commands/shaheerkhawaja/productionos/productionos-resume/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-resume"><img src="https://agentmods.dev/badge/commands/shaheerkhawaja/productionos/productionos-resume.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.00028 | $0.00442 |
| Opus 5 | $0.00014 | $0.00221 |
| Sonnet 5 | $0.00006 | $0.00088 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
productionos-resume 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 11d 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 Resume — Restore Pipeline State
Resume work from a previously paused pipeline.
Execution
-
Read checkpoint:
Read .productionos/CHECKPOINT.json If not found: "No checkpoint found. Start a new pipeline with /production-upgrade or /omni-plan." -
Validate state:
- Check that all listed artifacts still exist
- Compare
git diff --name-onlywith saveduncommitted_files - If divergence detected: warn but don't halt
"WARNING: Working tree has changed since pause. {N} new files, {M} missing files."
-
Display status:
[ProductionOS] Resuming pipeline. Command: {command} Paused at: {step} ({timestamp}) Grade: {before} → {current} Artifacts: {N} files in .productionos/ Uncommitted: {N} files -
Route to command:
- Parse the
commandandstepfields - Invoke the appropriate command with a
--resume-fromcontext:/omni-plan→ resume from the saved step number/production-upgrade→ resume from the saved step/auto-swarm→ resume with remaining coverage gaps
- Pass all existing
.productionos/artifacts as prior work (the Preamble's artifact reuse check handles this)
- Parse the
-
Clean up:
- After successful resumption (pipeline reaches completion or next pause): delete CHECKPOINT.json
- If the resumed pipeline fails: keep CHECKPOINT.json for retry
Notes
- Resume is NOT a full context restoration — it provides enough state for the pipeline to skip completed steps
- The Preamble's "Prior work check" (Step 0B) already handles artifact reuse, so most of the context recovery is automatic
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.
- 11d ago First seen · 50 lines · 28 tokens per session scan A 9409ae954bdf
productionos-resume is a command published in the GitHub repository ShaheerKhawaja/ProductionOS (8 stars, last pushed 4mo ago), licensed MIT. It adds 28 tokens to every session and 442 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
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.