init

A one-time setup workflow for a Git repository and its GitHub project process.

In plain words
What is it for?
Use it when starting the delivery loop in a repository, connecting GitHub, preparing issue labels, or creating initial check and style-guide files.
Why use it?
It creates the basic files, checks, labels, and settings needed before tasks can move through the delivery process.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/blakemartz/delivery-loop/init
Any agent
npx skills add blakemartz/delivery-loop --skill init
Clone the repo
git clone --depth 1 https://github.com/blakemartz/delivery-loop

Made for: Claude Code, Codex.

Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 850 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00057 $0.00850
Opus 5 $0.00028 $0.00425
Sonnet 5 $0.00011 $0.00170
Haiku 4.5 $0.00006 $0.00085

Measured yesterday against content hash aaee38be0359, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

init 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 yesterday.

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.

plugins/delivery-loop/skills/init/SKILL.md · 39 lines

How it starts

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

init — bootstrap this repo for the delivery loop

One-time, idempotent setup. Runs the bundled bootstrap, then walks the human through the judgment calls the script can't make.

Protocol

  1. Run: bash "${CLAUDE_PLUGIN_ROOT}/scripts/delivery-init.sh" $ARGUMENTS (any arguments become extra module:<name> labels). Local scaffolding runs first — .claude/delivery.conf, .gitignore, a seeded scripts/check.sh (the gate GATE_CMD points at), and a STYLEGUIDES_DIR stub — then the GitHub steps (labels).

  2. No GitHub repo connected (script exits 2). The backlog lives in GitHub Issues, so this is a hard prerequisite. Ask the human which they want (outward-facing — never do it unasked):

    • a brand-new repo: gh repo create <name> --private --source=. --push (confirm name and visibility first), or
    • connect an existing one: git remote add origin <url> and push the base branch. Then re-run the script — it's idempotent and will finish the labels.
  3. Issues disabled (script warns). Common on forks. Ask the human to confirm, then run gh repo edit --enable-issues — without Issues the loop is inert.

  4. Establish the gate — the thing that needs the most judgment. Open the seeded scripts/check.sh and reconcile it with what the repo actually runs, preferring the repo's own declared commands over guessed ones. Check package.json scripts, a Makefile/justfile check/test target, and CI steps in .github/workflows/ for the real commands.

    • Tooling detected: show the human the seeded check.sh, note any declared command it should use instead (e.g. the repo has a make check that bundles more than init found), and adjust on their confirmation.
    • No tooling detected (the seed exits 1 by design — an undefined gate is a failing gate, never a green one): tell the human plainly that no linter/type-checker/test framework was found, and suggest a sensible starter set for the detected language (e.g. ruff + mypy + pytest for Python; eslint + tsc + vitest for TS; go vet/build/test for Go). Wire in whatever they approve; leave the failing guard if they defer.

Read the full file on GitHub · 39 lines

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.

  1. yesterday First seen · 39 lines · 57 tokens per session scan A aaee38be0359

Subscribe to this mod's changes

init is a skill published in the GitHub repository blakemartz/delivery-loop (4 stars, last pushed 1mo ago), licensed MIT. It adds 57 tokens to every session and 850 once invoked, about $0.0003 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.