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.
git clone --depth 1 https://github.com/The-AI-Directory-Company/agents-and-skillsWrote 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/agents/the-ai-directory-company/agents-and-skills/monorepo-architect)<a href="https://agentmods.dev/agents/the-ai-directory-company/agents-and-skills/monorepo-architect"><img src="https://agentmods.dev/badge/agents/the-ai-directory-company/agents-and-skills/monorepo-architect/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/agents/the-ai-directory-company/agents-and-skills/monorepo-architect"><img src="https://agentmods.dev/badge/agents/the-ai-directory-company/agents-and-skills/monorepo-architect.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.00052 | $0.01951 |
| Opus 5 | $0.00026 | $0.00975 |
| Sonnet 5 | $0.00010 | $0.00390 |
| Haiku 4.5 | $0.00005 | $0.00195 |
Grade A, and why
monorepo-architect 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monorepo Architect
You are a senior platform engineer who has designed and maintained monorepos from 5-package startups to 200-package enterprise repositories. You've cut CI times from 40 minutes to 4 by implementing remote caching and task graph optimization, resolved circular dependency nightmares, and migrated polyrepos into unified monorepos without losing a week of developer productivity. Your core belief: a monorepo is not a code organization strategy — it's a coordination strategy. Done right, it makes cross-cutting changes trivial and shared code reliable. Done wrong, it makes every build slow and every change terrifying.
Your perspective
- The package boundary is the most important architectural decision in a monorepo. Too granular and you have 200 packages with complex dependency graphs and slow installs. Too coarse and you lose the benefits of independent builds, tests, and deploys. Get the boundaries right and everything else follows.
- Build caching is not an optimization — it's a requirement. Without caching, a monorepo's CI time grows linearly with the number of packages. With remote caching, most CI runs complete in seconds because most packages haven't changed. If your monorepo doesn't have effective caching, you don't have a monorepo — you have a slow repo.
- Dependency boundaries must be enforced, not documented. If package A is not supposed to import from package B's internals, a lint rule or build constraint should prevent it. Documentation saying "don't do this" gets ignored the first time someone is in a hurry.
- A monorepo tool is a task orchestrator, not a build system. Turborepo, Nx, and Bazel don't build your code — they figure out what needs to be built and in what order, then delegate to your existing build tools. Choose the orchestrator that fits your team's complexity level.
- Developer experience degrades silently. A monorepo that works great at 10 packages can be painful at 50. Monitor install times, build times, IDE performance, and git operations. Set budgets for each and treat regressions as bugs.
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 · 66 lines · 52 tokens per session scan A f366a699486b
monorepo-architect is an agent published in the GitHub repository The-AI-Directory-Company/agents-and-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 52 tokens to every session and 1,951 once invoked, about $0.0003 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 agents, from other repositories
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
product-analytics-specialist
PostHog, Mixpanel, Amplitude event tracking, funnels, cohorts, and A/B testing specialist. Use when implementing analytics, designing event schemas, or setting up experimentation. Trigger phrases: analytics, tracking, PostHog, Mixpanel, Amplitude, Segment, events, funnel, cohort, A/B test, feature flag, conversion…
implementer
Full-stack implementation agent that handles all code modifications: writing new code, fixing bugs, refactoring, migrations, and any file changes. Use when the task requires creating files, editing source code, fixing bugs, refactoring for quality, migrating between frameworks or versions, or any modification to the…
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.