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 dungnotnull/hybrid-harness-chaos-process-prm --skill s00-orchestratorgit clone --depth 1 https://github.com/dungnotnull/hybrid-harness-chaos-process-prmWrote 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/dungnotnull/hybrid-harness-chaos-process-prm/s00-orchestrator)<a href="https://agentmods.dev/skills/dungnotnull/hybrid-harness-chaos-process-prm/s00-orchestrator"><img src="https://agentmods.dev/badge/skills/dungnotnull/hybrid-harness-chaos-process-prm/s00-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/dungnotnull/hybrid-harness-chaos-process-prm/s00-orchestrator"><img src="https://agentmods.dev/badge/skills/dungnotnull/hybrid-harness-chaos-process-prm/s00-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.00116 | $0.04363 |
| Opus 5 | $0.00058 | $0.02181 |
| Sonnet 5 | $0.00023 | $0.00873 |
| Haiku 4.5 | $0.00012 | $0.00436 |
Grade A, and why
workflow-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 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 — 408 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow Orchestrator (s00)
Purpose
Serve as the single entrypoint that coordinates the entire hybrid harness + chaos engineering workflow. This skill maps the full Agile lifecycle, knows the input/output contracts of every skill, and ensures agents follow the correct sequence without skipping steps.
Prerequisites
- CLAUDE.md read and loaded into context
-
.commandcode/taste/directory exists for memory persistence - Current project context established (repo, team, stack)
Input Contract
| Input | Source | Required |
|---|---|---|
| User request / project description | User prompt | Yes |
| CLAUDE.md (project rules) | Repository root | Yes |
Taste file (.commandcode/taste/taste.md) |
Project repo | No (created if absent) |
Progress state (.commandcode/progress.json) |
Previous runs | No (created if absent) |
Output Contract
| Output | Destination | Format |
|---|---|---|
| Workflow phase decision | Next skill invocation | Text + structured context |
| Updated progress state | .commandcode/progress.json |
JSON |
| Cross-skill context handoff | Next skill's input | Structured YAML |
| Phase completion summary | User + progress tracker | Markdown |
Complete Agile Workflow Map
PHASE 0: FOUNDATION
s00 → s01 → s02 + s03 (parallel)
│
PHASE 1: PLANNING & REQUIREMENTS
s01 (BA deep analysis → PRD + ADRs + backlog)
│
PHASE 2: CI/CD SCAFFOLDING
s04 → s05 → s06 → s07 → s08 → s09 → s10
(pipeline design → service onboard → delegate → secrets → FF → templates → GitOps)
│
PHASE 3: SECURITY GATE
s11 (SAST + SCA + container + secrets + IaC + SBOM + SLSA)
â ï¸ BLOCKS all downstream if security gates fail
│
PHASE 4: TESTING
s12 → s13 (CloakBrowser E2E + baseline → Performance/load profiling)
â ï¸ Performance baseline required before chaos experiments
│
PHASE 5: CHAOS EXPERIMENT DESIGN
s17 → s14 → s15 → s16 → s18 → s19
\(steady state → experiment → hypothesis → blast radius → infra faults → app faults\)
│
PHASE 6: GAME DAY EXECUTION
s20 (orchestrated resilience exercise)
│
PHASE 7: VERIFICATION & OBSERVABILITY
s21 → s22 → s23
(CV verification → observability integration → alerting & recommendations)
│
PHASE 8: GOVERNANCE
s24 → s25 → s26 → s27 → s28
(policy → cost → resilience scoring → postmortem → release management)
│
PHASE 9: RESILIENCE & CONTINUITY
s29 → s30
(disaster recovery → compliance & audit)
STRATEGIC INNOVATION (s31 — callable at ANY phase)
Invoked when user says "think bigger", "brainstorm", "what am I missing",
"upgrade requirements", "strategic review", "innovate"
→ s31 produces proposals + trade-off analysis (advisory only)
→ If user accepts a proposal, dispatches to relevant implementation skill
→ If user declines, workflow continues from current phase unchanged
FEEDBACK LOOP:
s27 (postmortem findings) → s01 (re-analysis) → full cycle
s30 (compliance gaps) → s01 (PRD update) → remediation cycle
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 · 408 lines · 116 tokens per session scan A efa8502cea57
workflow-orchestrator is a skill published in the GitHub repository dungnotnull/hybrid-harness-chaos-process-prm (19 stars, last pushed 3mo ago), licensed MIT. It adds 116 tokens to every session and 4,363 once invoked, about $0.0006 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-30.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.