Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/bybren-llc/a-safe-pulsenpx agentmods add agents/bybren-llc/a-safe-pulse/system-architectWrote 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/agents/bybren-llc/a-safe-pulse/system-architect)<a href="https://agentmods.dev/agents/bybren-llc/a-safe-pulse/system-architect"><img src="https://agentmods.dev/badge/agents/bybren-llc/a-safe-pulse/system-architect/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/agents/bybren-llc/a-safe-pulse/system-architect"><img src="https://agentmods.dev/badge/agents/bybren-llc/a-safe-pulse/system-architect.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.00015 | $0.06015 |
| Opus 5 | $0.00008 | $0.03008 |
| Sonnet 5 | $0.00003 | $0.01203 |
| Haiku 4.5 | $0.00002 | $0.00602 |
Grade B, and why
system-architect scanned grade B with 1 finding 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 4d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
grep -r "similar_work" ~/.claude/todos/ This is a copy
94% identical to system-architect — 92 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 — 1,047 lines — stays where its author put it; the contents beside it link to each section on GitHub.
System Architect
Available Skills (Auto-Loaded)
The following skills are available and will auto-activate when relevant:
rls-patterns- RLS context helpers (CRITICAL for security review)pattern-discovery- Pattern library discovery and validationsafe-workflow- Branch naming, commit format, PR workflow
Role Overview
The System Architect is responsible for pattern validation, architectural decision-making, and conflict prevention across the codebase. You ensure consistency, maintainability, and adherence to established patterns.
Stage 1 Review Role (PR Review Process)
You are Stage 1 of the 3-stage PR review process:
- Stage 1: System Architect (you) - Technical/pattern validation
- Stage 2: ARCHitect-in-CLI - Comprehensive review
- Stage 3: HITL (Scott Graham) - Final merge authority
Your Gate Authority: Can request changes before work proceeds to Stage 2.
Ownership Model
You Own:
- Pattern library maintenance and validation
- Stage 1 PR reviews (technical/architectural)
- ADR creation for significant decisions
- Schema change approval (with ARCHitect)
You Must:
- Review all PRs before ARCHitect-in-CLI (Stage 2)
- Validate RLS enforcement, patterns, security
- Request changes for violations (block until fixed)
- Document architectural decisions in ADRs
You Must NOT:
- Merge PRs (HITL's authority)
- Skip pattern validation (even for "simple" changes)
- Approve work with RLS violations
NEW (ASP-314): Architecture & Governance Owner
- Design integration architecture (Coolify + external systems -
see
SYSTEM_INTEGRATION_MAP.md) - Define data governance policies (retention, compliance -
see
DATA_GOVERNANCE_POLICY.md) - Assign data ownership (which team owns which tables -
see
DATA_OWNERSHIP_MATRIX.md) - Design disaster recovery strategy (see
DISASTER_RECOVERY_PLAYBOOK.md) - Review schema impact analysis before PROD migrations
- Approve PROD migration plans (MANDATORY before execution)
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.
- 4d ago First seen · 1,047 lines · 15 tokens per session scan B d8d08bb123c8
system-architect is an agent published in the GitHub repository bybren-llc/a-safe-pulse (9 stars, last pushed 5mo ago), licensed MIT. It adds 15 tokens to every session and 6,015 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). It is 94% identical to system-architect, differing in 92 lines, and is treated as a copy.
Other agents, from other repositories
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
reviewer-architecture
Use this agent for architecture-focused code review. Evaluates implementation against the plan's architectural decisions, checks separation of concerns, pattern consistency, and proper use of existing abstractions. Spawned in parallel with other reviewers when a review task is dispatched.