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 DominikTobureto/awesome-grok-build --skill tdd-test-engineergit clone --depth 1 https://github.com/DominikTobureto/awesome-grok-buildWrote 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/dominiktobureto/awesome-grok-build/tdd-test-engineer)<a href="https://agentmods.dev/skills/dominiktobureto/awesome-grok-build/tdd-test-engineer"><img src="https://agentmods.dev/badge/skills/dominiktobureto/awesome-grok-build/tdd-test-engineer/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/dominiktobureto/awesome-grok-build/tdd-test-engineer"><img src="https://agentmods.dev/badge/skills/dominiktobureto/awesome-grok-build/tdd-test-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00037 | $0.00362 |
| Opus 5 | $0.00018 | $0.00181 |
| Sonnet 5 | $0.00007 | $0.00072 |
| Haiku 4.5 | $0.00004 | $0.00036 |
Grade A, and why
tdd-test-engineer 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 12d 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 Test Engineer
Make behavior executable before changing implementation.
Grok Build Mode
- Use Plan Mode for new test strategy, broad CI changes, or uncertain behavior.
- Use subagents for test work:
behavior: expected behavior and edge cases.fixtures: setup/data/mocking strategy.failure: reproduce current bug or CI failure.coverage: missing test surfaces.
- Arena-style test design: compare several test strategies and choose the smallest test that proves the behavior.
- Human-in-the-loop: get approval before deleting or weakening tests.
Workflow
- Identify the behavior or bug.
- Find existing test style and commands.
- Write or propose a failing test first.
- Run the narrow test and capture failure.
- Implement the smallest fix.
- Re-run the narrow test, then broader checks if cheap.
- Summarize the regression protected.
Test Quality Rules
- Prefer behavior assertions over implementation details.
- Avoid sleeps; use deterministic waiting or mocks.
- Keep fixtures small.
- Do not snapshot volatile output without normalization.
- Do not remove failing tests unless they are invalid and the user approves.
Example Prompts
Use tdd-test-engineer. Add a failing regression test for this bug before fixing it.
Use subagents to inspect flaky test causes: timing, shared state, network, fixture leakage. Propose the smallest deterministic fix.
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.
- 12d ago First seen · 50 lines · 37 tokens per session scan A 1797469c5a69
tdd-test-engineer is a skill published in the GitHub repository DominikTobureto/awesome-grok-build (61 stars, last pushed 19d ago), licensed MIT. It adds 37 tokens to every session and 362 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-30.
Other skills, from other repositories
openspec-superpowers
Bridge between OpenSpec's SDD-TDD workflow and Superpowers skills. Provides plan, run, verify, and archive modes to drive spec-driven, test-driven development from proposal through to archived change.
codegraph
Analyze indexed codebases via graph database (neug) and vector index (zvec). Covers call graphs, dependencies, dead code, hotspots, module coupling, architecture reports, semantic search, impact analysis, bug root cause from GitHub issues, class diagrams (UML), and PR review (risk scoring, conflict detection…
stuck
Diagnose frozen, stuck, or slow Qwen Code sessions on this machine. Scans for problematic processes, high CPU/memory usage, hung subprocesses, and debug logs. Use /stuck or /stuck to focus on a specific process.
e2e-testing
Guide for running end-to-end tests of the Qwen Code CLI, including headless mode, MCP server testing, and API traffic inspection. Use this skill whenever you need to verify CLI behavior with real model calls, reproduce user-reported bugs end-to-end, test MCP tool integrations, or inspect raw API request/response…
structured-debugging
Hypothesis-driven debugging methodology for hard bugs. Use this skill whenever you're investigating non-trivial bugs, unexpected behavior, flaky tests, or tracing issues through complex systems. Activate proactively when debugging requires more than a quick glance — especially when the first attempt at a fix didn't…
terminal-capture
Automates terminal UI screenshot testing for CLI commands. Applies when reviewing PRs that affect CLI output, testing slash commands (/about, /context, /auth, /export), generating visual documentation, or when 'terminal screenshot', 'CLI test', 'visual test', or 'terminal-capture' is mentioned.