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/smartfrog/opencode-froggy/tddnpx skills add smartfrog/opencode-froggy --skill tddgit clone --depth 1 https://github.com/smartfrog/opencode-froggyWhat 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.00017 | $0.00366 |
| Opus 5 | $0.00009 | $0.00183 |
| Sonnet 5 | $0.00003 | $0.00073 |
| Haiku 4.5 | $0.00002 | $0.00037 |
Grade A, and why
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 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.
What it actually says
TDD Protocol
Core Principle
- TDD First: Test-Driven Development is the default approach.
- Goal: Prioritize behavioral correctness and regression safety over formal compliance.
Workflow
- Requirement Synthesis: Briefly summarize the requirements before coding.
- Test Specification: Write tests describing the expected behavior (unit, integration, or E2E).
- Implementation: Update the logic only to the extent required to satisfy those tests.
Mandatory Rules
- No Test, No Code: Every new feature or bugfix must include relevant test coverage.
- Black-Box Testing: Validate observable behavior, not internal implementation details.
- Merge Requirement: Tests are mandatory for completion unless an explicit exception is documented.
Preferred Practice
- Red-Green-Refactor: Start with a failing test whenever practical.
- Right-Sized Testing:
- Unit Tests: For pure logic and isolated functions.
- Integration Tests: For system interactions and API boundaries.
- E2E Tests: For critical user journeys and "happy paths."
Explicit Exceptions (Must be justified)
- Pure refactoring (where behavior remains identical).
- Exploratory spikes or R&D.
- UI/Styling iterations where unit tests offer diminishing returns.
- Complex integrations where mocking is counterproductive.
- Emergency hotfixes (requires a follow-up ticket for test debt).
Quality Bar
- Readability: Tests must serve as documentation for the feature.
- Reliability: Tests must be deterministic (no flakes) and decoupled from implementation internals.
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 · 45 lines · 17 tokens per session scan A 773800a6e3ee
tdd is a skill published in the GitHub repository smartfrog/opencode-froggy (105 stars, last pushed 3mo ago), licensed MIT. It adds 17 tokens to every session and 366 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
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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.