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 heristop/leclap --skill monorepo-dev-workflowgit clone --depth 1 https://github.com/heristop/leclapWrote 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/heristop/leclap/monorepo-dev-workflow)<a href="https://agentmods.dev/skills/heristop/leclap/monorepo-dev-workflow"><img src="https://agentmods.dev/badge/skills/heristop/leclap/monorepo-dev-workflow.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.00050 | $0.00711 |
| Opus 5 | $0.00025 | $0.00356 |
| Sonnet 5 | $0.00010 | $0.00142 |
| Haiku 4.5 | $0.00005 | $0.00071 |
Grade A, and why
monorepo-dev-workflow 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 7d 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monorepo Dev Workflow
Overview
pnpm workspaces (apps/*, packages/*), no turbo/nx. Tooling is vite-plus (vp) — it provides lint (oxlint), format, test (vitest), and staged checks. There is no eslint, no prettier, and no jest at the root (jest lives only inside apps/leclap-expo).
- pnpm 11.5.2, Node ≥ 22.14.0 (
engine-strict— wrong versions are rejected). Install:pnpm install.
Command map
| Task | Command |
|---|---|
| Lint | pnpm lint |
| Format / check | pnpm fmt · pnpm fmt:check |
| All checks | pnpm check |
| Test | pnpm test · UI pnpm test:ui · coverage pnpm test:coverage · CI pnpm test:ci |
| Build | pnpm build (tsdown) |
| Typecheck a package | pnpm --filter <pkg> exec tsc --noEmit |
| Perf bench / profile | pnpm --filter ffmpeg-video-composer bench · FVC_PERF=1 pnpm compile <t.json> (docs/performance.md) |
| Run Expo app | pnpm app:expo · app:ios · app:android |
| Run web app | pnpm app:web |
| Build executables | pnpm build:exe:all |
| Dep graph / check | pnpm graph · pnpm deps:check |
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.
- 7d ago First seen · 45 lines · 50 tokens per session scan A aa33883344dd
monorepo-dev-workflow is a skill published in the GitHub repository heristop/leclap (24 stars, last pushed 11d ago), licensed MIT. It adds 50 tokens to every session and 711 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-30.
Other skills, from other repositories
qiaomu-cut
A workflow for turning a brief video idea into a planned, sourced, edited, rendered, and checked video project.
spec-harness-generate-agents
Bind the 6 SDD agents to THIS project's rules — fill each agent's GEN:rules region with its concern's real rules (implementer←Coding, tester←Testing+commands, reviewer←Reviewing, researcher/planner←Architecture, verifier←goal). Use when Malik says 'generate the agents', 'make the agents project-specific', 'bind agents…
spec-harness-build
Run the SDD pipeline over tasks.md: implement → test → VERIFY → review, one task at a time, under the ratchet. Use when Malik says 'build it', 'run the pipeline', 'implement the tasks', or 'ship this feature'. Each task gated by the separate verifier; lessons harvested by learn.
spec-harness-rules
Per-directory rules — resolve the nearest RULES.md for a path (coding/architecture/packages/testing/reviewing), or generate it from a directory's real code when missing. Use when Malik says 'different directories have different rules', 'add rules per directory', 'each package needs its own rules', 'what rules apply…
spec-harness-verify
Run the verifier alone — a separate clean-context agent that returns PASS/FAIL against goal.md (not the agent that wrote the code). Use when Malik says 'verify it', 'is it actually done', 'check against the goal', or 'did this pass'. Tests passing ≠ goal met.
react-native-testing
Deep React Native Testing Library (RNTL) reference — v13 (React 18 sync) and v14 (React 19 async), queries, userEvent, matchers, anti-patterns.