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/00-core-principles)<a href="https://agentmods.dev/rules/bybren-llc/a-safe-pulse/00-core-principles"><img src="https://agentmods.dev/badge/rules/bybren-llc/a-safe-pulse/00-core-principles.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.00771 | $0.00771 |
| Opus 5 | $0.00385 | $0.00385 |
| Sonnet 5 | $0.00154 | $0.00154 |
| Haiku 4.5 | $0.00077 | $0.00077 |
Grade A, and why
00-core-principles 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 3d 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
97% identical to 00-core-principles — 4 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.
SAFe Core Principles
This repository uses SAFe (Scaled Agile Framework) Agentic Workflow with 11 specialized AI agent roles. You are part of a collaborative team where every contributor has equal voice.
Round Table Philosophy
- Equal voice, mutual respect, shared responsibility
- Every agent and human contributor's input carries equal weight
- "Stop-the-line" authority: ANY contributor can halt work for architectural or security concerns
- Decisions are evidence-based, not authority-based
Search First, Reuse Always
MANDATORY before implementing anything:
- Search
patterns_library/for existing code patterns - Search
specs/for similar specifications - Search the codebase for similar implementations
- Consult documentation (see CONTRIBUTING.md, docs/)
- Only create new patterns if nothing exists (and that is BSA/Architect's job)
See patterns_library/README.md for the full pattern index (18+ patterns across 7 categories).
SAFe Hierarchy
All work follows: Epic > Feature > Story > Enabler
- BSA creates spec in
specs/ASP-XXX-feature-spec.md - System Architect validates the architectural approach
- Implementation agents execute using discovered patterns
- QAS validates against acceptance criteria
- Evidence is attached to the project management ticket before POPM review
Metacognitive Tags
Use these in specs to flag critical decisions:
#PATH_DECISION-- Architectural path chosen (document alternatives)#PLAN_UNCERTAINTY-- Areas requiring validation#EXPORT_CRITICAL-- Security or compliance requirements
Key Resources
CLAUDE.md-- Full AI assistant context and development commandsAGENTS.md-- All 11 agent roles, invocation patterns, exit statesCONTRIBUTING.md-- Git workflow, commit standards, PR processpatterns_library/-- Reusable code patterns (copy-paste ready)docs/onboarding/-- Setup guides and daily workflowsdocs/guides/ROUND-TABLE-PHILOSOPHY.md-- Collaboration principles
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.
- 3d ago First seen · 85 lines · 771 tokens per session scan A 8eb4504d9c8a
00-core-principles is a cursor rule published in the GitHub repository bybren-llc/a-safe-pulse (9 stars, last pushed 5mo ago), licensed MIT. It adds 771 tokens to every session, about $0.0039 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to 00-core-principles, differing in 4 lines, and is treated as a copy.
Other cursor rules, from other repositories
slice-tasks
PLANNING SPINE STEP 2 of 3 — Slice the work: break a scoped PRD into vertical-slice stories in specs/epics/. Use after scope-work (step 1), before plan-work (step 3). Not a substitute for scope-work or plan-work.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
elite-orchestrator
Elite orchestrator for mission-critical, enterprise-scale tasks requiring strategic coordination of 7+ agents across all domains. Makes architectural decisions, manages risk, ensures business continuity, and delivers enterprise-grade outcomes. Use for platform migrations, security incidents, multi-system integrations…
feedback-enhanced
Rules for an interactive feedback system that lets users and an AI agent discuss complex development work in real time. It includes guidance for recording decisions, tracking progress and handling detailed inputs such as code and diagrams.
project-onboarding-rule
Automatically onboards existing projects into the AI-driven development workflow.
linear-in-review
After finishing a Linear issue, set its status to In Review (never Done).