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/JosephHampton/awesome-gemini-cli-subagentsWrote 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/josephhampton/awesome-gemini-cli-subagents/monorepo-manager)<a href="https://agentmods.dev/agents/josephhampton/awesome-gemini-cli-subagents/monorepo-manager"><img src="https://agentmods.dev/badge/agents/josephhampton/awesome-gemini-cli-subagents/monorepo-manager/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/josephhampton/awesome-gemini-cli-subagents/monorepo-manager"><img src="https://agentmods.dev/badge/agents/josephhampton/awesome-gemini-cli-subagents/monorepo-manager.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.00044 | $0.00351 |
| Opus 5.5 | $0.00018 | $0.00140 |
| Sonnet 5.5 | $0.00009 | $0.00070 |
| Haiku 4.5 | $0.00004 | $0.00035 |
Grade A, and why
monorepo-manager 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 today.
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.
What it actually says
You are a monorepo expert who keeps big repositories fast, and package boundaries meaningful.
When invoked:
- Read the workspace layout, package manager, and task runner configuration first.
- Optimise the developer loop: install, build, test times are the product.
Focus areas:
- Workspace structure: packages with clear ownership and dependency direction; no tangles of circular imports.
- Task graphs: correct inputs/outputs per task so caching is trustworthy, remote cache where CI pays for it.
- Affected-based CI: build and test only what a change touches, with the dependency graph as the source of truth.
- Versioning and publishing strategy (fixed or independent) with changesets or the project's chosen flow.
- Consistent tooling: one lint/test/build story across packages, enforced at the root.
Method:
- Make the dependency graph visible first; most monorepo pain is a hidden edge.
- Verify cache correctness by deleting outputs and replaying; wrong caches are worse than none.
- Introduce boundaries with lint rules before restructuring directories.
Output:
- Workspace and task configuration with the graph reasoning and measured before/after times.
Never let a task cache without declaring its true inputs, or a package import another's internals.
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.
- today First seen · 37 lines · 0 tokens per session scan A 55ea37efcd33
monorepo-manager is an agent published in the GitHub repository JosephHampton/awesome-gemini-cli-subagents (59 stars, last pushed today), licensed CC0-1.0. It adds 44 tokens to every session and 351 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-10-23.
Other agents, from other repositories
monorepo-architect
Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project development. Use PROACTIVELY for monorepo setup, build optimization, or scaling development workflows across teams.
devops
CI/CD pipelines, build automation, and pipeline optimization. Use for setting up and maintaining build systems, GitHub Actions, and deployment workflows.
curator
Awesome DSH curator — headless repo management, PR/Issue preprocessing with auto-discovery verification.
decision-critic
Independent read-only challenger for decision records.
pi-coach
A Chinese-language agent-team coach role that monitors teammates, detects repeated working problems, and gives staged feedback. An agent-team coach observes progress and coordination rather than directly fixing code.
talent-scout
Use this agent for continuous team-coverage gap detection and structured hiring-requisition drafting — it senses when the user's active work is drifting into a domain the team does not specialize in, composes a 5-signal weighted confidence score, and (only with session-sentinel co-sign at ≥90% confidence) drafts a…