Borrowing it
Nothing to install: this file belongs to ky2renzzz/acp-forge. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ky2renzzz/acp-forge/master/.grok/skills/forge-overlaps/SKILL.mdgit clone --depth 1 https://github.com/ky2renzzz/acp-forgeWrote 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/ky2renzzz/acp-forge/forge-overlaps)<a href="https://agentmods.dev/skills/ky2renzzz/acp-forge/forge-overlaps"><img src="https://agentmods.dev/badge/skills/ky2renzzz/acp-forge/forge-overlaps/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/ky2renzzz/acp-forge/forge-overlaps"><img src="https://agentmods.dev/badge/skills/ky2renzzz/acp-forge/forge-overlaps.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.00035 | $0.00191 |
| Opus 5.5 | $0.00014 | $0.00076 |
| Sonnet 5.5 | $0.00007 | $0.00038 |
| Haiku 4.5 | $0.00003 | $0.00019 |
Grade A, and why
forge-overlaps 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 2mo 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
Forge Overlaps
Detect file-level overlaps between active agent worktrees.
When to Use
- Before merging sub-agent results
- When you suspect two agents edited the same file
- As a pre-merge safety check
How to Run
cd <project-root>
cargo run --manifest-path <path-to-acp-forge>/Cargo.toml -- overlaps
Output
- If no overlaps:
✓ No file overlaps detected. - If overlaps found: lists each pair of branches and the conflicting files
Follow-up
If overlaps are found:
- Review the conflicting files manually
- Decide which branch's changes to keep
- Or merge manually with
git merge-file
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.
- 2mo ago First seen · 33 lines · 35 tokens per session scan A 5e56e281edb2
forge-overlaps is a skill published in the GitHub repository ky2renzzz/acp-forge (5 stars, last pushed 4mo ago), licensed MIT. It adds 35 tokens to every session and 191 once invoked, about $0.0001 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
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…
worktree
Use when the user requests a Git worktree or a development task needs an isolated directory to create, find, reuse, hand off, or clean up. Exclude read-only work, non-Git repositories, and tasks that need no separate branch or directory.
coding-agents-farm
To orchestrate parallel coding-agent farms (Claude, Codex, Copilot, Gemini, etc.) on isolated git worktrees.
gh
You have access to gh (GitHub CLI) for repository and project management.
changelog-writer
Use when a release needs a changelog entry drafted from merged pull requests, grouped by the kind of change rather than by the order they landed.
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup.