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 hoangatg/ai-agent-toolkit --skill monorepo-managementgit clone --depth 1 https://github.com/hoangatg/ai-agent-toolkitWrote 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/hoangatg/ai-agent-toolkit/monorepo-management)<a href="https://agentmods.dev/skills/hoangatg/ai-agent-toolkit/monorepo-management"><img src="https://agentmods.dev/badge/skills/hoangatg/ai-agent-toolkit/monorepo-management/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/hoangatg/ai-agent-toolkit/monorepo-management"><img src="https://agentmods.dev/badge/skills/hoangatg/ai-agent-toolkit/monorepo-management.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.00043 | $0.00787 |
| Opus 5 | $0.00022 | $0.00394 |
| Sonnet 5 | $0.00009 | $0.00157 |
| Haiku 4.5 | $0.00004 | $0.00079 |
Grade A, and why
monorepo-management 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 7d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monorepo Management
One repo, many packages. Shared code, independent deploys.
1. Tool Selection
| Tool | Best For |
|---|---|
| Turborepo | JavaScript/TypeScript, simple setup |
| Nx | Full-featured, plugins, any language |
| pnpm Workspaces | Package management (often paired with Turbo/Nx) |
| Lerna | Legacy, publishing-focused |
| Bazel | Very large scale, polyglot |
2. Structure
Recommended Layout
monorepo/
├── apps/ # Deployable applications
│ ├── web/ # Next.js frontend
│ ├── mobile/ # React Native app
│ └── api/ # Backend server
├── packages/ # Shared libraries
│ ├── ui/ # Shared UI components
│ ├── config/ # Shared configs (ESLint, TS)
│ ├── utils/ # Shared utilities
│ └── types/ # Shared TypeScript types
├── turbo.json # Turborepo config
├── pnpm-workspace.yaml
└── package.json # Root package
3. Dependency Management
| Principle | Application |
|---|---|
| Internal packages | Reference via workspace protocol workspace:* |
| Shared deps | Hoist common dependencies to root |
| Version sync | Same version of React across all apps |
| Dev deps | Config packages (ESLint, TypeScript) shared |
4. Build Optimization
Turborepo Features
| Feature | Impact |
|---|---|
| Remote caching | Skip builds already done by teammates |
| Task pipelines | Define build order dependencies |
| Parallel execution | Build independent packages simultaneously |
| Pruning | Deploy only needed packages |
Pipeline Config
Only rebuild what changed:
├── Package A changed → Rebuild A + dependents
├── Package B unchanged → Cache hit ✅
└── App X depends on A → Rebuild X
5. CI/CD for Monorepos
| Strategy | Approach |
|---|---|
| Affected only | Build/test only changed packages |
| Remote cache | Share build cache across CI runs |
| Parallel | Run tests per package in parallel |
| Deploy independently | Each app has its own deploy pipeline |
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.
- 7d ago First seen · 115 lines · 43 tokens per session scan A 990698aaa68b
monorepo-management is a skill published in the GitHub repository hoangatg/ai-agent-toolkit (1 stars, last pushed 5mo ago), licensed MIT. It adds 43 tokens to every session and 787 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-09-03.
Other skills, from other repositories
gentle-ai-collab-perfect
Trigger: contributing to Gentleman-Programming/gentle-ai as an external collaborator. Strict issue-first workflow, honest PR bodies, contributor-vs-maintainer scope, chained-PR strategy, verification protocol, docstring coverage. Load whenever the active repo is Gentleman-Programming/gentle-ai and any part of the…
branch-pr
Create Gentle AI pull requests with issue-first checks. Trigger: creating, opening, or preparing PRs for review.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
chained-pr
Trigger: PRs over 400 lines, stacked PRs, review slices. Split oversized changes into chained PRs that protect review focus.
memorix-git-memory
Use when the task depends on commit history, what changed, when a fix shipped, or linking engineering evidence to reasoning memory.
finishing-a-development-branch
Use when development work is complete and you need to prepare for merge. Guides through cleanup, testing, documentation, and creating a well-structured pull request.