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 agentmods add commands/alirezarezvani/claudeforge/github-initgit clone --depth 1 https://github.com/alirezarezvani/ClaudeForgeWhat 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 | $0.00006 | $0.00617 |
| Opus 5 | $0.00003 | $0.00309 |
| Sonnet 5 | $0.00001 | $0.00123 |
| Haiku 4.5 | $0.00001 | $0.00062 |
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.
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
-
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
- Verify
-
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)
- If not yet run, guide user to run bootstrap workflow:
-
Create Dev Branch (if not exists)
git checkout -b dev git push -u origin dev -
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
-
Set Default Branch
- Settings → General → Default branch → Change to
dev - This ensures new PRs target dev by default
- Settings → General → Default branch → Change to
-
Verification
- Show current branch protection rules
- Verify workflows are present
- Confirm setup is complete
-
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"
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.
- yesterday First seen · 96 lines · 6 tokens per session scan A dcae4967ffd8
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.
Other commands, from other repositories
implement
Execute phased implementation with validation gates.
workflow-claude-commands
Track Claude Code commands report changes and find what needs updating.
weather-orchestrator
Fetch Dubai weather and create an SVG weather card.
ingest
Ingest source material into an active wiki. Accepts URLs, file paths, PDFs, freeform text, or processes the inbox. Supports tweets via Grok MCP.
output
Generate output artifacts from active wiki content — summaries, reports, study guides, slide outlines, timelines, glossaries, comparisons. Outputs are filed back into the wiki.
portfolio
Show a read-only hub-wide portfolio of canonical Ideas and active Projects without duplicating topic-owned records.