Borrowing it
Nothing to install: this file belongs to mtnyilmaz/agents. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mtnyilmaz/agents/main/.agents/skills/monorepo-architecture/SKILL.mdgit clone --depth 1 https://github.com/mtnyilmaz/agentsWrote 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/mtnyilmaz/agents/monorepo-architecture)<a href="https://agentmods.dev/skills/mtnyilmaz/agents/monorepo-architecture"><img src="https://agentmods.dev/badge/skills/mtnyilmaz/agents/monorepo-architecture/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/mtnyilmaz/agents/monorepo-architecture"><img src="https://agentmods.dev/badge/skills/mtnyilmaz/agents/monorepo-architecture.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.00055 | $0.00672 |
| Opus 5 | $0.00028 | $0.00336 |
| Sonnet 5 | $0.00011 | $0.00134 |
| Haiku 4.5 | $0.00006 | $0.00067 |
Grade A, and why
monorepo-architecture 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 10d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monorepo Architecture Skill
This project is a TypeScript-first monorepo boilerplate for building products with web, admin, mobile, and API apps sharing core packages.
Quick Reference
When working on this project, read the relevant doc from .agents/rules/:
| Task | Read |
|---|---|
| Adding a new technology or checking versions | .agents/rules/project-architecture.md |
| Creating new files or folders | .agents/rules/project-architecture.md |
| Naming anything (files, variables, routes, DB) | .agents/rules/naming-conventions.md |
| Working on frontend (web/admin) | .agents/rules/frontend-patterns.md |
| Working on API | .agents/rules/api-patterns.md |
| Working on authentication or RBAC | .agents/rules/auth-patterns.md |
| Working on database schema or queries | .agents/rules/database-patterns.md |
| Adding a third-party integration | .agents/rules/integration-patterns.md |
| Setting up environment variables | .agents/rules/config-patterns.md |
| Writing tests | .agents/rules/testing-patterns.md |
| DevOps, CI/CD, or deployment | .agents/rules/ci-cd.md |
| Understanding shared utilities | .agents/rules/project-architecture.md |
| Setting up the project from scratch | README.md |
Core Patterns
API: Route → Service → Database
tRPC routers call services. Services contain business logic. Services call database. Routes never touch the database directly.
Validation: Single Source of Truth
Zod schemas in @repo/utils/validation are used by both frontend forms (React Hook Form) and API input validation (tRPC). Write the schema once.
Integrations: Adapter Pattern
Every third-party service has an interface, provider implementations, mock for tests, and a factory. App code calls the factory, never a provider.
Auth: Single User Base
One user table, one session system. Web/Admin use cookies, Mobile uses JWT. Access control via RBAC roles (owner > super_admin > admin > user).
Response Format
All API responses: { success: true/false, data?: {}, error?: { code, message, details? }, meta?: { page, limit, total } }
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 56 lines · 55 tokens per session scan A 79f4151144aa
monorepo-architecture is a skill published in the GitHub repository mtnyilmaz/agents (6 stars, last pushed 3mo ago), licensed MIT. It adds 55 tokens to every session and 672 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…