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 saajunaid/caddis-plugin --skill monorepogit clone --depth 1 https://github.com/saajunaid/caddis-pluginWrote 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/saajunaid/caddis-plugin/monorepo)<a href="https://agentmods.dev/skills/saajunaid/caddis-plugin/monorepo"><img src="https://agentmods.dev/badge/skills/saajunaid/caddis-plugin/monorepo/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/saajunaid/caddis-plugin/monorepo"><img src="https://agentmods.dev/badge/skills/saajunaid/caddis-plugin/monorepo.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.00047 | $0.02133 |
| Opus 5.5 | $0.00019 | $0.00853 |
| Sonnet 5.5 | $0.00009 | $0.00427 |
| Haiku 4.5 | $0.00005 | $0.00213 |
Grade C, and why
monorepo scanned grade C with 1 finding 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 1mo 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
"clean": "turbo clean && rm -rf node_modules" How it starts
The opening of the file, as written. The whole thing — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monorepo Skill
Turborepo + pnpm workspaces for managing multi-app, multi-package repositories efficiently.
1. Repository Structure
monorepo/
├── apps/
│ ├── web/ # Next.js app
│ ├── api/ # FastAPI or Express backend
│ └── docs/ # Docusaurus or similar
├── packages/
│ ├── ui/ # Shared React component library
│ ├── config/ # Shared ESLint, TypeScript, Tailwind configs
│ ├── types/ # Shared TypeScript types / Zod schemas
│ └── utils/ # Shared utility functions
├── turbo.json
├── pnpm-workspace.yaml
└── package.json # Root — scripts only, no app deps
2. pnpm Workspaces
# pnpm-workspace.yaml
packages:
- 'apps/*'
- 'packages/*'
// Root package.json
{
"name": "my-monorepo",
"private": true,
"scripts": {
"dev": "turbo dev",
"build": "turbo build",
"test": "turbo test",
"lint": "turbo lint",
"typecheck": "turbo typecheck",
"clean": "turbo clean && rm -rf node_modules"
},
"devDependencies": {
"turbo": "^2.0.0"
},
"engines": { "node": ">=20", "pnpm": ">=9" }
}
workspace: Protocol — Cross-Package Dependencies
// apps/web/package.json
{
"dependencies": {
"@myapp/ui": "workspace:*", // Always latest local version
"@myapp/types": "workspace:^", // Semver compatible local version
"@myapp/utils": "workspace:*"
}
}
Rules:
workspace:*— consume local package always (recommended for internal packages)workspace:^— enforces semver compatibility (use for packages that may be published)- Never use relative paths (
"../packages/ui") — use workspace protocol
3. Turborepo Configuration
// turbo.json
{
"$schema": "https://turbo.build/schema.json",
"ui": "tui",
"tasks": {
"build": {
"dependsOn": ["^build"], // Build dependencies first (topological)
"inputs": ["src/**", "package.json"],
"outputs": [".next/**", "dist/**", "!.next/cache/**"]
},
"dev": {
"persistent": true, // Keep running (dev servers)
"cache": false, // Never cache watch mode
"dependsOn": ["^build"]
},
"test": {
"dependsOn": ["^build"],
"inputs": ["src/**", "test/**", "vitest.config.ts"],
"outputs": ["coverage/**"]
},
"lint": {
"inputs": ["src/**", ".eslintrc*", "eslint.config.*"]
},
"typecheck": {
"dependsOn": ["^build"], // Types may be generated by build
"inputs": ["src/**", "tsconfig*.json"]
},
"clean": {
"cache": false
}
}
}
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.
- 1mo ago Changed · -35 tokens per session a2b3ee49ef43
- 1mo ago First seen · 268 lines · 82 tokens per session scan C 03168f2ed312
monorepo is a skill published in the GitHub repository saajunaid/caddis-plugin (0 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 2,133 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
github-workflow-automation
Advanced GitHub Actions workflow automation with AI swarm coordination, intelligent CI/CD pipelines, and comprehensive repository management.
commit
Atomic git commit with conventional message. Use when the user says "commit", "save my changes", "commit this", or wants to create a git commit. Stages specific files, writes a conventional commit message with body explaining non-obvious decisions. Never uses git add -A.
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
github
Use the gh CLI for issues, pull requests, Actions runs, and GitHub API queries.