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 rules/louisbrulenaudet/monorepo-template/cdgit 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/rules/louisbrulenaudet/monorepo-template/cd)<a href="https://agentmods.dev/rules/louisbrulenaudet/monorepo-template/cd"><img src="https://agentmods.dev/badge/rules/louisbrulenaudet/monorepo-template/cd.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.00000 | $0.02411 |
| Opus 5 | $0.00000 | $0.01205 |
| Sonnet 5 | $0.00000 | $0.00482 |
| Haiku 4.5 | $0.00000 | $0.00241 |
Grade A, and why
cd 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 2d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Continuous Deployment
The pipeline is .github/workflows/cd.yml. Read it for the step list; a prose copy here would only drift. How a release reaches it: ops/release.md. CI invariants: ops/ci.md. Human-facing secret/variable tables: the README deploy section. Wrangler secrets vs vars: backend/workers-config.md.
Weakening a deploy gate or shipping with missing credentials is covered by guardrails.md and is never the answer here either.
Status
CD is paused until the production GitHub Environment secrets are configured. The pause is the repository variable CD_ENABLED, checked by release.yml's deploy job - set it to true in the same act as adding the secrets. It deliberately does not live in this workflow: a job skipped inside a workflow_call target reports success to the caller, so a paused CD used to leave a green Release run with the tag already cut and nothing shipped. Gating at the caller makes the skip visible, and keeps workflow_dispatch usable for a manual redeploy.
Trigger
workflow_callandworkflow_dispatchonly.release.ymlcalls this workflow after it has cut the tag and confirmed it did not already exist;workflow_dispatchtakes ataginput and is the redeploy/rollforward path.- There is no
push: tags:trigger, and adding one is a regression. The release tag is created withGITHUB_TOKEN, and events created by that token do not start workflow runs, so a tag trigger never fires (GitHubGITHUB_TOKENdocs; changesets/action#669, changesets/changesets#1545). Zero tags existed while that dead trigger was the only path. - Do not deploy from
pull_requestorpull_request_target(the latter especially - base context plus untrusted checkout is a pwn pattern). - Concurrency is
cd-production,cancel-in-progress: false,queue: max. Cancelling would drop an in-flight ship; and with the defaultqueue: singlea third trigger replaces the pending one, silently losing that release. - Checkout uses
ref: ${{ inputs.tag }}- the ship must match the tagged commit, not whatever the branch tip is at job start. The tag must be exactlyvX.Y.Z: a changesets pre-mode tag (v1.0.0-next.0) fails closed atResolve release versioninstead of shipping @100%, and that red run is by design.RELEASE_SHA(the tagged commit) is what upload messages and Release notes record -GITHUB_SHApoints at the dispatching ref onworkflow_dispatchredeploys.
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.
- 2d ago First seen · 60 lines · 0 tokens per session scan A be7eb6cbfb47
cd is a cursor rule published in the GitHub repository louisbrulenaudet/monorepo-template (19 stars, last pushed 5d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,411 tokens. 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-03.
Other cursor rules, from other repositories
mcp-releasing
Steps and procedures for releasing MCP (Model Context Protocol) servers as NPM packages.
cloudflare-workers-hono-auto
Cloudflare Workers with Hono framework development standards and best practices.
changelog-generator-manual
This rule generates a comprehensive changelog.md file by analyzing all git tags and commits, creating a chronological record of all project changes with proper semantic versioning structure. The changelog.md file is stored at the root of the project.
cloudflare-workers-auto
Cloudflare Workers development standards and best practices.
release-commit-analysis-auto
This rule analyzes commits to determine if they should trigger a version bump. It categorizes conventional and non-conventional commits into Features, Bug Fixes, Breaking Changes, Documentation, and Other. It uses intelligent keyword matching for non-conventional commits and analyzes file changes to help categorize…
release-git-tags-auto
This rule checks for existing tags before creating new ones. It also offers to push the tag to the remote repository. It runs when users request release creation, version bumping, or package publishing.