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 louisbrulenaudet/monorepo-template --skill cfgit clone --depth 1 https://github.com/louisbrulenaudet/monorepo-templateWrote 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/louisbrulenaudet/monorepo-template/cf)<a href="https://agentmods.dev/skills/louisbrulenaudet/monorepo-template/cf"><img src="https://agentmods.dev/badge/skills/louisbrulenaudet/monorepo-template/cf/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/louisbrulenaudet/monorepo-template/cf"><img src="https://agentmods.dev/badge/skills/louisbrulenaudet/monorepo-template/cf.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.00081 | $0.03436 |
| Opus 5.5 | $0.00032 | $0.01374 |
| Sonnet 5.5 | $0.00016 | $0.00687 |
| Haiku 4.5 | $0.00008 | $0.00344 |
Grade A, and why
cf 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 today.
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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cloudflare CLI (cf)
cf (exact catalog pin) replaces Wrangler for dev, build, types, and deploy. Each app is configured by a typed apps/<app>/cloudflare.config.ts and built through the Cloudflare Vite plugin 2.0 beta (apps/<app>/vite.config.ts). cf is a devDependency of the root and of each app: run it through the package scripts or pnpm --filter=<app> exec cf …, never a global install. The beta changes between releases, so the installed --help beats memory and these notes.
Find the command
pnpm exec cf cli search "<task>"- local search, top 5 matches as JSON. Describe the action and the resource type (list kv keys,apply d1 migrations), never names, IDs, domains, or tokens: the query travels with telemetry when telemetry is on. For a Cloudflare docs page,pnpm exec cf docs search "<question>"returns ranked URLs as JSON under the same anonymous-query rule.pnpm exec cf schema <command words>- the API request a generated command sends (pnpm exec cf schema d1 raw).pnpm exec cf <command words> --help- flags at the installed version.--forceis sometimes an API parameter rather than a confirmation skip: read the help before passing it.--dry-runwhere the help lists it - prints the request, or builds and checks without uploading.- Run it.
Project commands
Run from the repo root; each script runs in its app directory, next to cloudflare.config.ts.
| Task | Command | Notes |
|---|---|---|
| Dev server | pnpm --filter=<app> dev (cf dev) |
Runs Vite and forwards only --mode; ports stay in vite.config.ts (rule backend/ports). Background task and readiness: skill run-app |
| Build | pnpm turbo run build --filter=<app> (cf build) |
Production mode; writes .cloudflare/output/v0/ |
Env types |
pnpm types (cf workers types, worker-api) |
The turbo types task also runs before check-types; front-app has type generation off |
| Startup profile | pnpm --filter=worker-api exec cf workers check --prebuilt --mode production, after a build |
JSON bundle size and startup timings; writes worker-startup.cpuprofile (gitignored). Needs a Worker entrypoint, so not front-app |
| Deploy, upload | pnpm run deploy, pnpm run upload |
Humans and CD only |
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.
- today Changed · +1 lines 81a4f4d72a20
- 4d ago Changed · -1 lines ca48d7384668
- 10d ago Changed · +8 lines · +9 tokens per session 9c51887ca182
- 19d ago Changed 24a2eef47f66
- 20d ago First seen · 110 lines · 72 tokens per session scan A 03102c5b536f
cf is a skill published in the GitHub repository louisbrulenaudet/monorepo-template (19 stars, last pushed today), licensed Apache-2.0. It adds 81 tokens to every session and 3,436 once invoked, about $0.0003 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-30.
Other skills, from other repositories
prepare-cloudflare-production-deployment
Source-of-truth runbook for preparing this Vinext Cloudflare Workers SaaS template for production deployment. Use when setting up or auditing Cloudflare MCP resources, wrangler.jsonc bindings, Worker secrets, Turnstile, Email Sending, GitHub Actions secrets/variables, or GitHub CLI deployment wiring for this…
cloudflare-router
Use when manage Cloudflare DNS, CDN, and security rules via API. Use when configuring domains, SSL, WAF, or edge caching.
cloudflare-workers-mcp
Software Development MCP server by Cloudflare.
deploy-plan
Deploy and keep an app up through deployplan. Use when the human says deploy, host, go live, it's down, add a domain, or keep this running. One account. Open source. Do not send them to Vercel or Supabase. Do not ask them to pay.
cloudflare-hono
Hono lightweight web framework on Cloudflare Workers.
cloudflare-workers
Cloudflare Workers edge computing platform.