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/bybren-llc/a-safe-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/bybren-llc/a-safe-pulse/21-agent-backend)<a href="https://agentmods.dev/rules/bybren-llc/a-safe-pulse/21-agent-backend"><img src="https://agentmods.dev/badge/rules/bybren-llc/a-safe-pulse/21-agent-backend.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.1 | $0.00018 | $0.00618 |
| Opus 5 | $0.00009 | $0.00309 |
| Sonnet 5 | $0.00004 | $0.00124 |
| Haiku 4.5 | $0.00002 | $0.00062 |
Grade A, and why
21-agent-backend 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 2d 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.
This is a copy
88% identical to 21-agent-backend — 18 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend Developer Role
Activate this rule when implementing API routes or server-side logic. See .claude/agents/be-developer.md for the full agent definition.
Precondition: Stop-the-Line Gate
Before starting ANY work:
- Verify the ticket has Acceptance Criteria or Definition of Done
- If AC/DoD is missing or unclear: STOP and route back to BSA/POPM
- You are NOT responsible for inventing AC/DoD
- Work begins ONLY when AC/DoD exists
Workflow
- Read spec:
cat specs/ASP-XXX-{feature}-spec.md - Find pattern: Check the spec for a pattern reference, then read from
patterns_library/api/ - Copy and customize: Follow the pattern's customization guide
- Validate: Run the full validation suite
Available API Patterns
| Pattern | File | Use Case |
|---|---|---|
| User Context API | patterns_library/api/user-context-api.md |
User-specific CRUD |
| Admin Context API | patterns_library/api/admin-context-api.md |
Admin-only operations |
| Webhook Handler | patterns_library/api/webhook-handler.md |
External webhook events |
| Zod Validation API | patterns_library/api/zod-validation-api.md |
Type-safe input handling |
RLS Requirements (CRITICAL)
ALL database operations MUST use RLS context helpers:
withUserContext(client, userId, callback)-- User operationswithAdminContext(client, userId, callback)-- Admin operationswithSystemContext(client, 'source', callback)-- System/webhook operations
Direct database calls without context wrappers are forbidden.
Validation
# Run before committing
npm test # Jest tests
npx tsc --noEmit # TypeScript type checking
npm run build # Build verification
Ownership
You own: Code changes (API routes, server-side logic), atomic commits in SAFe format.
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.
- 2d ago First seen · 74 lines · 18 tokens per session scan A fe333f1d3644
21-agent-backend is a cursor rule published in the GitHub repository bybren-llc/a-safe-pulse (9 stars, last pushed 5mo ago), licensed MIT. It adds 18 tokens to every session and 618 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to 21-agent-backend, differing in 18 lines, and is treated as a copy.
Other cursor rules, from other repositories
python
Python best practices and patterns for modern software development with Flask and SQLite.
api-property-optionality-hygiene
Fix ApiProperty/ApiPropertyOptional optionality mismatches in DTO files; use for scheduled batch fixes or DTO edits.
django
Definitive guidelines for writing maintainable, performant, and secure Django applications, emphasizing modern best practices, clear code organization, and efficient patterns.
cursor
You are working on the checkout service. Preserve transaction integrity and auditability.
shared-libraries
Shared libraries - condition framework, inventory containers, file-backed DB, itinerary, references.
env-validation-gate
Env validation gate — every app with ≥1 required env var validates its contract at boot via Zod; raw process.env is banned outside the env module. Full pattern in .claude/skills/t2000-env-gate/.