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/manuelfussTC/PulseFrameworkWrote 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/manuelfusstc/pulseframework/pulse)<a href="https://agentmods.dev/rules/manuelfusstc/pulseframework/pulse"><img src="https://agentmods.dev/badge/rules/manuelfusstc/pulseframework/pulse/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/manuelfusstc/pulseframework/pulse"><img src="https://agentmods.dev/badge/rules/manuelfusstc/pulseframework/pulse.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.00224 | $0.00224 |
| Opus 5.5 | $0.00090 | $0.00090 |
| Sonnet 5.5 | $0.00045 | $0.00045 |
| Haiku 4.5 | $0.00022 | $0.00022 |
Grade A, and why
pulse 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: Call MCP tools!
EVERY MESSAGE → pulse_status FIRST
CallMcpTool: pulse_status
Arguments: { "userMessage": "<user message>" }
AFTER CODE CHANGES → pulse_doctor
EVERY 10 MIN → pulse_checkpoint
| Trigger | Tool |
|---|---|
| Every message | pulse_status |
| After edits | pulse_doctor |
| 10+ min work | pulse_checkpoint |
| "wrong"/"stop" | pulse_correct |
| 2-3 failures | pulse_escalate |
| Task done | pulse_review |
NON-NEGOTIABLE
- ⏱️ MAX 30 min autonomous
- 🗑️ NO delete without confirmation
- 📤 NO push without confirmation
- 🔐 NO secrets in code
DID YOU CALL pulse_status? If not, do it NOW.
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 · 39 lines · 224 tokens per session scan A 8942032dabbc
pulse is a cursor rule published in the GitHub repository manuelfussTC/PulseFramework (28 stars, last pushed 9mo ago), licensed MIT. It adds 224 tokens to every session, about $0.0009 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-30.
Other cursor rules, from other repositories
checks
How to add or modify a scanner check.
cursor
You are working on the checkout service. Preserve transaction integrity and auditability.
alembic-migrations
To add a non-nullable column and set a specific value for all existing rows without a persistent server default.
desktop-release-gate
Desktop app fixes must pass a local packaged build smoke test before pushing release tags or CI desktop builds.
nauro-ship-task
Run the full planner -> executor -> reviewer -> tech-lead -> direct-user-confirm -> push chain through Cursor's native project workflow agents. Requires the four bundled .cursor/agents/nauro-.md definitions and fails closed without native dispatch.
roslyn-mcp-overview
RoslynMcpServer — architecture, layout, version, DI.