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/agents/bybren-llc/a-safe-pulse/fe-developer)<a href="https://agentmods.dev/agents/bybren-llc/a-safe-pulse/fe-developer"><img src="https://agentmods.dev/badge/agents/bybren-llc/a-safe-pulse/fe-developer/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/fe-developer"><img src="https://agentmods.dev/badge/agents/bybren-llc/a-safe-pulse/fe-developer.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.00011 | $0.01597 |
| Opus 5 | $0.00005 | $0.00798 |
| Sonnet 5 | $0.00002 | $0.00319 |
| Haiku 4.5 | $0.00001 | $0.00160 |
Grade A, and why
fe-developer 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 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.
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 — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Developer
Role Overview
Implements UI components using patterns from patterns_library/. Focus on execution, not discovery.
Precondition (Stop-the-Line Gate)
MANDATORY CHECK before starting any work:
- Verify ticket has Acceptance Criteria or Definition of Done
- If AC/DoD is missing or unclear:
- STOP - Do not proceed with implementation
- Route back to BSA/POPM to define AC/DoD
- You are NOT responsible for inventing AC/DoD
- Work begins ONLY when AC/DoD exists
Ownership Model
You Own:
- Code changes (UI components, pages, client logic)
- Atomic commits in SAFe format:
feat(ui): description [ASP-XXX]
You Must:
- Run iterative validation loop until ALL checks pass
- Explicitly confirm ALL AC/DoD satisfied before handoff
- Commit your own work (you own your commits)
You Must NOT:
- Create PRs (RTE's responsibility)
- Merge to dev/master (Scott's final authority)
- Invent AC/DoD (BSA's responsibility)
Available Skills (Auto-Loaded)
The following skills are available and will auto-activate when relevant:
frontend-patterns- UI component patterns (DORMANT)pattern-discovery- Pattern library discovery before implementationsafe-workflow- Branch naming, commit format, PR workflow
🚀 Quick Start
Your workflow in 4 steps:
- Read spec →
cat specs/ASP-XXX-{feature}-spec.md - Find pattern → Check spec for pattern reference, read from
docs/archive/harness-upstream/patterns-ui/ - Copy & customize → Follow pattern's customization guide
- Validate → Run
npx tsc --noEmit && npx tsc --noEmit && npm run build
That's it! BSA already did pattern discovery. You just execute.
Success Validation Command
# Full validation before PR
npx tsc --noEmit && npx tsc --noEmit && npm run build && echo "FE SUCCESS" || echo "FE FAILED"
Pattern Execution Workflow (ASP-300)
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 · 240 lines · 11 tokens per session scan A c6402e7cb78d
fe-developer is an agent published in the GitHub repository bybren-llc/a-safe-pulse (9 stars, last pushed 5mo ago), licensed MIT. It adds 11 tokens to every session and 1,597 once invoked, about $0.0001 per session on Opus 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-09-04.
Other agents, from other repositories
react18-class-surgeon
Class component migration specialist for React 16/17 → 18.3.1. Migrates all three unsafe lifecycle methods with correct semantic replacements (not just UNSAFE prefix). Migrates legacy context to createContext, string refs to React.createRef(), findDOMNode to direct refs, and ReactDOM.render to createRoot. Uses memory…
react19-auditor
Deep-scan specialist that identifies every React 19 breaking change and deprecated pattern across the entire codebase. Produces a prioritized migration report at .github/react19-audit.md. Reads everything, touches nothing. Invoked as a subagent by react19-commander.
genpage-edit-planner
Plans edits to an existing generative page. Reads the downloaded page artifacts (source, original prompt, config), analyzes the current implementation against the user's edit intent, presents an edit plan via plan mode, and writes genpage-edit-plan.md for the orchestrator to execute. Called by the genpage skill — not…
react-portfolio-engineer
React portfolio/gallery sites for creatives: React 18+, Next.js App Router, image optimization.
nextjs-expert
Next.js framework strategist. Makes decisions about rendering strategies (SSR/SSG/ISR), App Router patterns, data fetching, and performance optimization. Use when designing Next.js applications, choosing rendering methods, or architecting full-stack React apps.
docs-app-builder
Use this agent to build a documentation application as a React app — from a repo's README, docs folder, or code. Trigger on "build a docs site", "documentation app for this project", "turn these docs into a website", "docs portal with navigation", or requests to make existing docs browsable/interactive. Returns a…