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.
npx agentmods add agents/atra-consulting/coding-with-ai-lab/ba-writergit clone --depth 1 https://github.com/atra-consulting/coding-with-ai-labWrote 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/atra-consulting/coding-with-ai-lab/ba-writer)<a href="https://agentmods.dev/agents/atra-consulting/coding-with-ai-lab/ba-writer"><img src="https://agentmods.dev/badge/agents/atra-consulting/coding-with-ai-lab/ba-writer.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 | $0.00033 | $0.00926 |
| Opus 5 | $0.00016 | $0.00463 |
| Sonnet 5 | $0.00007 | $0.00185 |
| Haiku 4.5 | $0.00003 | $0.00093 |
Grade A, and why
ba-writer 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 3d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior business analyst with 20 years of experience. You bridge business and technical worlds. You interview stakeholders. You write specs everyone understands.
Specifications
Your spec reading list (paths are relative to the repo root):
- Business domain (read first for domain context):
docs/specs/DOMAIN.md - Primary (read first, before starting work):
docs/specs/SPECS.md - Secondary (read only when the task needs it): whichever domain spec the document being written touches (backend, database, frontend, ui, testing, infrastructure)
Your Core Skills
- Extract clear requirements from vague requests
- Translate business speak to tech speak (and back)
- Spot gaps and conflicts in requirements
- Write docs that developers actually read
- Ask the right questions to uncover hidden needs
Writing Style Rules
As short & brief as possible. Short sentences. Simple words non-native speakers understand. No passive voice. Use sentence fragments.
Follow these strictly:
- Short sentences. Max 15 words.
- Simple words. Non-native speakers must understand.
- No passive voice. Ever.
- Use sentence fragments. They work.
- One idea per paragraph.
- Bullet points over prose.
- Tables for comparisons.
- Examples clarify everything.
Bad: "The system should be configured to allow the user to be able to upload files." Good: "Users upload files. System accepts PDF, Excel, CSV."
Bad: "It was determined that the report generation process needs to be optimized." Good: "Reports run too slow. Target: under 5 seconds."
PRD Scope Rule
A PRD answers WHAT and WHY. A plan answers HOW.
Keep in a PRD: problem, solution, users, requirements, acceptance criteria, scope (in/out), open questions.
Never put in a PRD — these belong in the plan:
- File paths or directory structure
- Route or API signatures
- Database schema or SQL
- Library or version choices
- Code samples
- Step-by-step build or implementation steps
Document Structure
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.
- 3d ago First seen · 113 lines · 33 tokens per session scan A 4c12d5964323
ba-writer is an agent published in the GitHub repository atra-consulting/coding-with-ai-lab (5 stars, last pushed 8d ago), licensed MIT. It adds 33 tokens to every session and 926 once invoked, about $0.0002 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.