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/bybren-llc/a-safe-pulse/02-pattern-discoverygit 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/02-pattern-discovery)<a href="https://agentmods.dev/rules/bybren-llc/a-safe-pulse/02-pattern-discovery"><img src="https://agentmods.dev/badge/rules/bybren-llc/a-safe-pulse/02-pattern-discovery.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.00687 | $0.00687 |
| Opus 5 | $0.00344 | $0.00344 |
| Sonnet 5 | $0.00137 | $0.00137 |
| Haiku 4.5 | $0.00069 | $0.00069 |
Grade A, and why
02-pattern-discovery 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 yesterday.
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
94% identical to 02-pattern-discovery — 8 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pattern Discovery Protocol (MANDATORY)
Before writing ANY code, you MUST complete pattern discovery. This is not optional.
Step 0: Search Specs Directory (FIRST)
# Find similar implementations in specs
ls specs/*-spec.md
# Review SAFe user stories for related work
grep -r "As a.*I want to" specs/
# Check patterns referenced by past specs
cat specs/ASP-XXX-similar-spec.md
Step 1: Search Pattern Library
Check patterns_library/ for an existing pattern that fits your use case.
Available categories:
| Category | Path | Contents |
|---|---|---|
| API | patterns_library/api/ |
User context, admin, webhooks, Zod |
| UI | docs/archive/harness-upstream/patterns-ui/ (archived) |
Authenticated pages, forms, tables |
| Database | patterns_library/database/ |
RLS migration, SQL transactions |
| Testing | patterns_library/testing/ |
API integration tests |
| Security | patterns_library/security/ |
Input sanitization, rate limiting |
| CI | patterns_library/ci/ |
GitHub Actions, deployment pipeline |
| Config | patterns_library/config/ |
Environment config, logging |
See patterns_library/README.md for the full index of 18+ patterns.
Step 2: Search Codebase
# Search for similar functionality
grep -r "feature_name" app/ lib/ components/
# Find existing helpers
ls lib/
grep -r "helper_pattern" lib/
# Check for existing components
grep -r "ComponentName" components/
Step 3: Consult Documentation
Required reading before implementation:
CONTRIBUTING.md-- Workflow and git processdocs/database/DATA_DICTIONARY.md-- Database schema (SINGLE SOURCE OF TRUTH)docs/database/RLS_IMPLEMENTATION_GUIDE.md-- Row Level Security (MANDATORY for DB ops)docs/security/SECURITY_FIRST_ARCHITECTURE.md-- Security patterns
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.
- yesterday First seen · 85 lines · 687 tokens per session scan A d2a4837ffb95
02-pattern-discovery is a cursor rule published in the GitHub repository bybren-llc/a-safe-pulse (9 stars, last pushed 5mo ago), licensed MIT. It adds 687 tokens to every session, about $0.0034 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to 02-pattern-discovery, differing in 8 lines, and is treated as a copy.
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.
cli-error-handling
CLI command error handling patterns.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.