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 skills/thiientv/godmode/branch-integrationnpx skills add thiientv/godmode --skill branch-integrationgit clone --depth 1 https://github.com/thiientv/godmodeWrote 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/thiientv/godmode/branch-integration)<a href="https://agentmods.dev/skills/thiientv/godmode/branch-integration"><img src="https://agentmods.dev/badge/skills/thiientv/godmode/branch-integration.svg" alt="Measured on agentmods" 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 | $0.00069 | $0.00336 |
| Opus 5 | $0.00034 | $0.00168 |
| Sonnet 5 | $0.00014 | $0.00067 |
| Haiku 4.5 | $0.00007 | $0.00034 |
Grade A, and why
branch-integration 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 5d 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.
What it actually says
Branch Integration
Finishing is a decision gate, not an automatic merge.
Final inspection
- Run
git statusand inspect the full diff from the intended base. - Check for untracked files, generated artifacts, secrets, unrelated edits, and migration or release notes that belong in the branch.
- Run the relevant focused and broad checks with fresh output.
- Summarize the behavior, evidence, limits, and known follow-ups.
Use completion-verification; a green suite alone does not choose the
integration path.
Present explicit options
- Merge locally: integrate into the target branch after review.
- Open a pull request: preserve the branch for collaborative review.
- Keep the branch: leave it available for later work.
- Discard: delete only after confirming no unique work remains.
Do not push, merge, delete a branch, or remove a worktree unless the user or the repository's explicit automation authorizes that action. If checks are blocked, present the blocked state instead of hiding it in a success summary.
Completion condition
The chosen integration path is recorded, the final diff and evidence match the scope, and cleanup is either performed safely or intentionally deferred.
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.
- 5d ago First seen · 41 lines · 69 tokens per session scan A 81be947c659b
branch-integration is a skill published in the GitHub repository thiientv/godmode (93 stars, last pushed 9d ago), licensed MIT. It adds 69 tokens to every session and 336 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-30.
Other skills, from other repositories
agent-evaluation-v2
Agent Evaluation workflow skill. Use this skill when the user needs Testing and benchmarking LLM agents including behavioral testing, and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
agent-evaluation
Agent Evaluation workflow skill. Use this skill when the user needs Testing and benchmarking LLM agents including behavioral testing, and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
agent-evaluation-v3
Agent Evaluation workflow skill. Use this skill when the user needs Testing and benchmarking LLM agents including behavioral testing, and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
rulesync
Generates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI coding configurations.
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.
loop
Full execution protocol for MODE: LOOP — the compound-engineering loop: brainstorm → plan → build → review → improve, iterating under defense-in-depth stop conditions with generator/critic separation, durable resumable state, and mandatory compounding learning capture. Loaded on demand by the architect when the loop…