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 agentmods add commands/vishnu2kmohan/mcp-server-langgraph/tddgit clone --depth 1 https://github.com/vishnu2kmohan/mcp-server-langgraphWrote 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/vishnu2kmohan/mcp-server-langgraph/tdd)<a href="https://agentmods.dev/commands/vishnu2kmohan/mcp-server-langgraph/tdd"><img src="https://agentmods.dev/badge/commands/vishnu2kmohan/mcp-server-langgraph/tdd.svg" alt="Measured on agentmods" 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 | $0.00018 | $0.00995 |
| Opus 5 | $0.00009 | $0.00498 |
| Sonnet 5 | $0.00004 | $0.00199 |
| Haiku 4.5 | $0.00002 | $0.00100 |
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 4d 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Start TDD Workflow
Begin Test-Driven Development (TDD) workflow for a new feature or bug fix.
Usage
/tdd
Workflow
🔴 RED Phase - Write Failing Tests
-
Understand the requirement:
- What behavior needs to be implemented?
- What are the expected inputs and outputs?
- What edge cases need to be handled?
-
Write the test FIRST:
# Example: tests/test_feature.py def test_feature_handles_valid_input(): # GIVEN: Valid input input_data = {"key": "value"} # WHEN: Function is called result = my_feature(input_data) # THEN: Returns expected output assert result == expected_output -
Run the test to verify it FAILS:
pytest tests/test_feature.py::test_feature_handles_valid_input -xvsExpected: Test should FAIL with clear error message. Why: Proves the test is actually testing something and isn't a false positive.
-
Commit the failing test:
git add tests/test_feature.py git commit -m "test: add failing test for feature X"
🟢 GREEN Phase - Implement Minimal Code
-
Write the simplest code to make test pass:
# src/module/feature.py def my_feature(input_data): # Minimal implementation return expected_output -
Run the test to verify it PASSES:
pytest tests/test_feature.py::test_feature_handles_valid_input -xvsExpected: Test should PASS.
-
Run all tests to ensure no regressions:
make test-unit -
Commit the implementation:
git add src/module/feature.py git commit -m "feat: implement feature X Adds minimal implementation to make test pass. Closes #123"
♻️ REFACTOR Phase - Improve Code Quality
- Refactor for better design:
- Extract functions for clarity
- Add type hints
- Improve variable names
- Add docstrings
- Remove duplication
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.
- 4d ago First seen · 162 lines · 18 tokens per session scan A 16378d40d962
tdd is a command published in the GitHub repository vishnu2kmohan/mcp-server-langgraph (4 stars, last pushed 11d ago), licensed MIT. It adds 18 tokens to every session and 995 once invoked, about $0.0001 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 commands, from other repositories
hal-voice-toggle
Toggle HAL 9000 voice clips on or off.
tdd
Test-driven development with TodoWrite planning and comprehensive testing.
tdd
Test-driven development with TodoWrite planning and comprehensive testing.
domains
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
deps-age
Analyze dependency freshness and maintenance activity.
criar-skill
Use when creating new skills, automations, or specialized knowledge packages. Keywords: criar skill, nova skill, automatizar, conhecimento, TDD skill.