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/classmethod/tsumiki/test-optimization-patternsgit clone --depth 1 https://github.com/classmethod/tsumikiWhat 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.00026 | $0.05330 |
| Opus 5 | $0.00013 | $0.02665 |
| Sonnet 5 | $0.00005 | $0.01066 |
| Haiku 4.5 | $0.00003 | $0.00533 |
Grade A, and why
test-optimization-patterns 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 yesterday.
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 — 744 lines — stays where its author put it; the contents beside it link to each section on GitHub.
テスト最適化パターン集
テスト実行速度を改善するためのリファクタリングパターンとベストプラクティスをまとめたドキュメントです。
パターン一覧
| パターン | 効果 | 難易度 | リスク |
|---|---|---|---|
| 1. データベーストランザクション | ★★★★★ | 低 | 低 |
| 2. ファイルI/Oのモック化 | ★★★★★ | 低 | 低 |
| 3. 外部APIのモック化 | ★★★★★ | 中 | 低 |
| 4. beforeEach → beforeAll | ★★★☆☆ | 低 | 中 |
| 5. 非同期待機の最適化 | ★★★☆☆ | 中 | 低 |
| 6. テストデータファクトリー | ★★☆☆☆ | 中 | 低 |
| 7. テストの粒度見直し | ★★★☆☆ | 高 | 中 |
| 8. 並列実行可能な設計 | ★★★☆☆ | 中 | 中 |
パターン1: データベーストランザクション
概要
各テストでデータベースのクリア・再投入を行うと、I/O待機時間が累積して遅くなります。トランザクションを使ってロールバックすることで、物理的なDELETE/INSERTを避けて高速化できます。
適用条件
- ✅ beforeEach でデータのクリア・再投入を行っている
- ✅ テストごとにクリーンな状態が必要
- ✅ データベースがトランザクションをサポート
Before(遅い実装)
describe('User API', () => {
beforeEach(async () => {
// 毎回DELETE・INSERT(遅い)
await db.query('DELETE FROM users');
await db.query('DELETE FROM posts');
await db.query('INSERT INTO users (id, name) VALUES (1, "Test")');
await db.query('INSERT INTO posts (id, user_id, title) VALUES (1, 1, "Post")');
});
afterEach(async () => {
await db.disconnect();
});
it('should get user', async () => {
const user = await getUserById(1);
expect(user.name).toBe('Test');
});
it('should get posts', async () => {
const posts = await getPostsByUserId(1);
expect(posts).toHaveLength(1);
});
});
After(高速実装)
describe('User API', () => {
let transaction;
beforeEach(async () => {
// トランザクション開始
transaction = await db.transaction();
// データ準備(トランザクション内)
await transaction.query('INSERT INTO users (id, name) VALUES (1, "Test")');
await transaction.query('INSERT INTO posts (id, user_id, title) VALUES (1, 1, "Post")');
});
afterEach(async () => {
// ロールバック(高速)
await transaction.rollback();
});
it('should get user', async () => {
const user = await getUserById(1);
expect(user.name).toBe('Test');
});
it('should get posts', async () => {
const posts = await getPostsByUserId(1);
expect(posts).toHaveLength(1);
});
});
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.
- yesterday First seen · 744 lines · 26 tokens per session scan A 584d95839093
test-optimization-patterns is a command published in the GitHub repository classmethod/tsumiki (974 stars, last pushed 25d ago), licensed MIT. It adds 26 tokens to every session and 5,330 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-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.