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 agentmods add skills/hassanzohdy/agent-kit/monoreposnpx skills add hassanzohdy/agent-kit --skill monoreposgit clone --depth 1 https://github.com/hassanzohdy/agent-kitWrote 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/hassanzohdy/agent-kit/monorepos)<a href="https://agentmods.dev/skills/hassanzohdy/agent-kit/monorepos"><img src="https://agentmods.dev/badge/skills/hassanzohdy/agent-kit/monorepos.svg" alt="Measured on agentmods" 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.00118 | $0.01540 |
| Opus 5 | $0.00059 | $0.00770 |
| Sonnet 5 | $0.00024 | $0.00308 |
| Haiku 4.5 | $0.00012 | $0.00154 |
Grade A, and why
mongez-agent-kit-monorepos 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 5d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monorepos
Claude Code (and every other agent) discovers project skills only from the session-root skills directory — it does not recurse into subdirectories. So in a full-stack repo opened at the root, an inner project's backend/.claude/skills/ (or backend/skills/) is invisible. agent-kit closes that gap by aggregating each project's skills up into the root.
repo/ ← you open your agent here; one .claude/skills/
├── package.json ← agentKit.monorepo.projects: ["backend", "frontend"]
├── AGENTS.md
├── backend/
│ ├── package.json ← backend's own agentKit.pick/omit
│ ├── skills/code-standards/SKILL.md
│ └── node_modules/@warlock.js/core/skills/…
└── frontend/
├── package.json
├── skills/forms/SKILL.md
└── node_modules/@warlock.js/core/skills/…
npx agent-kit sync --projects backend,frontend
.claude/skills/
backend-code-standards/ # backend's authored skill — prefixed with the project dir
frontend-forms/ # frontend's authored skill
warlock-js-core-use-cache/ # shared dependency — ONE copy, by package slug
The mental model
Each declared project is scanned as if you ran
agent-kit syncinside it — itsnode_modules/dependency skills (filtered by that project's ownagentKitconfig) plus its authoredskills/folder — and the results are merged up into the root's skill directories.
Declaring projects
Two equivalent ways. Pin it in config so contributors don't retype it:
{
"scripts": { "postinstall": "agent-kit sync" },
"agentKit": { "monorepo": { "projects": ["backend", "frontend"] } }
}
…or pass it ad-hoc on the CLI (overrides the config):
npx agent-kit sync --projects backend,frontend
npx agent-kit sync --projects "apps/*" # one-level glob: every dir under apps/
Entries are paths relative to the repo root (or absolute). A one-level glob (apps/*, packages/*, or bare *) expands to each immediate subdirectory; hidden dirs and node_modules are skipped. Multi-level / mid-path globs are intentionally unsupported.
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.
- 5d ago First seen · 119 lines · 118 tokens per session scan A aeac8519094a
mongez-agent-kit-monorepos is a skill published in the GitHub repository hassanzohdy/agent-kit (2 stars, last pushed 19d ago), licensed MIT. It adds 118 tokens to every session and 1,540 once invoked, about $0.0006 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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…