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 design-sparx/mantine-analytics-dashboard --skill tdd-workflowgit clone --depth 1 https://github.com/design-sparx/mantine-analytics-dashboardWrote 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/design-sparx/mantine-analytics-dashboard/tdd-workflow)<a href="https://agentmods.dev/skills/design-sparx/mantine-analytics-dashboard/tdd-workflow"><img src="https://agentmods.dev/badge/skills/design-sparx/mantine-analytics-dashboard/tdd-workflow/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/design-sparx/mantine-analytics-dashboard/tdd-workflow"><img src="https://agentmods.dev/badge/skills/design-sparx/mantine-analytics-dashboard/tdd-workflow.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.00030 | $0.00154 |
| Opus 5.5 | $0.00012 | $0.00062 |
| Sonnet 5.5 | $0.00006 | $0.00031 |
| Haiku 4.5 | $0.00003 | $0.00015 |
Grade A, and why
tdd-workflow 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 7d 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 Workflow
Follow ECC-inspired test-driven development for this project.
When to Use
- New features
- Bug fixes
- Refactors that change behavior
- Any change that needs verification
Workflow
- Write the test first (RED)
- Run it and confirm it fails for the right reason
- Write minimal implementation (GREEN)
- Run it and confirm it passes
- Refactor while keeping tests green
- Verify coverage
Test Structure
Use Arrange-Act-Assert with descriptive names that explain the behavior under test.
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.
- 7d ago First seen · 29 lines · 30 tokens per session scan A 3748f507aab2
tdd-workflow is a skill published in the GitHub repository design-sparx/mantine-analytics-dashboard (387 stars, last pushed yesterday), licensed MIT. It adds 30 tokens to every session and 154 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-09-24.
Other skills, from other repositories
server-side-calls
Call tRPC procedures directly from server code using t.createCallerFactory() and router.createCaller(context) for integration testing, internal server logic, and custom API endpoints. Catch TRPCError and extract HTTP status with getHTTPStatusCodeFromError(). Error handling via onError option.
implement-feature
Implement an approved feature plan with fresh-context slices, TDD, evidence, and PR-ready output.
common-subagent-driven-development
Execute multi-task implementation plans by dispatching a fresh implementer subagent per task with independent review gates. Use when implementing plans, executing multi-task PRs, or transitioning from planning to implementation.
common-tdd
Guides quality-first TDD for new behavior, bug fixes, and test changes. Selects the smallest test layer, proves a distinct regression risk, and runs bounded RED-GREEN-REFACTOR verification.
tdd
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
dpf-tdd
Use for DPF test-first work. Write the failing behavior test first, make it green, refactor, then run the functional gate; never claim an unrun test passed.