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/cursorrules)<a href="https://agentmods.dev/rules/manuelfusstc/pulseframework/cursorrules"><img src="https://agentmods.dev/badge/rules/manuelfusstc/pulseframework/cursorrules/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/cursorrules"><img src="https://agentmods.dev/badge/rules/manuelfusstc/pulseframework/cursorrules.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.02365 | $0.02365 |
| Opus 5.5 | $0.00946 | $0.00946 |
| Sonnet 5.5 | $0.00473 | $0.00473 |
| Haiku 4.5 | $0.00236 | $0.00236 |
Grade A, and why
cursorrules 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.
How it starts
The opening of the file, as written. The whole thing — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
═══════════════════════════════════════════════════════════════════════════════
PULSE FRAMEWORK - AI Agent Rules (v1.1)
═══════════════════════════════════════════════════════════════════════════════
Author: Manuel Fuß ([email protected])
Repo: https://github.com/manuelfussTC/PulseFramework
These rules apply to YOU, the AI Agent. You MUST follow them.
═══════════════════════════════════════════════════════════════════════════════
┌─────────────────────────────────────────────────────────────────────────────┐
│ 🛑 CRITICAL RULE: 30-MINUTE AUTONOMY LIMIT │
└─────────────────────────────────────────────────────────────────────────────┘
You may work autonomously for a MAXIMUM of 30 minutes. Then you MUST:
1. STOP - No further action without human confirmation
2. SUMMARIZE - What have you done in the last 30 min?
3. ASK - "Should I continue? Here is my current status: [...]"
WHY: After 30 min you lose context, build in wrong directions,
and overwrite working things.
For EVERY longer task:
- Split into 30-min blocks
- At the end of each block: Checkpoint + Summary + Question
- NEVER "just one more quick thing" after 30 min
┌─────────────────────────────────────────────────────────────────────────────┐
│ 🔒 5 CRITICAL SAFEGUARDS - NON-NEGOTIABLE │
└─────────────────────────────────────────────────────────────────────────────┘
SAFEGUARD 1: DELETE LOCK
- NEVER delete a non-empty file without explicitly asking:
"CONFIRM DELETION: [filename] - This file contains [X lines]. Delete?"
- NEVER "Apply All" on a diff >50 lines without prior summary
SAFEGUARD 2: GIT PUSH LOCK
- NEVER git push without explicit instruction
- Before every push: "Ready to push. Changes: [summary]. Confirm push?"
SAFEGUARD 3: DEPLOYMENT LOCK
- NEVER deploy without prior local test
- Before deploy: "Local tests: [passed/failed]. Confirm deploy?"
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 · 248 lines · 2,365 tokens per session scan A a4fa59dabcc5
cursorrules is a cursor rule published in the GitHub repository manuelfussTC/PulseFramework (28 stars, last pushed 9mo ago), licensed MIT. It adds 2,365 tokens to every session, about $0.0095 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.