Context Engineering Kit is a collection of skills, agents, hooks, instructions, commands, and plugins that shape how coding agents use context and carry out development work. It is for developers using Claude Code and other supported coding agents who want more predictable results. The catalogue entries are components from this collection.
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 NeoLabHQ/context-engineering-kit --skill test-driven-developmentgit clone --depth 1 https://github.com/NeoLabHQ/context-engineering-kitWrote 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/neolabhq/context-engineering-kit/test-driven-development)<a href="https://agentmods.dev/skills/neolabhq/context-engineering-kit/test-driven-development"><img src="https://agentmods.dev/badge/skills/neolabhq/context-engineering-kit/test-driven-development/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/neolabhq/context-engineering-kit/test-driven-development"><img src="https://agentmods.dev/badge/skills/neolabhq/context-engineering-kit/test-driven-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- 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.00042 | $0.04271 |
| Opus 5.5 | $0.00017 | $0.01708 |
| Sonnet 5.5 | $0.00008 | $0.00854 |
| Haiku 4.5 | $0.00004 | $0.00427 |
Grade A, and why
test-driven-development 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 1mo 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.
The source is not reproduced here
Licensed GPL-3.0
The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 1mo ago First seen · 699 lines · 42 tokens per session scan A 6042b77d6b66
test-driven-development is a skill published in the GitHub repository NeoLabHQ/context-engineering-kit (1,779 stars, last pushed 1mo ago), licensed GPL-3.0. It adds 42 tokens to every session and 4,271 once invoked, about $0.0002 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-03.
Other skills, from other repositories
tdd
Test-driven development — write failing tests first, then implement to make them pass.
test-driven-development
A test-driven development (TDD) workflow: write a test first, confirm that it fails, add the smallest implementation, and then clean up the code.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code.
test-driven-development
Drives development with tests using the red-green-refactor loop. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality. Use when asked to add tests to a function, fix a bug…
bad-case-to-dpo
A guide to turning failed production agent runs into training and evaluation data. It explains how to find the first mistake, create preference examples for DPO (Direct Preference Optimization), and check that a fix does not damage other tasks.
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.