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 skills add Sistema2D/FrameCode-VibeWork --skill brainstorming-and-tddgit clone --depth 1 https://github.com/Sistema2D/FrameCode-VibeWorkWrote 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/sistema2d/framecode-vibework/brainstorming-and-tdd)<a href="https://agentmods.dev/skills/sistema2d/framecode-vibework/brainstorming-and-tdd"><img src="https://agentmods.dev/badge/skills/sistema2d/framecode-vibework/brainstorming-and-tdd/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.
<a href="https://agentmods.dev/skills/sistema2d/framecode-vibework/brainstorming-and-tdd"><img src="https://agentmods.dev/badge/skills/sistema2d/framecode-vibework/brainstorming-and-tdd.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00018 | $0.00471 |
| Opus 5 | $0.00009 | $0.00235 |
| Sonnet 5 | $0.00004 | $0.00094 |
| Haiku 4.5 | $0.00002 | $0.00047 |
Grade A, and why
brainstorming-and-tdd 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 9d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Behavior design and test-first development
Purpose
Turn an implementation request into observable behavior and use the smallest useful test-first loop to reduce ambiguity and regression risk.
Use conditions
Use for behavior changes where an automated unit, integration, contract, or end-to-end check is practical. Ask a blocking question only when missing information would materially change scope or outcome; otherwise state a bounded assumption and proceed.
Non-responsibilities
- requiring TDD for pure documentation, exploratory spikes, or surfaces with no practical harness;
- expanding the feature beyond agreed acceptance criteria;
- replacing product decisions with test implementation details;
- creating brittle tests that assert incidental structure instead of behavior.
Inputs
User outcome, current behavior, edge cases, constraints, acceptance criteria, affected interfaces, existing tests, and active plan.
Procedure
- Express the request as actors, trigger, observable result, boundaries, and failure cases.
- Resolve material ambiguity and record assumptions.
- Select the narrowest test level that proves the behavior.
- For a defect, reproduce it with a failing regression check when feasible; for legacy code, use a characterization test before changing behavior.
- Run the new check and confirm it fails for the intended reason.
- Implement the smallest plan-scoped change that satisfies it.
- Rerun the focused check, then the relevant regression suite.
- Refactor only while all checks remain green and within scope.
Required output
Concise behavior specification, assumptions, test level, red/green evidence, implementation scope, regression results, and any justified manual validation.
Validation
The test fails before implementation for the expected reason, passes after the change, remains meaningful if the defect is reintroduced, and does not depend on irrelevant internals.
Exit criteria
Exit when acceptance criteria are demonstrated by appropriate evidence, or when the missing test capability and alternative validation are recorded explicitly.
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.
- 9d ago First seen · 59 lines · 18 tokens per session scan A 3f14c63843b6
brainstorming-and-tdd is a skill published in the GitHub repository Sistema2D/FrameCode-VibeWork (24 stars, last pushed 8d ago), licensed Apache-2.0. It adds 18 tokens to every session and 471 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.
Other skills, from other repositories
ensemble-implement-trd
Complete TRD implementation using git-town workflow with ensemble-orchestrator delegation and TDD methodology (Codex skill for /ensemble:implement-trd).
ensemble-full-implement-trd
This command implements a complete Technical Requirements Document (TRD) using modern git-town feature branch workflow. It creates a feature branch and delegates to ensemble-orchestrator which routes to tech-lead-orchestrator for structured TDD-based development including planning, implementation, testing, and quality…
implement
Test-driven implementation of a plan produced by /plan: loads the JSON tracker, then per chunk writes a failing test, implements until it passes, and runs a two-agent quality gate (review-impl conformance + red-team correctness). Use after /plan has produced an approved tracker. Requires a tracker whose planreview…
plan
Structured planning process: explores the code, decomposes a feature into independently-testable TDD chunks with a dependency graph, writes a JSON tracker, and gates the plan through an independent review-plan agent before any code is written. Use after /spec (or on its own) and before /implement, to decide HOW to…
tdd
Guided TDD workflow — plan, tracer bullet, incremental RED-GREEN.
testing-patterns
Jest testing patterns, factory functions, mocking strategies, and TDD workflow. Use when writing unit tests, creating test factories, or following TDD red-green-refactor cycle.