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 atretyak1985/swarmery --skill monorepo-coordinationgit clone --depth 1 https://github.com/atretyak1985/swarmeryWrote 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/atretyak1985/swarmery/monorepo-coordination)<a href="https://agentmods.dev/skills/atretyak1985/swarmery/monorepo-coordination"><img src="https://agentmods.dev/badge/skills/atretyak1985/swarmery/monorepo-coordination/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/atretyak1985/swarmery/monorepo-coordination"><img src="https://agentmods.dev/badge/skills/atretyak1985/swarmery/monorepo-coordination.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.00057 | $0.00759 |
| Opus 5.5 | $0.00023 | $0.00304 |
| Sonnet 5.5 | $0.00011 | $0.00152 |
| Haiku 4.5 | $0.00006 | $0.00076 |
Grade A, and why
monorepo-coordination 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Plan and sequence changes that span multiple repositories (or multiple monorepo apps/packages) so they land in the correct order, with CI-probe-enforced operator gates and post-merge validation of the whole system. Done when every repo is phased, each MR/PR carries dependency arrows and failure modes, and every operator step has a probe.
Rules
- Read the repo shape from
${CLAUDE_PROJECT_DIR}/.claude/project.json(repos,monorepo) before planning — the phase model is identical for both shapes; only merge mechanics differ. - Merge order follows the phase model: 1 Foundation → 2 Operator action → 3 Wire consumers → 4 Consume. Never wire before foundation.
- Every operator step gets a CI probe that fails if skipped — MR prose alone is never a gate.
- When a contracted cross-service boundary changes, read the living contract document FIRST (see
api-contract) and place its update no later than the emitter change. - Each MR is individually revert-safe; its description carries Depends on, Blocks, Operator steps, and Failure mode if merged out of order.
- Use durable identifiers (file paths), never transient MR numbers; immutable digests, never mutable tags, in cross-repo handoffs.
Resources
- Read
resources/phase-model-and-procedure.mdwhen building the plan — repo-shape detection, when (not) to use, inputs/outputs, the output template, and the six-step procedure with MR and CI-probe boilerplate. - Read
resources/checks-and-examples.mdbefore returning — self-check, common mistakes, escalation triggers, worked scenarios, failure modes, related skills.
How to use
What it does
Plans the landing order for a change touching multiple repositories — or multiple independently deployed monorepo apps: a phased merge order, MR/PR descriptions spelling out dependencies, CI probes that fail when a manual step was skipped, and a post-merge checklist.
When to use it
- A change spans two or more repos, or monorepo packages that deploy independently.
- A runtime env var seeded in one place, wired in another, read by the app.
- A message-format change crosses a contracted device↔app boundary.
- Not for single-repo changes (
refactor-plan), hotfixes, dependency bumps, or image promotion.
What ships with it
2 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 · 59 lines · 57 tokens per session scan A 65723f0f4750
monorepo-coordination is a skill published in the GitHub repository atretyak1985/swarmery (7 stars, last pushed today), licensed Apache-2.0. It adds 57 tokens to every session and 759 once invoked, about $0.0002 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
claim
Acquire, renew or release a Fakoli State task lease when beginning work or recovering an interrupted claim.
state-ops
Inspect the Fakoli State project summary, task details, ready queue, active claims and local reconciliation when orienting or diagnosing blocked work.
pipeline-conductor
Operating procedure for the kirocrew-pipeline-conductor agent. Use when a pipeline conductor session is seeded, inspected or debugged. You MANAGE one issue/PR pipeline on one repo: two columns per item (session working? item solved?), send intent, never re-derive a red yourself.
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
create-milestone
Create a GitHub milestone for an upcoming release. Suggests the next version based on the latest release, gathers all merged PRs and closed issues since that release, presents a draft with two tables (Issues and PRs) for user approval, then creates the milestone and assigns all approved items.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.