github-init

A command that guides setup of the ClaudeForge continuous integration and delivery system on GitHub. CI/CD means automated checks and release-related workflows run when code changes.

In plain words
What is it for?
Use it to initialize the GitHub workflow system, create or push a dev branch, and configure protection and required checks for main and dev.
Why use it?
It checks the repository setup and explains the required branches, labels, milestones, and branch-protection rules.

Command for Claude Code

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 commands/alirezarezvani/claudeforge/github-init
Clone the repo
git clone --depth 1 https://github.com/alirezarezvani/ClaudeForge

Made for: Claude Code.

Per session 6 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 617 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.00006 $0.00617
Opus 5 $0.00003 $0.00309
Sonnet 5 $0.00001 $0.00123
Haiku 4.5 $0.00001 $0.00062

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

Security

Grade A, and why

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

.claude/commands/github/github-init.md · 96 lines

How it starts

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

GitHub CI/CD Initialization

You are helping the user initialize the ClaudeForge CI/CD system.

Workflow

  1. Check Current State

    • Verify .github/workflows/ directory exists
    • Check if bootstrap workflow has been run (look for labels/milestones)
    • Check if dev branch exists
    • Check branch protection status
  2. Run Bootstrap Workflow

    • If not yet run, guide user to run bootstrap workflow:
      • Go to Actions → Bootstrap Repository → Run workflow
      • Enable all options (create labels, milestones, validate settings)
    • Explain what will be created (23 labels, 3 milestones)
  3. Create Dev Branch (if not exists)

    git checkout -b dev
    git push -u origin dev
    
  4. Configure Branch Protection

    Guide user step-by-step:

    For main branch:

    • Go to Settings → Branches → Add rule
    • Pattern: main
    • Enable:
      • Require PR before merging
      • Require status checks: quality-gates, production-build, validate-release-pr
      • Require linear history
      • Block force pushes
      • Restrict deletions

    For dev branch:

    • Pattern: dev
    • Enable:
      • Require PR before merging
      • Require status checks: quality-gates, validate-pr
      • Require linear history
      • Block force pushes
      • Restrict deletions
  5. Set Default Branch

    • Settings → General → Default branch → Change to dev
    • This ensures new PRs target dev by default
  6. Verification

    • Show current branch protection rules
    • Verify workflows are present
    • Confirm setup is complete
  7. Next Steps

    • Point to docs/GITHUB_WORKFLOWS.md for workflow reference
    • Point to docs/BRANCHING_STRATEGY.md for branch flow
    • Suggest creating first feature branch to test

Commands to provide

# Check current setup
gh repo view --json name,defaultBranchRef,hasIssuesEnabled

# List workflows
ls -la .github/workflows/

# Check labels
gh label list

# Check milestones
gh api repos/:owner/:repo/milestones

# Check branch protection
gh api repos/:owner/:repo/branches/main/protection 2>/dev/null || echo "Not protected"
gh api repos/:owner/:repo/branches/dev/protection 2>/dev/null || echo "Not protected"

Read the full file on GitHub · 96 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 · 96 lines · 6 tokens per session scan A dcae4967ffd8

Subscribe to this mod's changes

github-init is a command published in the GitHub repository alirezarezvani/ClaudeForge (419 stars, last pushed 3mo ago), licensed MIT. It adds 6 tokens to every session and 617 once invoked, about $0.0000 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.