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-augmentnpx skills add evolplus/talos --skill ba-mode-augmentgit clone --depth 1 https://github.com/evolplus/talosWhat 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.00072 | $0.01026 |
| Opus 5 | $0.00036 | $0.00513 |
| Sonnet 5 | $0.00014 | $0.00205 |
| Haiku 4.5 | $0.00007 | $0.00103 |
Grade A, and why
ba-mode-augment 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 2d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BA Mode D — augment-existing
When to use
You are the BA and Shape Detection selected Mode D (the steady-state mode): docs/SRS.md and its per-US/per-FR file trees are fully populated, and the dispatch carries an incremental change. Capture any operator-supplied new requirement VERBATIM first, then hand to the pipeline.
Phase 1.D — Mode augment-existing setup
This is the steady-state mode — most BA dispatches after the initial ingest are Mode D.
Step D0 — Capture user-input requirements VERBATIM (mandatory when dispatch carries new requirements)
When the Orchestrator's dispatch prompt contains operator-supplied new requirements (an SRS revision request, a new feature spec, a constraint change, a scope addition, a clarification), BA's FIRST action is to capture the input VERBATIM at docs/requirements/conversational-additions/<ISO-date>-<slug>.md BEFORE any synthesis into US / FR / external-integration content. This keeps docs/requirements/ the complete audit log of every requirement that ever entered the project, so the downstream srs-validator can do its coverage check against a complete source corpus.
File location: docs/requirements/conversational-additions/<ISO-date>-<slug>.md
<ISO-date>= today's UTC date inYYYY-MM-DDformat<slug>= short kebab-case noun describing the addition (e.g.,add-batch-rbac-permissions,clarify-promo-state-machine,change-max-batch-size)
File content shape:
# <Operator-supplied title or BA-derived if not provided>
- Captured-by: BA (Mode D, dispatch <task-id-or-N/A>)
- Captured-at: <ISO-8601>
- Operator: <name from CLAUDE.md user context, or "operator" if unknown>
- Dispatch-context: <one-line summary of what the Orchestrator told BA — e.g., "user added batch RBAC constraint to FR-022 batch UI flow">
- Verbatim input follows. NO BA editorial intervention.
---
<the operator's input, copied verbatim — paragraph breaks preserved, no rewording, no summarization, no commentary>
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.
- 2d ago First seen · 58 lines · 72 tokens per session scan A 46a59afaab80
ba-mode-augment is a skill published in the GitHub repository evolplus/talos (8 stars, last pushed 28d ago), licensed Apache-2.0. It adds 72 tokens to every session and 1,026 once invoked, about $0.0004 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…