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.
git 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/ports)<a href="https://agentmods.dev/rules/louisbrulenaudet/monorepo-template/ports"><img src="https://agentmods.dev/badge/rules/louisbrulenaudet/monorepo-template/ports/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/rules/louisbrulenaudet/monorepo-template/ports"><img src="https://agentmods.dev/badge/rules/louisbrulenaudet/monorepo-template/ports.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.00539 | $0.00539 |
| Opus 5 | $0.00269 | $0.00269 |
| Sonnet 5 | $0.00108 | $0.00108 |
| Haiku 4.5 | $0.00054 | $0.00054 |
Grade A, and why
ports 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 9d 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.
What it actually says
Local Dev Ports
Follow the ranges and registry below when scaffolding or editing port config.
Role ranges
| Role | Prefix | Local HTTP ports |
|---|---|---|
| HTTP gateway | worker-api |
8700–8709 |
| Business worker (RPC) | worker-* |
8710–8739 |
| Queue-only consumer | queue-* |
8740–8759 |
| Webhook ingress | webhook-* |
8760–8779 |
| MCP server | mcp-* |
8780–8789 |
| Growth reserve | - | 8790–8799 |
| Frontend (Vite) | front-* |
5170–5199 (dev), 4170–4199 (preview) |
Assigned registry
| App | Role | Dev | Preview |
|---|---|---|---|
worker-api |
gateway | 8700 | - |
front-app |
frontend | 5174 | 4174 |
Local-dev rules
- Assign the next free port in the role’s range; record it in
package.json→monorepo.devPortandwrangler.jsoncdev.port(or Viteserver.port/preview.port). - RPC / queue workers still set a stable
dev.portfor standalonewrangler dev, but production has no public URL. Prefer multi-config:wrangler dev -c apps/worker-api/wrangler.jsonc -c apps/worker-foo/wrangler.jsonc(first config = HTTP primary). See also workers-config.mdc. - MCP servers are public HTTP locally and in prod; keep handlers thin and call
worker-*over RPC. Never expose credential rotation or other irreversible privileged actions on the MCP surface (see guardrails.mdc). - Inspectors: always
inspector_port: 0(ephemeral). - Frontends:
strictPort: trueon bothserverandpreview(see vite-config.mdc).
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.
- 9d ago First seen · 37 lines · 539 tokens per session scan A 356c80d5e403
ports is a cursor rule published in the GitHub repository louisbrulenaudet/monorepo-template (19 stars, last pushed 8d ago), licensed Apache-2.0. It adds 539 tokens to every session, about $0.0027 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 cursor rules, from other repositories
code-optimization
Guidelines for optimizing duplicate and poorly structured code.
paperfit
PaperFit project rule for LaTeX visual typesetting optimization.
swift-argument-parser
Documentation and usage patterns for Swift Argument Parser for command-line tools.
competition-details
Exclude competition details from agent work.
swift-observable
Migration guide for updating SwiftUI apps from ObservableObject to the @Observable macro.
update-docs
You will generate LLM-optimized documentation with concrete file references and flexible formatting.