bsa

A business-systems analysis role that turns business needs into clear user stories, acceptance criteria, and testing plans. Acceptance criteria are conditions that can be checked to decide whether a feature is complete.

In plain words
What is it for?
Finding patterns, writing user stories, defining acceptance criteria, planning unit, integration, and end-to-end tests, and documenting requirements in Linear.
Why use it?
It helps remove ambiguity before implementation and makes requirements testable.

Agent for Claude Code

Install

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.

agentmods
npx agentmods add agents/bybren-llc/safe-agentic-workflow/bsa
Clone the repo
git clone --depth 1 https://github.com/bybren-llc/safe-agentic-workflow

Made for: Claude Code.

Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,481 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00016 $0.03481
Opus 5 $0.00008 $0.01741
Sonnet 5 $0.00003 $0.00696
Haiku 4.5 $0.00002 $0.00348

Measured yesterday against content hash b583f502a976, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

.claude/agents/bsa.md · 624 lines

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 - {{TICKET_PREFIX}}-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:

  1. ✅ Check patterns_library/ library FIRST
  2. ✅ If pattern exists → Use it (execution agents implement)
  3. ✅ If no pattern → Search codebase for similar implementations
  4. ✅ If still no pattern → Propose to System Architect to create new pattern
  5. ✅ 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/

Read the full file on GitHub · 624 lines

Changes

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.

  1. yesterday First seen · 624 lines · 0 tokens per session scan A b583f502a976

Subscribe to this mod's changes

bsa is an agent published in the GitHub repository bybren-llc/safe-agentic-workflow (404 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 3,481 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-08-30.