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/dachivadachkoria/claude-code-starter-kit/testgit clone --depth 1 https://github.com/dachivadachkoria/claude-code-starter-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/commands/dachivadachkoria/claude-code-starter-kit/test)<a href="https://agentmods.dev/commands/dachivadachkoria/claude-code-starter-kit/test"><img src="https://agentmods.dev/badge/commands/dachivadachkoria/claude-code-starter-kit/test.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.00020 | $0.00741 |
| Opus 5 | $0.00010 | $0.00370 |
| Sonnet 5 | $0.00004 | $0.00148 |
| Haiku 4.5 | $0.00002 | $0.00074 |
Grade A, and why
test 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 3d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unit Test Generation
Generate comprehensive unit tests for: $ARGUMENTS
Execution Flow
Step 1: Determine Target Files
If $ARGUMENTS contains a file path:
- Test that specific file
If $ARGUMENTS is --changed or empty:
- Run:
git diff --name-only HEAD~1 | grep -E '\.(py|js|ts|go)$' - Test all changed source files
If $ARGUMENTS is --staged:
- Run:
git diff --cached --name-only | grep -E '\.(py|js|ts|go)$' - Test all staged files
Step 2: Analyze Source Code
For each target file:
- Read the entire file
- Identify all public functions/methods/classes
- Note dependencies and imports
- Check for existing tests
Step 3: Generate Tests
For each function/method, create tests for:
Happy Path
- Normal inputs → expected outputs
- Multiple valid input variations
Edge Cases
- Empty inputs (null, empty string, empty array)
- Boundary values (0, -1, MAX_INT)
- Single element collections
Error Handling
- Invalid inputs
- Exception scenarios
- Network/IO failures (mocked)
Async Behavior (if applicable)
- Successful async operations
- Timeout handling
- Concurrent execution
Step 4: Apply Project Conventions
Read CLAUDE.md and existing tests to match:
- Naming conventions
- File structure
- Assertion style
- Mocking patterns
- Fixture usage
Step 5: Write and Verify
- Create test file in appropriate location
- Run the new tests
- Fix any failures
- Report coverage delta
Output Format
📁 Generated: tests/test_<module>.py
✅ Tests: 12 passed
📊 Coverage: 87% (+15%)
Language-Specific Patterns
Python (pytest)
import pytest
from unittest.mock import Mock, patch
class TestClassName:
def test_method_success_returns_expected(self):
# Arrange
...
# Act
result = function_under_test(input)
# Assert
assert result == expected
JavaScript/TypeScript (jest)
describe('ClassName', () => {
describe('methodName', () => {
it('should return expected when given valid input', () => {
// Arrange
...
// Act
const result = functionUnderTest(input);
// Assert
expect(result).toEqual(expected);
});
});
});
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.
- 3d ago First seen · 134 lines · 20 tokens per session scan A d35588925eec
test is a command published in the GitHub repository dachivadachkoria/claude-code-starter-kit (4 stars, last pushed 5mo ago), licensed MIT. It adds 20 tokens to every session and 741 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
sdlc-cycle
이슈/기획서 기준 SDLC 한 사이클(이슈→개발→테스트→검증→PR/MR)을 사람 개입 없이 자동 실행.
knowledge-graph
AGENTS.md 생태계(rules·memory·agents·skills·commands·workflows)의 연결 구조를 1장의 대시보드로 뽑는다. 온보딩·문서 정합성 점검용.
fix-issue
이슈 #$ARGUMENTS 를 처리한다(이슈 우선 워크플로).
README
반복 작업을 /이름 으로 호출. 파일명 = 커맨드 이름(fix-issue.md → /fix-issue). frontmatter name/argument-hint, 본문에 프롬프트. $ARGUMENTS 로 인자 수신.
test
Command "test" from jzl-maker/EA-SKILL, covering 命令: /ea test (测试生成与执行), 功能, 触发, 单元测试(unit) and 流程.
test-gen
Generate comprehensive tests for a specified file with edge cases and error scenarios.