ODS is a system for turning a PC, Mac, or Linux computer into a private local AI server, meaning a machine that runs models and related AI services itself. It supports local model inference, chat, voice, agents, workflows, document retrieval, search, and image generation. The catalogue includes commands and an instruction for operating or configuring this system.
Borrowing it
Nothing to install: this file belongs to Osmantic/ODS. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Osmantic/ODS/main/.claude/commands/tdd.mdgit clone --depth 1 https://github.com/Osmantic/ODSWrote 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/commands/osmantic/ods/tdd)<a href="https://agentmods.dev/commands/osmantic/ods/tdd"><img src="https://agentmods.dev/badge/commands/osmantic/ods/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/commands/osmantic/ods/tdd"><img src="https://agentmods.dev/badge/commands/osmantic/ods/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.00017 | $0.03625 |
| Opus 5.5 | $0.00007 | $0.01450 |
| Sonnet 5.5 | $0.00003 | $0.00725 |
| Haiku 4.5 | $0.00002 | $0.00363 |
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 2mo 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 — 509 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TDD TDD TDD - Strict Test-Driven Development
Enforce the classic Red -> Green -> Refactor cycle. Tests are written FIRST, implementation comes SECOND.
"TDD TDD TDD" - the repetition is intentional. This skill enforces discipline.
ODS has two test ecosystems: Shell (BATS + bash assert) and Python (pytest). This skill handles both.
Arguments
$ARGUMENTS- Feature description and options:- First part: Feature description in quotes or as text
--shell- Write shell/BATS test (default for installers/, scripts/, ods-cli)--python- Write Python/pytest test (default for dashboard-api/)--file <path>- Explicit test file path
The Three Laws of TDD
- You may not write production code until you have written a failing test
- You may not write more test than is sufficient to fail
- You may not write more production code than is sufficient to pass the test
Philosophy: Ask Early, Ask Often
This skill should liberally use AskUserQuestion at decision points. TDD involves judgment about what to test, test granularity, and when the implementation is "done." The user should direct these choices.
- Before writing the test — confirm what behavior to test and test type
- After RED phase — validate that the failure is the right kind before implementing
- After GREEN phase — ask if the implementation approach is acceptable
- After each cycle — ask whether to iterate or stop
Workflow
Phase 0: Understand the Feature
Before writing anything:
- Parse
$ARGUMENTSto extract feature description and flags - Analyze the feature - what behavior needs to be tested?
- Determine test ecosystem (Shell or Python) based on the feature area:
Shell Test Locations (BATS)
| Feature Area | Test Path | Implementation Path |
|---|---|---|
| Installer libraries | tests/bats-tests/<lib>.bats |
installers/lib/<lib>.sh |
| Installer phases | tests/bats-tests/<phase>.bats |
installers/phases/<phase>.sh |
| Scripts | tests/test-<script>.sh |
scripts/<script>.sh |
| CLI features | tests/test-<feature>.sh |
ods-cli |
| Compose selection | tests/bats-tests/compose-select.bats |
installers/lib/compose-select.sh |
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.
- 2mo ago First seen · 509 lines · 17 tokens per session scan A 9dcee87bf9ba
tdd is a command published in the GitHub repository Osmantic/ODS (7,712 stars, last pushed today), licensed Apache-2.0. It adds 17 tokens to every session and 3,625 once invoked, about $0.0001 per session on Opus 5.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 commands, from other repositories
cpp-test
Enforce TDD workflow for C++. Write GoogleTest tests first, then implement. Verify coverage with gcov/lcov.
go-test
Go TDD workflow with table-driven tests.
rust-test
Rust TDD workflow with unit and property tests.
tdd
Test-driven development cycle — write the test first, then implement.
tdd
Test-driven change — write the failing test first, then implement.
lfe-tdd
Red-green-refactor quality pass on code the Builder just wrote. Use in the Builder sub-pipeline after lfe-builder completes implementation.