bsa

bsa is an agent for Claude Code from bybren-llc/a-safe-pulse. It costs 16 tokens per session (3,463 once invoked), scanned A, a copy of bsa, MIT.

A business-systems analysis role that turns business needs into user stories, acceptance criteria, and a testing plan. Acceptance criteria are the specific conditions a feature must meet.

In plain words
What is it for?
Use it to discover existing project patterns, write Linear tickets, define testable requirements, and plan unit, integration, and end-to-end tests.
Why use it?
It helps turn vague requirements into work that developers and testers can understand and verify.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; reads .claude/ paths.

Good fit Use it to discover existing project patterns, write Linear tickets, define testable requirements, and plan unit, integration, and end-to-end tests.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/bybren-llc/a-safe-pulse/bsa
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.

Clone the repo
git clone --depth 1 https://github.com/bybren-llc/a-safe-pulse

Made for: Claude Code.

Wrote 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.

agentmods badge for bsa

README.md
[![agentmods](https://agentmods.dev/badge/agents/bybren-llc/a-safe-pulse/bsa/github.svg)](https://agentmods.dev/agents/bybren-llc/a-safe-pulse/bsa)
Your own site
<a href="https://agentmods.dev/agents/bybren-llc/a-safe-pulse/bsa"><img src="https://agentmods.dev/badge/agents/bybren-llc/a-safe-pulse/bsa/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.

agentmods 80×15 button for bsa

Your own site · 80×15
<a href="https://agentmods.dev/agents/bybren-llc/a-safe-pulse/bsa"><img src="https://agentmods.dev/badge/agents/bybren-llc/a-safe-pulse/bsa.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
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,463 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 95% copy Near-identical to another mod 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.1 $0.00016 $0.03463
Opus 5 $0.00008 $0.01732
Sonnet 5 $0.00003 $0.00693
Haiku 4.5 $0.00002 $0.00346

Measured 4d ago against content hash 1892e95c04ad, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, 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 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.

Origin

This is a copy

95% identical to bsa — 42 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.

.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
npx tsc --noEmit: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 - ASP-300)

# Check pattern library for existing patterns
cat patterns_library/README.md

# Search for relevant pattern category
ls patterns_library/api/      # For API features
# UI patterns archived (see docs/archive/harness-upstream/patterns-ui/)
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. 4d ago First seen · 624 lines · 16 tokens per session scan A 1892e95c04ad

Subscribe to this mod's changes

bsa is an agent published in the GitHub repository bybren-llc/a-safe-pulse (9 stars, last pushed 5mo ago), licensed MIT. It adds 16 tokens to every session and 3,463 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to bsa, differing in 42 lines, and is treated as a copy.

Related

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…

eunomia-bpf/agentsight · 0 tokens

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.

ashrafmusa/agenticana · 49 tokens

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.

mnzralee/claude-multi-agent-architecture · 41 tokens

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.).

DevZonayed/Mochi · 60 tokens

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…

sembraniteam/claude-plugins · 112 tokens

qa-engineer

Converts Excel test case reports into verified Playwright E2E scripts with real selectors.

odarino/haren · 21 tokens