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 JakubMikolajek/codex-skills-collection --skill multi-repogit clone --depth 1 https://github.com/JakubMikolajek/codex-skills-collectionWrote 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/jakubmikolajek/codex-skills-collection/multi-repo)<a href="https://agentmods.dev/skills/jakubmikolajek/codex-skills-collection/multi-repo"><img src="https://agentmods.dev/badge/skills/jakubmikolajek/codex-skills-collection/multi-repo/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/jakubmikolajek/codex-skills-collection/multi-repo"><img src="https://agentmods.dev/badge/skills/jakubmikolajek/codex-skills-collection/multi-repo.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.00036 | $0.00956 |
| Opus 5 | $0.00018 | $0.00478 |
| Sonnet 5 | $0.00007 | $0.00191 |
| Haiku 4.5 | $0.00004 | $0.00096 |
Grade A, and why
multi-repo 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 12d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multi-Repo Coordination
This skill provides a structured process for coordinating changes that span multiple repositories. It enforces contract-owner-first ordering, cross-repo impact detection, and mandatory handoff documentation.
When to Use
- Changing an API endpoint, request/response shape, or auth contract
- Modifying shared types, interfaces, or proto definitions
- Updating environment variables or config schema used across repos
- Coordinating a release across frontend, backend, and/or mobile
- Database schema changes with consumers in multiple services
When NOT to Use
- Changes affect only one repository — use the appropriate domain skill directly
- Task is about reading or analyzing multiple repos without modifying them
- Cross-repo dependency is only a version bump with no contract change
Core Principles
Map Before Touching Anything
- Identify the contract owner (the repo that defines the shared interface)
- List all consumer repos and their dependency on the contract
- Determine change propagation order: owner first, consumers after
- Confirm which repos are accessible in the current session
Change Propagation Order
- Never modify a consumer repo before the contract owner is updated
- If consumer repos are not accessible, produce a per-repo checklist for manual follow-up
- Each affected repo gets a scoped task description: what changes, why, what to verify
Multi-Repo Process
Use the checklist below and track your progress:
Multi-repo progress:
- [ ] Step 1: Map contract owner and consumers
- [ ] Step 2: Detect cross-repo impact
- [ ] Step 3: Update contract owner first
- [ ] Step 4: Propagate changes to consumers
- [ ] Step 5: Coordinate versioning
- [ ] Step 6: Produce session handoff with per-repo status
Step 1: Map contract owner and consumers
Identify which repo owns the shared interface. List every consumer repo and how it depends on the contract (import, API call, env var, shared type).
Step 2: Detect cross-repo impact
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.
- 12d ago First seen · 113 lines · 36 tokens per session scan A 3ef89ca9fc5e
multi-repo is a skill published in the GitHub repository JakubMikolajek/codex-skills-collection (5 stars, last pushed 6d ago), licensed MIT. It adds 36 tokens to every session and 956 once invoked, about $0.0002 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-31.
Other skills, from other repositories
batch
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
gsd-complete-milestone
Archive completed milestone and prepare for next version.
operating-github-cli
Default GitHub skill for the action agent. Use githubcli for any GitHub request — create/list/view/close issues and PRs, assign, labels, repos, releases, checks, github.com/owner/repo URLs, or gh api. Prefer over shellrun/!gh. Run these with githubcli in the current agent turn.
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.
testdino-releases
Use when the user wants to browse, inspect, create, or update releases/milestones in a TestDino project. Covers listreleases, getrelease, createrelease, and updaterelease. Accepts counter-style IDs like MS-12.
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.