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 skills/evolplus/talos/ba-mode-multi-docnpx skills add evolplus/talos --skill ba-mode-multi-docgit clone --depth 1 https://github.com/evolplus/talosWrote 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/skills/evolplus/talos/ba-mode-multi-doc)<a href="https://agentmods.dev/skills/evolplus/talos/ba-mode-multi-doc"><img src="https://agentmods.dev/badge/skills/evolplus/talos/ba-mode-multi-doc.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.00069 | $0.00701 |
| Opus 5 | $0.00034 | $0.00351 |
| Sonnet 5 | $0.00014 | $0.00140 |
| Haiku 4.5 | $0.00007 | $0.00070 |
Grade A, and why
ba-mode-multi-doc 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 — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BA Mode B — ingest-from-multi-doc
When to use
You are the BA and Shape Detection selected Mode B: docs/SRS.md plus some/all of docs/user-stories/*.md + docs/frs/*.md already exist, but the pairing has orphans. Validate each per-file artifact and identify the gaps the common pipeline will close.
Phase 1.B — Mode ingest-from-multi-doc setup
The incoming repo already has docs/SRS.md + some/all of docs/user-stories/*.md + docs/frs/*.md. Your job is to validate each per-file artifact and identify the gaps the common procedure will close.
B1. Per-file structural validation. For each docs/user-stories/<US-ID>.md, verify it has Description, Pre-conditions, Main Flow, Business Rules, Post-conditions, Linked artifacts sections per user-story-template.md. For each docs/frs/<FR-ID>.md, verify Description, Preconditions, Main Flow, Business Rules, Input Schema, Output Schema, Error Handling, Sequence Diagram per frs-template.md. Missing-section issues become OQs in Phase 1.X.
B2. Index-vs-file pairing. Phase 1.X Step 0a + 0b handle this. Note in advance which orphans you've detected so the common procedure produces OQs of the right granularity.
B3. Set Source: inline if not already set.
B4. Gap detection (no invention). Walk every per-file artifact (docs/user-stories/<US-ID>.md, docs/frs/<FR-ID>.md) against its template's required sub-sections. For every required sub-section that's missing or empty, leave a TODO: <sub-section expected> marker in the file AND raise a paired OQ in SRS §8 citing the file+sub-section. Same for the SRS body — apply Gap Handling per srs-ingestion-checklist.md § Gap Handling. Never auto-author missing content.
B5. Conflict detection (batched). Cross-reference per-file artifacts for contradictions (US-001's Business Rules vs FR-001's Error Handling; two USes claiming the same capability with different roles; etc.) AND against the SRS body. Accumulate all conflicts. Halt with one batched NEEDS_CONTEXT if any exist. Single round-trip.
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 · 35 lines · 69 tokens per session scan A f7ae64f81c66
ba-mode-multi-doc is a skill published in the GitHub repository evolplus/talos (8 stars, last pushed 29d ago), licensed Apache-2.0. It adds 69 tokens to every session and 701 once invoked, about $0.0003 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…