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/ashishcloud/agentpulse-pulseWrote 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/ashishcloud/agentpulse-pulse/cursor)<a href="https://agentmods.dev/rules/ashishcloud/agentpulse-pulse/cursor"><img src="https://agentmods.dev/badge/rules/ashishcloud/agentpulse-pulse/cursor/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/ashishcloud/agentpulse-pulse/cursor"><img src="https://agentmods.dev/badge/rules/ashishcloud/agentpulse-pulse/cursor.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.00020 | $0.00327 |
| Opus 5.5 | $0.00008 | $0.00131 |
| Sonnet 5.5 | $0.00004 | $0.00065 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
cursor 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 1mo 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
Pulse engagement (Cursor)
Register the MCP server in .cursor/mcp.json:
{ "mcpServers": { "pulse": { "command": "npx", "args": ["pulse-mcp"] } } }
When the user asks to run an engagement, drive the pulse MCP tools — Pulse owns the method + contract +
validation; you own the model, the UI, and the human gate:
pulse_startwith the requirements.pulse_next→ run each task prompt on your model; fill its JSON schema exactly.pulse_submitthe results. Fix anyschemaErrorsand resubmit. SurfaceproductBlockersto the user for a decision; do NOT surfaceautoResolved(architecture points the contract already dictates).pulse_gate({approved:true, decisions})only after the user approves. Silence = not approved.- Repeat Stories → Architecture → Build. In Build, implement one board item at a time;
pulse_claimit first. pulse_verify— "done" is the gate command going green, never your judgment.- If
.pulse/sync.jsonis enabled,pulse_syncthen reflect the board into the connected PM MCP.
The project board is .pulse/board.json (truth) / .pulse/BOARD.md (view). Never hand-edit BOARD.md.
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.
- 1mo ago First seen · 27 lines · 20 tokens per session scan A 26107e322b7e
cursor is a cursor rule published in the GitHub repository ashishcloud/agentpulse-pulse (0 stars, last pushed 2mo ago), licensed MIT. It adds 20 tokens to every session and 327 once invoked, about $0.0001 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-08-31.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.