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/docsgit clone --depth 1 https://github.com/dachivadachkoria/claude-code-starter-kitWhat 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.00008 | $0.01076 |
| Opus 5 | $0.00004 | $0.00538 |
| Sonnet 5 | $0.00002 | $0.00215 |
| Haiku 4.5 | $0.00001 | $0.00108 |
Grade A, and why
docs 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 2d 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 — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Generator
Generate documentation for: $ARGUMENTS
Target Selection
If $ARGUMENTS is empty:
- Generate/update README.md
- Update API documentation
- Check for missing docstrings
If $ARGUMENTS is a file:
- Generate docstrings for all public functions/classes
- Create/update corresponding docs
If $ARGUMENTS is --api:
- Generate API endpoint documentation
- Create OpenAPI/Swagger spec if applicable
Documentation Types
1. Function/Method Docstrings
Python (Google style):
def process_payment(amount: float, currency: str = "USD") -> PaymentResult:
"""Process a payment transaction.
Args:
amount: The payment amount in the smallest currency unit.
currency: ISO 4217 currency code. Defaults to "USD".
Returns:
PaymentResult containing transaction ID and status.
Raises:
PaymentError: If the payment fails.
ValidationError: If amount is negative.
Example:
>>> result = process_payment(1000, "EUR")
>>> print(result.transaction_id)
'txn_abc123'
"""
TypeScript (JSDoc):
/**
* Process a payment transaction.
*
* @param amount - The payment amount in cents
* @param currency - ISO 4217 currency code
* @returns Promise resolving to PaymentResult
* @throws {PaymentError} If the payment fails
*
* @example
* const result = await processPayment(1000, 'EUR');
* console.log(result.transactionId);
*/
Go:
// ProcessPayment handles a payment transaction.
//
// It accepts the amount in the smallest currency unit and an optional
// currency code (defaults to "USD").
//
// Returns a PaymentResult or an error if the payment fails.
func ProcessPayment(amount int64, currency string) (*PaymentResult, error) {
2. Class/Module Documentation
"""User authentication and session management.
This module provides:
- User login/logout functionality
- Session token generation and validation
- Password hashing and verification
Typical usage:
from auth import AuthService
auth = AuthService()
token = auth.login(username, password)
user = auth.validate_token(token)
Security Notes:
- Tokens expire after 24 hours
- Failed logins are rate-limited
- Passwords are hashed with bcrypt
"""
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.
- 2d ago First seen · 225 lines · 8 tokens per session scan A e2620fad407f
docs is a command published in the GitHub repository dachivadachkoria/claude-code-starter-kit (4 stars, last pushed 5mo ago), licensed MIT. It adds 8 tokens to every session and 1,076 once invoked, about $0.0000 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 로 인자 수신.
sonar
SonarQube 정적분석 실행 및 결과 조회. 코드 품질·보안 핫스팟·커버리지 확인 시 사용.
tailtest-hunt
Run an adversarial pass on $ARGUMENTS -- explicitly try to break the source code.