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 AyushParkara/syntra --skill tddgit clone --depth 1 https://github.com/AyushParkara/syntraWrote 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/ayushparkara/syntra/tdd)<a href="https://agentmods.dev/skills/ayushparkara/syntra/tdd"><img src="https://agentmods.dev/badge/skills/ayushparkara/syntra/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/ayushparkara/syntra/tdd"><img src="https://agentmods.dev/badge/skills/ayushparkara/syntra/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.00032 | $0.00264 |
| Opus 5 | $0.00016 | $0.00132 |
| Sonnet 5 | $0.00006 | $0.00053 |
| Haiku 4.5 | $0.00003 | $0.00026 |
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 8d 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
You practice strict test-driven development. The cycle is RED → GREEN → REFACTOR.
RED — write a failing test first:
- Write the smallest test that captures the next bit of desired behavior.
- Run it. Confirm it FAILS for the right reason (the behavior doesn't exist yet). A test that passes immediately tested nothing.
GREEN — make it pass with the simplest code: 3. Write the minimum code to make the test pass. No extra features. 4. Run the test. Confirm it now passes, and existing tests still pass.
REFACTOR — clean up with the safety net: 5. Improve naming, remove duplication, simplify — tests stay green throughout.
Rules:
- Never write production code without a failing test demanding it.
- One behavior per test; descriptive test names.
- If a test passes on first run, it's suspect — verify it actually exercises the path.
- Keep the cycle tight: small test, small code, repeat.
Output: Show the test first, confirm RED, then the code, confirm GREEN.
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.
- 8d ago First seen · 28 lines · 32 tokens per session scan A 83773700cb3e
tdd is a skill published in the GitHub repository AyushParkara/syntra (5 stars, last pushed 28d ago), licensed Apache-2.0. It adds 32 tokens to every session and 264 once invoked, about $0.0002 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
tdd
A test-driven development workflow based on repeating three stages: write a failing test, make it pass, then improve the code. The tests focus on what users can do through public interfaces rather than internal implementation details.
go
Go phase. Reads the approved SPEC file, maps Requirements to tasks (plan), executes via TDD (build), and integrates results verifying all Acceptance Criteria.
tdd
Test-Driven Development enforcer. Red→Green→Refactor cycle with no production code without a failing test first. Use for new features and bug fixes.
skill-test
Verifies that the skill system is working correctly.
test-writer
Writes tests that fail before a fix and pass after it.
taiyi-dev
A software-development stage that implements planned tasks using test-driven development, or TDD: write a failing test, make it pass, then improve the code. It checks the task plan, dependencies, file boundaries, and required completion evidence.