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/ashishpatill/tell-proof/tell-local-dev-servergit clone --depth 1 https://github.com/ashishpatill/tell-proofWrote 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/ashishpatill/tell-proof/tell-local-dev-server)<a href="https://agentmods.dev/rules/ashishpatill/tell-proof/tell-local-dev-server"><img src="https://agentmods.dev/badge/rules/ashishpatill/tell-proof/tell-local-dev-server.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 | $0.00182 | $0.00182 |
| Opus 5 | $0.00091 | $0.00091 |
| Sonnet 5 | $0.00036 | $0.00036 |
| Haiku 4.5 | $0.00018 | $0.00018 |
Grade A, and why
tell-local-dev-server 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 4d 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 Server Runs
- This rule applies only when starting a local dev server for this Tell project.
- Before running
pnpm dev,pnpm -F @tell/web dev,pnpm dev:fixture,pnpm -F @tell/generic-app dev, or an equivalent local server command, first stop any existing local instance of this project. - Check active terminals and listening processes for the expected project ports: web on
3000, fixture app on3001. - Only kill processes that are clearly this project's dev servers, such as
next devprocesses with cwd under this repo. Do not kill unrelated apps that happen to use the same port; report the conflict instead. - After the old project instance is stopped and the port is free, start the requested local dev command.
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.
- 4d ago First seen · 13 lines · 182 tokens per session scan A 0f28d9c27a3b
tell-local-dev-server is a cursor rule published in the GitHub repository ashishpatill/tell-proof (1 stars, last pushed 9d ago), licensed MIT. It adds 182 tokens to every session, about $0.0009 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 cursor rules, from other repositories
cursor
You are working on the checkout service. Preserve transaction integrity and auditability.
frontend-architecture
Vite + React SPA architecture - directory layout, providers, bundle splitting. Tailwind styling in tailwind.mdc.
dev_workflow
Guide for using Taskmaster to manage task-driven development workflows.
lean
Answer densely. Cut filler, keep all technical signal.
orchestrator-main
Rules for the main orchestrator agent in multi-agent workflows.
react_hooks
React Hooks best practices for frontend package.