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 skills add dbc-oduffy/coordinator-claude --skill merging-to-maingit clone --depth 1 https://github.com/dbc-oduffy/coordinator-claudeWrote 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/dbc-oduffy/coordinator-claude/merging-to-main)<a href="https://agentmods.dev/skills/dbc-oduffy/coordinator-claude/merging-to-main"><img src="https://agentmods.dev/badge/skills/dbc-oduffy/coordinator-claude/merging-to-main/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/dbc-oduffy/coordinator-claude/merging-to-main"><img src="https://agentmods.dev/badge/skills/dbc-oduffy/coordinator-claude/merging-to-main.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.00020 | $0.02726 |
| Opus 5.5 | $0.00008 | $0.01090 |
| Sonnet 5.5 | $0.00004 | $0.00545 |
| Haiku 4.5 | $0.00002 | $0.00273 |
Grade A, and why
merging-to-main 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 6d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 6d ago Changed 03b54d8e41ff
- 10d ago Changed · -7 lines 94a60a838e02
- 11d ago Changed 11b13f988050
- 12d ago Changed · +7 lines a68943ee53d0
- 17d ago Changed · -3 lines e5e93445b979
- 20d ago Changed · -3 lines 247b81aaada4
- 25d ago Changed · -32 lines · -6 tokens per session cd71704e4941
- 28d ago Changed 789eda1b9872
- 1mo ago Changed · +5 lines d9652d62a057
- 1mo ago First seen · 235 lines · 26 tokens per session scan A 23221aae7cce
merging-to-main is a skill published in the GitHub repository dbc-oduffy/coordinator-claude (6 stars, last pushed 4d ago), with no licence file. It adds 20 tokens to every session and 2,726 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-09-03.
Other skills, from other repositories
pipeline-digest
Daily release-pipeline digest with a change gate — reports which plugins are pending release, whether main's CI is green, and which branches went stale, and notifies the operator only when that state actually moved since the last run. Use when the operator asks "what moved in the pipeline", "anything to ship"…
upstream
Opt-in upstream contribution workflow for process improvements and field lessons. Scans the consuming repo's local AGENTS.md, {{ agentsdir }}/team.toml, and commit history for emergent rules, sanitizes sensitive client context, formats governed rule origins, and drafts an upstream Pull Request or Issue to the upstream…
open-pr
Use this skill to submit the commits on the current branch as one pull request against a GitHub repository. Push the branch, open the PR with an imperative title and a body that names what changed and why, and post a follow-up ping only when CODEOWNERS resolves to one person. One branch per run, one pull request per…
pre-release-review
Run the pre-release gate for this multi-plugin monorepo: establish each plugin's release boundary from its last reachable tag to HEAD, audit every changed plugin's [Unreleased] changelog against the actual code diff, identify contract-surface and breaking changes, and, per the objective the user picks up front, either…
pipeline-digest
Daily release-pipeline digest with a change gate — reports which plugins are pending release, whether main's CI is green, and which branches went stale, and notifies the operator only when that state actually moved since the last run. Use when the operator asks "what moved in the pipeline", "anything to ship"…
especialista-em-github
Especialista em GitHub. Use para Pull Requests, Releases, Issues, Actions, Projects e Milestones, além de fluxo de colaboração e automação no GitHub. Palavras-chave: GitHub, PR, release, issue, actions, milestone, projects, gh.