A runbook generator that turns a YAML work plan into draft GitHub issues. It creates a parent tracking issue, grouped child workstream issues, sequential batches, phase gates, and a script for creating them.

Use it to validate a runbook specification, generate issue and summary files, and prepare an idempotent GitHub CLI script for later issue creation.

It organizes large projects into reviewable workstreams without publishing issues automatically.

How aram-devdocs/plumb configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to aram-devdocs/plumb. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/aram-devdocs/plumb/main/.agents/skills/gh-runbook/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/aram-devdocs/plumb

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/aram-devdocs/plumb/gh-runbook/github.svg)](https://agentmods.dev/skills/aram-devdocs/plumb/gh-runbook)

Your own site

<a href="https://agentmods.dev/skills/aram-devdocs/plumb/gh-runbook"><img src="https://agentmods.dev/badge/skills/aram-devdocs/plumb/gh-runbook/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/aram-devdocs/plumb/gh-runbook"><img src="https://agentmods.dev/badge/skills/aram-devdocs/plumb/gh-runbook.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,176 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00058	$0.01176
Opus 5.5	$0.00023	$0.00470
Sonnet 5.5	$0.00012	$0.00235
Haiku 4.5	$0.00006	$0.00118

Measured 2mo ago against content hash b93145ab327d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

gh-runbook 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 2mo ago.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/generate_runbook.py, scripts/validate_skill.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

.agents/skills/gh-runbook/SKILL.md · 110 lines

How it starts

The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/gh-runbook — spec-driven runbook generator

Turn a PRD-phase spec into a parent tracking issue + N child workstream issues + an idempotent gh issue create script. Target repo: aram-devdocs/plumb.

Use /gh-issue afterwards to drive each child issue through the delivery lifecycle.

Usage

/gh-runbook docs/runbooks/phase-1-spec.yaml --dry-run
/gh-runbook docs/runbooks/phase-1-spec.yaml --output-dir .agents/runs/gh-runbook/phase-1/
/gh-runbook docs/runbooks/roadmap-spec.yaml --output-dir .agents/runs/gh-runbook/roadmap/

The underlying script:

python3 .agents/skills/gh-runbook/scripts/generate_runbook.py \
    docs/runbooks/phase-1-spec.yaml \
    --output-dir .agents/runs/gh-runbook/phase-1/ \
    --dry-run

Workflow

Read the spec YAML. Validate it against schemas/runbook-spec.json (via cargo xtask validate-runbooks if available, or via the generator's --validate-only mode).
Render the parent issue body from assets/parent-issue-template.md with all batches laid out as sub-sections.
Render one child issue body per child from assets/child-issue-template.md.
Emit manifest.json, summary.md, create-issues.sh in the output directory.
Review summary.md.
Only execute create-issues.sh after approval — it creates the real GitHub issues and updates the parent body with real issue numbers.

Spec schema

See references/spec-format.md for the full YAML grammar. A minimal skeleton:

schema: https://plumb.aramhammoudeh.com/schemas/runbook-spec.json
name: "Phase N — <headline>"
phase_number: N
repo: aram-devdocs/plumb

parent:
  title: "[RUNBOOK] Phase N — <headline>"
  labels: [phase-N, kind:rfc]
  milestone: "v0.N"
  summary: |
    <1–3 paragraph description>
  acceptance_criteria:
    - <objective gate for unlocking next phase>
  related_prd_sections: ["§10.3"]

batches:
  - id: "NA"
    description: "Foundation — independent, parallel"
    parallel: true
    issues:
      - slug: cdp-chromium-launch
        title: "feat(cdp): Chromium detection, launch, BYO-Chromium"
        labels: ["area:cdp", "kind:feat", "phase-N"]
        crate: plumb-cdp
        effort: M
        prd_refs: ["§10.6"]
        summary: |
          <purpose>
        acceptance_criteria:
          - bullet 1
        reviewers: ["02-spec-reviewer", "03-code-quality-reviewer", "05-architecture-validator", "06-security-auditor"]

phase_gate:
  criterion: |
    `just validate` passes AND <phase-specific check>.
  unblocks: "phase-(N+1)"

Read the full file on GitHub · 110 lines

Files

What ships with it

5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

2mo ago First seen · 110 lines · 58 tokens per session scan A b93145ab327d

Subscribe to this mod's changes

gh-runbook is a skill published in the GitHub repository aram-devdocs/plumb (3 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 58 tokens to every session and 1,176 once invoked, about $0.0002 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-08-31.

Planning Project management chromium cli css design-system design-tokens developer-tools

extract-design

Extract the full design language from any website URL. Produces 8 output files including AI-optimized markdown, visual HTML preview, Tailwind config, React theme, shadcn/ui theme, Figma variables, W3C design tokens, and CSS variables. Also runs WCAG accessibility scoring. Use when user says 'extract design', 'get…

Manavarya09/design-extract · 140 tokens

designlang-tokens

Use when styling UI for cal.com — references the extracted design system tokens instead of inventing colors, spacing, or typography.

Manavarya09/design-extract · 30 tokens

design-md-extractor

Extract and document the visual style of public websites as reusable DESIGN.md files. Use when the user asks to analyze a website's design system, extract styles, create design tokens, produce DESIGN.md, generate an agent-readable style guide, or build from a website's visual language.

jpoindexter/design-md-extractor · 60 tokens

omd-apply

A skill that applies a project's DESIGN.md file as visual and brand guidance for interface work. It covers components, colors, fonts, layout, copy, motion, and visual assets.

kwakseongjae/oh-my-design · 129 tokens

bench-fixture-gen

Generates the shared per-task fixture that every competing arm starts from: a realistic dataset plus an image asset base. Fairness rule: fixtures are generated ONCE per task by this preprocessor and sealed (sha256) before any arm runs; arms never generate their own.

kwakseongjae/oh-my-design · 0 tokens

contribution-workflow

Design or document how new work enters a design system: contribution types, proposal criteria, review stages, sign-off and release. Triggers: contribution process, how should someone contribute, contribution guidelines, adding a new component. Not for audit findings to tickets (backlog-generator).

murphytrueman/design-system-ops · 60 tokens

plumb: Skill for Claude Code