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 skills add EliasOulkadi/shokunin --skill test-commandergit clone --depth 1 https://github.com/EliasOulkadi/shokuninWrote 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/eliasoulkadi/shokunin/test-commander)<a href="https://agentmods.dev/skills/eliasoulkadi/shokunin/test-commander"><img src="https://agentmods.dev/badge/skills/eliasoulkadi/shokunin/test-commander/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/eliasoulkadi/shokunin/test-commander"><img src="https://agentmods.dev/badge/skills/eliasoulkadi/shokunin/test-commander.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 6 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Memory Poisoning · line 204 Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
- high Memory Poisoning · line 281 Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
- medium MCP Rug Pull · line 172 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 273 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 306 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 194 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00117 | $0.03107 |
| Opus 5 | $0.00059 | $0.01554 |
| Sonnet 5 | $0.00023 | $0.00621 |
| Haiku 4.5 | $0.00012 | $0.00311 |
Grade A, and why
test-commander 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 10d 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 — 321 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Commander
Tests that catch real bugs. Following the Testing Trophy (Kent C. Dodds): 80% integration, 10% unit, 10% E2E. Based on patterns from Testing Library, Playwright, MSW, and Chromatic.
Testing Trophy (visual)
/\
/E2E\ ← 2-3 critical flows
/------\
/ Visual \ ← Visual regression on key components
/----------\
/Integration\ ← 80% of tests. Components + API + store.
/--------------\
/ Unit \ ← Pure logic. Utils, helpers, formatters.
/------------------\
Static ← TypeScript + ESLint
Workflow
Step 1: Determine test level
| What are you testing? | Level | Tool | Speed |
|---|---|---|---|
| Pure logic (math, format, transform) | Unit | Vitest | < 5ms each |
| Component + API + store together | Integration | Testing Library + MSW | 50-200ms each |
| Critical user flow (checkout, signup) | E2E | Playwright | 2-10s each |
| Visual appearance | Visual | Playwright / Chromatic | 1-5s each |
Default: Integration. Catches 80% of bugs with 20% of maintenance cost.
Step 2: Write integration tests (5 mandatory states)
Every data-fetching component must test ALL five states:
describe('UserProfile', () => {
it('shows loading skeleton initially', async () => {
render(<UserProfile userId="123" />)
expect(screen.getByRole('status')).toHaveTextContent('Loading...')
})
it('shows error state with retry button', async () => {
server.use(http.get('/api/users/123', () => new HttpResponse(null, { status: 500 })))
render(<UserProfile userId="123" />)
await waitFor(() => {
expect(screen.getByRole('alert')).toHaveTextContent('Failed to load')
})
expect(screen.getByRole('button', { name: /retry/i })).toBeInTheDocument()
})
it('shows empty state when no data', async () => {
server.use(http.get('/api/users/123', () => HttpResponse.json(null)))
render(<UserProfile userId="123" />)
await waitFor(() => {
expect(screen.getByText(/no user found/i)).toBeInTheDocument()
})
})
it('renders user data on success', async () => {
render(<UserProfile userId="123" />)
await screen.findByText('Alice')
expect(screen.getByText('[email protected]')).toBeInTheDocument()
})
it('handles race condition: fast re-fetch', async () => {
const { rerender } = render(<UserProfile userId="123" />)
await screen.findByText('Alice')
rerender(<UserProfile userId="456" />)
await screen.findByText('Bob')
expect(screen.queryByText('Alice')).not.toBeInTheDocument()
})
})
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 321 lines · 117 tokens per session scan A db0c391a829d
test-commander is a skill published in the GitHub repository EliasOulkadi/shokunin (113 stars, last pushed 1mo ago), licensed MIT. It adds 117 tokens to every session and 3,107 once invoked, about $0.0006 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 skills, from other repositories
memstack-development-test-writer
Use this skill when the user says 'write tests', 'add tests', 'test coverage', 'unit tests', 'integration tests', 'component tests', 'mocking', 'edge cases', or needs to generate tests with proper mocking and edge case coverage. Do NOT use for refactoring plans or database migrations.
mandu-testing
Testing patterns for Mandu applications. Use when writing unit tests, integration tests, or E2E tests. Triggers on test, spec, Bun test, Playwright, or testing tasks.
react-testing-workflows
Testing strategy and execution for React applications. Covers Vitest configuration, React Testing Library patterns, custom hook testing, Playwright E2E, Storybook stories and play functions, and coverage reporting. Keywords: test, vitest, testing library, playwright, storybook, coverage, unit test, integration test…
testing-strategy
Choose the right test type for every change — unit, integration, contract, end-to-end, property-based, mutation, fuzz. Use when adding tests to a new feature, deciding what to test for a bug fix, designing a test pyramid for a service, evaluating coverage targets, or untangling a slow test suite. Stack-agnostic…
dev-testing
A testing guide that defines when to use unit, integration, API, and end-to-end tests. Unit tests check small pieces of code, while end-to-end tests check a full user flow.
redbar.fix
Write the missing tests for the gaps redbar found, following the canonical standard for that layer (Playwright's best practices for e2e, Vitest/Jest idiom for unit, Testcontainers for integration). Reads .redbar/gaps.json, writes one test file per gap, RUNS each test it wrote, and never leaves a failing test behind …