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 monorepo-toolinggit 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/monorepo-tooling)<a href="https://agentmods.dev/skills/jakubmikolajek/codex-skills-collection/monorepo-tooling"><img src="https://agentmods.dev/badge/skills/jakubmikolajek/codex-skills-collection/monorepo-tooling/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/monorepo-tooling"><img src="https://agentmods.dev/badge/skills/jakubmikolajek/codex-skills-collection/monorepo-tooling.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.00073 | $0.02452 |
| Opus 5 | $0.00036 | $0.01226 |
| Sonnet 5 | $0.00015 | $0.00490 |
| Haiku 4.5 | $0.00007 | $0.00245 |
Grade A, and why
monorepo-tooling 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 — 329 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monorepo Tooling
A monorepo is only as good as its tooling. Without caching and task pipelines, a monorepo becomes a slowrepo. This skill covers the patterns that make monorepos fast, coherent, and easy to navigate.
When to Use
- Setting up a new monorepo with multiple apps and shared packages
- Adding a new app or package to an existing monorepo
- CI is running full builds on every change regardless of what changed
- Shared packages are inconsistently versioned or causing dependency conflicts
- Developers complain that
pnpm installor builds are slow
When NOT to Use
- Single-app repositories — monorepo tooling adds overhead without benefit
- Polyrepo architecture where repos are separate by design (use
multi-reposkill) - Python monorepos — different toolchain (uv workspaces, not Turborepo/Nx)
Core Principles
Affected-Only Builds
The entire point of a monorepo build tool is running only the tasks that are affected by what changed. If CI rebuilds everything on every commit, the monorepo tooling is not configured correctly.
Package Boundaries are Contracts
A shared package is a contract with its consumers. Treat it like a library: explicit exports, versioned changes, no circular dependencies between packages.
Caching is Correctness-Critical
A cache hit must produce identical output to a full build. If caching produces wrong results, the cache key is wrong — not the cache. Fix the key, not by disabling caching.
Repository Structure
Standard monorepo layout:
/
├── apps/
│ ├── web/ # Next.js / Nuxt frontend
│ ├── api/ # NestJS / FastAPI backend
│ └── mobile/ # React Native / SwiftUI
├── packages/
│ ├── ui/ # Shared component library
│ ├── config/ # ESLint, TypeScript, Tailwind configs
│ ├── types/ # Shared TypeScript types
│ └── utils/ # Shared utility functions
├── turbo.json # or nx.json
├── package.json # Root workspace config
└── pnpm-workspace.yaml
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 · 329 lines · 73 tokens per session scan A 83a910da42e6
monorepo-tooling is a skill published in the GitHub repository JakubMikolajek/codex-skills-collection (5 stars, last pushed 7d ago), licensed MIT. It adds 73 tokens to every session and 2,452 once invoked, about $0.0004 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
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
managing-github-actions-secrets
Creates and updates GitHub Actions secrets for PostHog workflows. Use when adding a new CI secret, rotating an existing secret, wiring a workflow to an API token, package registry credential, deploy key, or any value referenced via ${{ secrets. }} in .github/workflows/.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.