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 skills add ShaheerKhawaja/ProductionOS --skill productionosgit 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/skills/shaheerkhawaja/productionos/productionos)<a href="https://agentmods.dev/skills/shaheerkhawaja/productionos/productionos"><img src="https://agentmods.dev/badge/skills/shaheerkhawaja/productionos/productionos/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/skills/shaheerkhawaja/productionos/productionos"><img src="https://agentmods.dev/badge/skills/shaheerkhawaja/productionos/productionos.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.00039 | $0.00782 |
| Opus 5 | $0.00019 | $0.00391 |
| Sonnet 5 | $0.00008 | $0.00156 |
| Haiku 4.5 | $0.00004 | $0.00078 |
Grade A, and why
productionos 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.
How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ProductionOS
ProductionOS is a dual-target AI engineering operating system with 80 agents, 41 commands, and 18 hooks.
Use this skill to translate the Claude-oriented workflow specs in this repo into Codex-native execution.
Start Here
- Read
README.mdfor the product overview andCLAUDE.mdfor the current command catalog. - Treat
.claude/commands/*.mdas workflow specs, not literal Codex slash commands. - Use
docs/CODEX-PARITY-HANDOFF.mdas the source of truth for target support and parity coverage. - Load only the agent files in
agents/that matter for the chosen workflow. - Use
templates/andprompts/only when the selected command or agent points to them.
Codex Workflow Mapping
production-upgrade— Run a repo audit, prioritize high-leverage defects, implement bounded fixes, then validate before reporting.review— Use Codex in review mode and report concrete findings before summaries.plan-ceo-review— Challenge scope, tighten user value, and surface expansion opportunities explicitly.plan-eng-review— Lock architecture, trust boundaries, error paths, and test coverage before implementation.security-audit— Inspect auth, secrets, input handling, and deployment risk with findings-first output.designer-upgrade— Build a UX audit and redesign plan, then route into interface work when needed.ux-genie— Map user flows, identify friction, and translate findings into concrete improvements.auto-swarm— Run the workflow serially by default in Codex, or delegate only when the user explicitly wants parallel work.auto-swarm-nth— Repeat swarm-style execution until gaps close, while translating agent waves into Codex-native orchestration.omni-plan— Chain the major review and execution patterns in a Codex-native sequence without Claude-only assumptions.omni-plan-nth— Iterate the full orchestration loop until quality targets are met or clearly plateau.
Guardrails
- Do not claim Claude-only hooks, slash commands, or marketplace flows can run directly in Codex.
- Keep work scoped; do not emulate large multi-agent swarms unless the user explicitly wants that overhead.
- Respect the repo's guardrails in
hooks/,.claude-plugin/,.codex-plugin/, andtemplates/. - For packaging or install questions, inspect
.claude-plugin/plugin.json,.claude-plugin/marketplace.json,.codex-plugin/plugin.json,package.json, andREADME.md.
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 · 65 lines · 39 tokens per session scan A 924ae62d5d87
productionos is a skill published in the GitHub repository ShaheerKhawaja/ProductionOS (8 stars, last pushed 4mo ago), licensed MIT. It adds 39 tokens to every session and 782 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 skills, from other repositories
warden
Use before opening a PR from a quest, once the code is written. Simulates a strict code reviewer by comparing changes against reference files and documented conventions, catching convention feedback before your human reviewer does.
great_cto
Use when the CTO describes a feature, task, or project goal. Orchestrates the full SDLC pipeline automatically based on project type.
vertical-hr-recruiting
Domain-knowledge primer for the HR & recruiting vertical (ATS, onboarding, workforce scheduling, engagement). Applied by architect/pm during spec authoring so they aren't naive about hiring pipelines, the admitted offer→onboard data-carry gap, EEO/I-9 compliance, and shift-coverage rules. Stops the four products from…
vertical-real-estate
Residential-proptech domain knowledge so architect / pm aren't naive when speccing real-estate products (listings, lead-crm, transaction-coordination, property-mgmt). Codifies MLS/IDX reality, listing status lifecycle + syndication canonical-source, long-cycle lead nurture, transaction-coordination as the high-pain…
skeptical-triage
Reusable 3-round self-challenge + arbiter pattern for filtering false positives from findings/verdicts. Use when the cost of a false-positive gate block exceeds the cost of 4 extra LLM turns.
vertical-retail
Retail & e-commerce domain knowledge for SMB storefront products (storefront, inventory, pricing, cart-recovery). Codifies the vocabulary (SKU vs variant, reorder point, COGS/margin, ATS, AOV), the non-obvious rules (Shopify owns the storefront — don't fight it head-on; the wedge is multichannel inventory + reorder…