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/refine)<a href="https://agentmods.dev/commands/shaheerkhawaja/productionos/refine"><img src="https://agentmods.dev/badge/commands/shaheerkhawaja/productionos/refine.svg" alt="Measured on agentmods" 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.00036 | $0.01868 |
| Opus 5 | $0.00018 | $0.00934 |
| Sonnet 5 | $0.00007 | $0.00374 |
| Haiku 4.5 | $0.00004 | $0.00187 |
Grade A, and why
refine 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 8d 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 — 254 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/refine -- RLM SelfRefine Pipeline
Step 0: Preamble
Before executing, run the shared ProductionOS preamble (templates/PREAMBLE.md).
You are the RLM Refine orchestrator. You process pending signals from the RLM classifier, showing the user flagged outputs and applying L17 SelfRefine to improve them.
Input
- Mode: $ARGUMENTS.mode (default: interactive)
- Max signals: $ARGUMENTS.max_signals (default: 10)
Step 1: Load Pending Signals
Read pending signals from ~/.productionos/recursive/pending/:
python3 -c "
import json, os
from pathlib import Path
pending_dir = Path(os.path.expanduser('~/.productionos/recursive/pending'))
if not pending_dir.exists():
print(json.dumps({'signals': [], 'count': 0}))
else:
signals = []
for f in sorted(pending_dir.glob('*.json')):
try:
data = json.loads(f.read_text())
if not data.get('reviewed', False):
data['_path'] = str(f)
signals.append(data)
except: pass
print(json.dumps({'signals': signals, 'count': len(signals)}, indent=2, default=str))
"
If no unreviewed signals exist, report: "No pending signals to review. All outputs have been reviewed." and exit.
Step 2: Display Signal Summary
For each pending signal, display:
SIGNAL {id} [{verdict}] — Tool: {tool_name} — Score: {score:.2f}
Agent: {agent_id or "session"}
Time: {formatted_timestamp}
Dimensions:
- {dimension_name}: {score} — {reason}
- ...
Group signals by verdict: show BLOCKs first (highest priority), then FLAGs.
Step 3: Process Each Signal
For BLOCK signals:
BLOCKed outputs indicate serious quality issues. In interactive mode:
- Display the full signal details including all dimension scores
- Ask the user: "This output was BLOCKED. Options: [A]ccept anyway, [R]eject, [S]kip"
- Based on response:
- Accept: Mark as
reviewed: true, human_verdict: "accept", log to metrics - Reject: Mark as
reviewed: true, human_verdict: "reject", log to metrics - Skip: Leave unreviewed for next session
- Accept: Mark as
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.
- 8d ago First seen · 254 lines · 36 tokens per session scan A eb18905f2528
refine is a command published in the GitHub repository ShaheerKhawaja/ProductionOS (8 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 1,868 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
settings
View or edit fellowship configuration (/.claude/fellowship.json). Run /settings to see current settings, change values, or reset to defaults.
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.
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.
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.