Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Destynova2/cli-code-skillsnpx agentmods add skills/destynova2/cli-code-skills/cli-forge-githubWrote 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/destynova2/cli-code-skills/cli-forge-github)<a href="https://agentmods.dev/skills/destynova2/cli-code-skills/cli-forge-github"><img src="https://agentmods.dev/badge/skills/destynova2/cli-code-skills/cli-forge-github/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/destynova2/cli-code-skills/cli-forge-github"><img src="https://agentmods.dev/badge/skills/destynova2/cli-code-skills/cli-forge-github.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.00165 | $0.08109 |
| Opus 5.5 | $0.00066 | $0.03244 |
| Sonnet 5.5 | $0.00033 | $0.01622 |
| Haiku 4.5 | $0.00016 | $0.00811 |
Grade A, and why
cli-forge-github 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 1mo 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 — 583 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Optimization: Heavy content lives in
references/. Load on demand.
Language rule: Skill instructions are written in English. When generating user-facing output, detect the project's primary language (from README, comments, docs, commit messages) and produce the output in that language. If the project is bilingual, ask the user which language to use before proceeding.
Gotchas: Read
../gotchas.mdbefore producing output to avoid known mistakes.
CLI Forge GitHub — Repository Health Auditor & Fixer
"The CI is green, the ruleset says pending, the PR has conflicts, the release is stuck, and 13 branches are dead. Welcome to GitHub."
Rules for the Auditor
- Read before touching. Always
gh apithe current state before proposing changes. Rulesets, branch protections, and workflows interact in non-obvious ways. - Fix the root cause, not the symptom. A PR stuck on "pending" is not fixed by force-merging — find which check is missing and why.
- Never force-push protected branches. Detect the base and release branches (main, develop, master, trunk) and never force-push them. Use
--force-with-leaseon feature branches only. - Prefer API over UI. Rulesets, checks, and branch cleanup are all automatable via
gh api. The UI is for humans reviewing the result. - Document every ruleset change. Add a comment in ci.yml explaining WHY the ruleset requires specific checks. Future you (or a teammate) will re-add the wrong checks if there's no explanation.
- Transient failures get a rerun, not a fix. Rate limits, runner timeouts, and network flakes are not code bugs. Rerun, don't refactor.
- Orphan branches are tech debt. Clean them on every release, not "when we have time".
- Always enable auto-merge on every PR you create. Every
gh pr createis followed bygh pr merge --auto --squash(or--rebase/--mergeper project policy). A PR without auto-merge is a PR somebody has to babysit — that is exactly the state this skill is designed to eliminate. The only exception is a draft PR: auto-merge is enabled when the draft is marked ready, not before. This rule applies to every agent that opens PRs through the skill (including the cli-forge-chef Sous-Chef). - Always check conflicts between parallel PRs before dispatch, not after. When N commis open N parallel PRs against the same base, the file-exclusion is enforced on the commis side (cli-forge-chef PERT + Fiedler partition). On the GitHub side, this skill verifies it didn't leak: for every pair of open PRs against the same base branch, compute the intersection of their changed-files sets; any non-empty intersection is a future merge conflict and must be reported before auto-merge lands the first one. Detection is cheap; post-merge rebasing N-1 branches is not.
- A PR is not done until the client has the fork in it. "Auto-merge enabled" is not "merged". Any session with PRs in flight runs a post-merge landing watchdog (F9) that polls every 45 s, rebases BEHIND branches on cascade, reruns transient failures (max 2× per cause), and only declares "done" once the PR is
MERGED, the release tag is cut (if applicable), orphan branches are deleted, and downstream PRs have been caught up. A brigade achieves this via the Maître d'hôtel role (cli-forge-chef references/maitre-dhotel.md); a single-agent session achieves it by calling F9 directly.
What ships with it
3 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.
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.
- 1mo ago First seen · 583 lines · 165 tokens per session scan A fc35caee6b13
cli-forge-github is a skill published in the GitHub repository Destynova2/cli-code-skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 165 tokens to every session and 8,109 once invoked, about $0.0007 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.
Other skills, from other repositories
hatch3r-release
Cuts a release with version bump, changelog, tagging, and deploy verification. Use when preparing a release, cutting a version, or deploying to production.
ensemble-release
Automated release workflow orchestration with quality gates, smoke test integration, (Codex skill for /ensemble:release).
changelog-generator
Quick Reference - Parse conventional commits and generate categorized changelog.
automating-devops
DevOps knowledge reference covering Git workflows, testing strategies, DevSecOps, release pipeline orchestration (release.yml, multi-arch images, cosign integration), CI/CD pipelines, database management, observability, and performance optimization. Use when working with Git, CI/CD, release pipelines, ghcr image…
release
Use this agent for versioning, changelogs, release notes, deployment coordination, and release process management.
setup-ci
Skill "setup-ci" from ecorkran/context-forge, covering set up ci and release, 1. detect, 2. write ci.yml, 3. write the release skill and template.