Borrowing it
Nothing to install: this file belongs to ebibibi/ebi-agent-chat-relay. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ebibibi/ebi-agent-chat-relay/main/.claude/skills/tdd/SKILL.mdgit clone --depth 1 https://github.com/ebibibi/ebi-agent-chat-relayWrote 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/ebibibi/ebi-agent-chat-relay/tdd)<a href="https://agentmods.dev/skills/ebibibi/ebi-agent-chat-relay/tdd"><img src="https://agentmods.dev/badge/skills/ebibibi/ebi-agent-chat-relay/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.1 | $0.00024 | $0.01558 |
| Opus 5 | $0.00012 | $0.00779 |
| Sonnet 5 | $0.00005 | $0.00312 |
| Haiku 4.5 | $0.00002 | $0.00156 |
Grade C, and why
tdd scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
assert not re.match(r"^[\w-]+$", "invalid; rm -rf /") How it starts
The opening of the file, as written. The whole thing — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TDD — Test-Driven Development (Enforced)
This is not a suggestion. This is the workflow.
When adding features or fixing bugs in claude-code-discord-bridge, you MUST write tests before writing implementation code. No exceptions.
When to Activate
- Adding any new feature or functionality
- Fixing a bug (write a test that reproduces the bug FIRST)
- Refactoring code (ensure existing tests pass, add missing ones)
- Adding a new Cog, parser rule, UI component, or database operation
The Cycle: RED → GREEN → REFACTOR
Step 1: RED — Write Failing Tests
Write tests that describe the desired behavior. Run them. They must fail.
uv run pytest tests/test_new_feature.py -v
# Expected: FAILED (because the code doesn't exist yet)
If tests pass before you write any implementation, your tests are wrong.
Step 2: GREEN — Write Minimal Implementation
Write the minimum code to make the tests pass. No more.
uv run pytest tests/test_new_feature.py -v
# Expected: PASSED
Step 3: REFACTOR — Clean Up
Improve the implementation while keeping all tests green. Then run the full suite:
uv run pytest tests/ -v --cov=claude_discord --cov-report=term-missing
Step 4: VERIFY — Lint + Format + Full Suite
uv run ruff check claude_discord/
uv run ruff format claude_discord/
uv run pytest tests/ -v --cov=claude_discord
What to Test First (by module type)
New Parser Rule
# tests/test_parser.py — Write THIS first
def test_parse_new_event_type():
line = '{"type":"new_type","data":"value"}'
event = parse_line(line)
assert event is not None
assert event.message_type == MessageType.ASSISTANT
def test_parse_new_event_type_missing_data():
line = '{"type":"new_type"}'
event = parse_line(line)
assert event is not None # Should handle gracefully
# THEN implement in claude_discord/claude/parser.py
New Cog Command
# tests/test_new_cog.py — Write THIS first
from unittest.mock import AsyncMock, MagicMock
def test_rejects_unauthorized_user():
cog = MyCog(bot=MagicMock(), allowed_user_ids={111})
assert cog._is_authorized(999) is False
def test_accepts_authorized_user():
cog = MyCog(bot=MagicMock(), allowed_user_ids={111})
assert cog._is_authorized(111) is True
def test_validates_input_format():
# Test that invalid input is rejected before reaching CLI
assert not re.match(r"^[\w-]+$", "invalid; rm -rf /")
# THEN implement in claude_discord/cogs/my_cog.py
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 · 222 lines · 24 tokens per session scan C a937a02f1920
tdd is a skill published in the GitHub repository ebibibi/ebi-agent-chat-relay (56 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 1,558 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
test-first-implementation
Implement behavior with a red-green-refactor loop, observable tests, and small vertical slices. Use when the user asks for TDD, test-first work, regression-first fixes, or a feature that needs clear behavior before implementation.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code.
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
nw-fp-clojure
Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
tdd
This skill should be used when the user wants to implement features or fix bugs using test-driven development. Enforces the RED-GREEN-REFACTOR cycle with vertical slicing, context isolation between test writing and implementation, human checkpoints, and auto-test feedback loops. Uses multi-agent orchestration with the…