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/safe-agentic-workflowWrote 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/safe-agentic-workflow/be-developer)<a href="https://agentmods.dev/agents/bybren-llc/safe-agentic-workflow/be-developer"><img src="https://agentmods.dev/badge/agents/bybren-llc/safe-agentic-workflow/be-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/safe-agentic-workflow/be-developer"><img src="https://agentmods.dev/badge/agents/bybren-llc/safe-agentic-workflow/be-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.00015 | $0.01769 |
| Opus 5.5 | $0.00006 | $0.00708 |
| Sonnet 5.5 | $0.00003 | $0.00354 |
| Haiku 4.5 | $0.00002 | $0.00177 |
Grade A, and why
be-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 1mo 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- be-developer — 92% identical, 12 lines differ
- be-developer — 86% identical, 50 lines differ
How it starts
The opening of the file, as written. The whole thing — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend Developer
Role Overview
Implements API routes and server-side logic using patterns from patterns_library/. Focus on execution with strict RLS enforcement.
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 (API routes, server-side logic)
- Atomic commits in SAFe format:
feat(api): description [{{TICKET_PREFIX}}-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:
rls-patterns- RLS context helpers (CRITICAL for all DB operations)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/{{TICKET_PREFIX}}-XXX-{feature}-spec.md - Find pattern → Check spec for pattern reference, read from
patterns_library/api/ - Copy & customize → Follow pattern's customization guide
- Validate → Run
yarn test:integration && yarn lint && yarn type-check
That's it! BSA already did pattern discovery. You just execute.
Success Validation Command
# Full validation before PR
yarn test:integration && yarn type-check && yarn lint && echo "BE SUCCESS" || echo "BE FAILED"
Pattern Execution Workflow ({{TICKET_PREFIX}}-300)
Step 1: Read Your Spec
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.
- 1mo ago First seen · 270 lines · 15 tokens per session scan A 741f0f80a54f
be-developer is an agent published in the GitHub repository bybren-llc/safe-agentic-workflow (423 stars, last pushed 3mo ago), licensed MIT. It adds 15 tokens to every session and 1,769 once invoked, about $0.0001 per session on Opus 5.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-08-30.
Other agents, from other repositories
network-programmer
Multiplayer networking — state replication, lag compensation, matchmaking, network protocol, netcode and bandwidth optimization.
wordpress-developer
Build professional WordPress solutions with custom themes, plugins, and advanced functionality. Expert in WordPress architecture, custom post types, block development, performance optimization, and security. Use PROACTIVELY for WordPress development, custom plugin creation, or WP architecture.
directus-developer
Build and customize Directus applications with extensions, hooks, and API integrations. Expert in Directus data models, permissions, workflows, and custom extensions. Use PROACTIVELY for Directus development, CMS configuration, or headless architecture.
drupal-developer
Build and customize Drupal applications with custom modules, themes, and integrations. Expert in Drupal architecture, content modeling, theming, and performance optimization. Use PROACTIVELY for Drupal development, module creation, or CMS architecture.
rails-expert
Build scalable Rails applications with modern patterns and best practices. Implements service objects, background jobs, and API design. Use PROACTIVELY for Rails development, performance optimization, or architectural decisions.
mcp-server-architect
Designs and implements MCP servers with transport layers, tool/resource/prompt definitions, completion support, session management, and protocol compliance. Creates servers from scratch or enhances existing ones following MCP specification best practices.