Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/roedyrustam/vibes-plugnpx agentmods add skills/roedyrustam/vibes-plug/monorepo-architectWrote 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/roedyrustam/vibes-plug/monorepo-architect)<a href="https://agentmods.dev/skills/roedyrustam/vibes-plug/monorepo-architect"><img src="https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/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/skills/roedyrustam/vibes-plug/monorepo-architect"><img src="https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/monorepo-architect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 100 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 101 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 183 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00057 | $0.02350 |
| Opus 5.5 | $0.00023 | $0.00940 |
| Sonnet 5.5 | $0.00011 | $0.00470 |
| Haiku 4.5 | $0.00006 | $0.00235 |
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 3d 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 — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monorepo Architect (Turborepo 2.x / Moon Edition)
English
Orchestration & Integration
- Upstream & Project Topology:
zero-to-prod-orchestrator(Phase 2 project foundation),brainstorming,session-memory-manager. - AST & Codebase Intelligence:
living-codebase-ast-graph(cross-package dependency topology & DAG sorting),typescript-expert(composite projects & isolated declarations). - CI/CD & Deployment:
ci-cd-devops-architect(monorepo cache pipelines),github-actions-expert(matrix testing & sparse checkout),cloud-hosting-expert(multi-app deployments). - Shared Design & Components:
design-system-architect(sharedpackages/uitokens),senior-frontend/js-backend-expert(shared packages consumption).
Description
Expert guide for designing and managing scalable monorepos. Covers Turborepo 2.x (the 2026 standard for JS/TS monorepos), moon (polyglot task runner for teams mixing JS + Rust + Go), pnpm workspaces, shared package design, incremental builds, remote caching, and CI/CD pipeline optimization.
Trigger Conditions
- Managing a codebase with multiple apps and shared packages.
- Setting up a monorepo for a SaaS with separate
web,admin,api, andpackages. - Optimizing build and test times with remote caching.
- Sharing TypeScript types, UI components, or utility functions across apps.
- Migrating from a multi-repo setup to a monorepo.
Tool Selection Guide (2026)
| Tool | Best For | Language Agnostic |
|---|---|---|
| Turborepo 2.x | JS/TS monorepos (Next.js, Vite, Node) | ❌ (JS focused) |
| moon | Polyglot teams (JS + Go + Rust + Python) | ✅ |
| Nx | Enterprise, Angular/React, plugin ecosystem | ❌ (JS focused) |
| Bazel | Very large orgs, hermetic builds | ✅ |
Turborepo 2.x — Standard JS Monorepo
Repository Structure
my-saas/
├── apps/
│ ├── web/ # Next.js 15 main app
│ ├── admin/ # Next.js 15 super admin (subdomain)
│ └── api/ # Hono/Fastify backend
├── packages/
│ ├── ui/ # Shared Tailwind v4 components
│ ├── db/ # Drizzle ORM schema + queries
│ ├── auth/ # Auth utilities (session, JWT)
│ ├── email/ # Email templates (React Email)
│ └── tsconfig/ # Shared TypeScript configs
├── turbo.json
├── pnpm-workspace.yaml
└── package.json
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.
- 3d ago Changed · +5 lines · +57 tokens per session 601c244059e6
- 4d ago Changed · +2 lines · -57 tokens per session 4d632a472e32
- 7d ago Changed 264d16d20551
- 16d ago Changed aef627b1a870
- 21d ago Changed e1fd9ea1d48f
- 22d ago Changed 2651756d7926
- 24d ago Changed · -6 lines · +44 tokens per session f39958120726
- 26d ago Changed · +6 lines · -44 tokens per session f20a76dc0373
- 1mo ago Changed 15fa1afadc16
- 1mo ago First seen · 234 lines · 57 tokens per session scan A 62da291ef479
monorepo-architect is a skill published in the GitHub repository roedyrustam/vibes-plug (113 stars, last pushed yesterday), licensed MIT. It adds 57 tokens to every session and 2,350 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-09-03.
Other skills, from other repositories
implement-spec
A coding workflow that implements a written specification through a set of linked tickets. It creates a branch and draft pull request, assigns independent work to separate agents, combines their changes, and prepares the result for review.
launch
Planning releases and reporting delivery work from GitHub PR history. Use when versioning, CHANGELOGs, rollout or rollback plans, engineering metrics, retrospectives, or stakeholder reports are needed.
setup
Configure this repo's issue tracker for the flow skills: GitHub, Jira, or local markdown (the default).
commit
Smart commit with Ollama-generated messages. Conventional commits, auto-push option. Triggers on: commit this, commit changes, smart commit, /commit.
jira-integration
Use this skill when retrieving Jira tickets, analyzing requirements, updating ticket status, adding comments, or transitioning issues. Provides Jira API patterns via MCP or direct REST calls.
github-pr-workflow
GitHub PR lifecycle: branch, commit, open, CI, merge.