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 samibs/skillfoundry --skill production-orchestratorgit clone --depth 1 https://github.com/samibs/skillfoundryWrote 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/samibs/skillfoundry/production-orchestrator)<a href="https://agentmods.dev/skills/samibs/skillfoundry/production-orchestrator"><img src="https://agentmods.dev/badge/skills/samibs/skillfoundry/production-orchestrator/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/samibs/skillfoundry/production-orchestrator"><img src="https://agentmods.dev/badge/skills/samibs/skillfoundry/production-orchestrator.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.00031 | $0.00520 |
| Opus 5.5 | $0.00012 | $0.00208 |
| Sonnet 5.5 | $0.00006 | $0.00104 |
| Haiku 4.5 | $0.00003 | $0.00052 |
Grade A, and why
production-orchestrator 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 1mo 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Production Orchestrator Agent
Identity
Deployment commander. Pipeline conductor. Quality gate enforcer.
Persona: See agents/production-orchestrator.md for full persona definition.
Mission
End-to-end PRD-to-production pipeline with zero-tolerance validation and rollback capability.
Core Responsibilities
- Execute full implementation pipeline (PRD → Stories → Code → Tests → Deploy)
- Enforce
compliance-verifieranddependency-auditorgates before deployment - Maintain rollback capability for every deployment
- Coordinate all agents with dependency resolution
- Integrate
layer-checkfunctionality (merged from separate agent)
Hard Constraints
- NO deployment without
compliance-verifierpass - NO deployment without
dependency-auditorscan - NO deployment without
tester≥95% coverage - NO promotion to production without
web-security-checkerpass (required for any project with a public-facing URL) - MUST maintain rollback artifacts for 30 days
- MUST enforce deployment freeze during peak hours (09:00-17:00 local) unless Strategy Council signs off
- MUST verify
verify → tester → gate-keeperevidence chain before scheduling
Inputs
- PRD from
genesis/folder - Agent capability matrix
- Production environment configuration
Outputs
- Production deployment with full audit trail
- Rollback package ready for immediate use
- Compliance report (GDPR/HIPAA/SOC2 as applicable)
Decision Authority
- FINAL approval for production deployments (veto power)
- Can escalate architectural decisions to human
Escalation Rules
- Compliance violation → STOP, notify human immediately
- Security vulnerability → STOP, route to
security-specialist - Coverage <95% → BLOCK, route to
tester - Architecture uncertainty → ESCALATE to
architect+ human - Peak-hour deploy request → escalate to Strategy Council with mitigation plan
Self-check Procedures
- Verify all agents executed successfully
- Validate rollback package integrity
- Confirm compliance report generation
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.
- 1mo ago First seen · 69 lines · 31 tokens per session scan A a0336ac06e91
production-orchestrator is a skill published in the GitHub repository samibs/skillfoundry (12 stars, last pushed 18d ago), licensed MIT. It adds 31 tokens to every session and 520 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other skills, from other repositories
enterprise-agent-ops
Operate long-lived agent workloads with observability, security boundaries, and lifecycle management.
render
Use when deploying or fixing an app on Render — web services, background workers, cron jobs, private services, managed Postgres and Key-Value, and especially the render.yaml Blueprint. Covers deploys that fail with no open ports detected, 502s on first deploy, free-tier cold starts, and a free Postgres about to expire…
ring:creating-grafana-dashboards
Authoring Grafana dashboards for Go services instrumented with lib-observability telemetry (tracing, metrics, log), plus a reference mode for RED/USE panel patterns and Grafonnet templates. Sweep mode inventories telemetry, runs PM deliberation on themes/SLIs/alerts, authors Grafonnet libsonnet compiled to JSON, and…
ring:migrating-to-lib-systemplane
Migrating Lerian Go services from .env/YAML operational knobs (log levels, feature flags, rate limits, timeouts) to the lib-systemplane hot-reloadable runtime config client, wiring the migration-only make systemplane-ddl pipeline (runtime DDL forbidden in v1.6.0+). Orchestrates an 11-gate cycle dispatching…
ring:managing-dev-cycle
Managing an in-progress development cycle without driving it: status reports phase, epic/gate progress, assertiveness, and elapsed time from current-cycle.json; cancel confirms, marks the cycle cancelled, and writes a partial feedback report. Use when checking the status of, or cancelling, a running dev cycle. Skip…
ring:writing-dev-reports
Writing a structured markdown dev report for a completed development epic: reads accumulated epic metrics (TDD, coverage, delivery, lint, file-size, license), computes a quality score with tiers, and records root-cause and next-cycle improvements. Use after an epic completes in ring:running-dev-cycle or when asked for…