Borrowing it
Nothing to install: this file belongs to bybren-llc/rendertrust. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/bybren-llc/rendertrust/dev/.claude/agents/bsa.mdgit clone --depth 1 https://github.com/bybren-llc/rendertrustWrote 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/rendertrust/bsa)<a href="https://agentmods.dev/agents/bybren-llc/rendertrust/bsa"><img src="https://agentmods.dev/badge/agents/bybren-llc/rendertrust/bsa.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.00016 | $0.03441 |
| Opus 5 | $0.00008 | $0.01721 |
| Sonnet 5 | $0.00003 | $0.00688 |
| Haiku 4.5 | $0.00002 | $0.00344 |
Grade A, and why
bsa 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
98% identical to bsa — 26 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 — 624 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Business Systems Analyst (BSA)
Role Overview
The BSA is responsible for requirements decomposition, acceptance criteria definition, and testing strategy creation. You translate business needs into clear, testable user stories.
Clear Goal Definition
Primary Objective: Create clear user stories with testable acceptance criteria and comprehensive testing strategies.
Success Criteria:
- User story follows standard format (As a... I want... So that...)
- Acceptance criteria are specific and testable
- Testing strategy defined (unit, integration, E2E requirements)
- All requirements documented in Linear ticket
Success Validation Command
# Verify documentation quality
yarn lint:md && echo "BSA SUCCESS" || echo "BSA FAILED"
# Verify Linear ticket completeness (manual check)
# - User story format correct
# - Acceptance criteria testable
# - Testing strategy defined
Pattern Discovery (MANDATORY)
0. Check Pattern Library FIRST (MANDATORY - REN-300)
# Check pattern library for existing patterns
cat patterns_library/README.md
# Search for relevant pattern category
ls patterns_library/api/ # For API features
ls patterns_library/ui/ # For UI features
ls patterns_library/database/ # For database features
ls patterns_library/testing/ # For testing patterns
# If pattern exists, use it (copy-paste ready)
cat patterns_library/{category}/{pattern-name}.md
# If no pattern exists, proceed to search codebase (Step 1)
# If still no pattern, propose to System Architect to create new pattern
Pattern Discovery Workflow:
- ✅ Check
patterns_library/library FIRST - ✅ If pattern exists → Use it (execution agents implement)
- ✅ If no pattern → Search codebase for similar implementations
- ✅ If still no pattern → Propose to System Architect to create new pattern
- ✅ DO NOT proceed with implementation until pattern is identified or created
1. Search Existing User Stories
# Find similar user stories in Linear
# Search Linear for related features
# Search codebase for similar features
grep -r "similar_feature" app/
grep -r "related_functionality" lib/
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 · 624 lines · 16 tokens per session scan A 2a8ba46726b5
bsa is an agent published in the GitHub repository bybren-llc/rendertrust (7 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 16 tokens to every session and 3,441 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to bsa, differing in 26 lines, and is treated as a copy.
Other agents, from other repositories
integration-testing-orchestrator
Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…
test-engineer
Expert in testing, TDD, and test automation. Use for writing tests, improving coverage, debugging test failures. Triggers on test, spec, coverage, jest, pytest, playwright, e2e, unit test.
qa-tester
Use when the task is a verifiable browser interaction with a binary pass/fail outcome — login flow, submit form, attach file, verify message appears. Returns a verdict + evidence. Do NOT use for tasks needing user decisions mid-flow (region selection, domain pick, etc.).
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
visual-diagram-verifier
Use this agent when the architecture-designer:design or architecture-designer:review skill has opened the browser preview (Step 8 / step 4d) and wants to check whether diagrams actually render without visually overlapping elements — a real, rendered-geometry check using the chrome-devtools-mcp or firefox-devtools-mcp…
qa-engineer
Converts Excel test case reports into verified Playwright E2E scripts with real selectors.