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 konamgil/mandu --skill mandu-testinggit clone --depth 1 https://github.com/konamgil/manduWrote 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/konamgil/mandu/mandu-testing)<a href="https://agentmods.dev/skills/konamgil/mandu/mandu-testing"><img src="https://agentmods.dev/badge/skills/konamgil/mandu/mandu-testing/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/konamgil/mandu/mandu-testing"><img src="https://agentmods.dev/badge/skills/konamgil/mandu/mandu-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00042 | $0.00861 |
| Opus 5.5 | $0.00017 | $0.00344 |
| Sonnet 5.5 | $0.00008 | $0.00172 |
| Haiku 4.5 | $0.00004 | $0.00086 |
Grade A, and why
mandu-testing 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 1mo 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mandu Testing
Mandu 애플리케이션의 테스트 패턴 가이드. Bun test를 활용한 단위 테스트, slot 테스트, Island 컴포넌트 테스트, Playwright E2E 테스트를 다룹니다.
Agent Workflow Contract
This skill is a Domain addendum. It must not replace mandu-agent-workflow.
Use it only after mandu.agent.plan selects testing or mandu.agent.verify asks for targeted test coverage.
Canonical workflow step: verify -> repair.
Preferred MCP tools:
| Step | Tools |
|---|---|
| plan | mandu.agent.plan |
| verify | mandu.agent.verify, mandu.run.tests, mandu.ate.generate, mandu.ate.run |
| repair | mandu.agent.repair, mandu.ate.heal |
Allowed file edits:
- Co-located
*.test.ts/*.test.tsxfiles tests/e2e/**/*.spec.ts- Test fixtures and mocks scoped to the planned domain
Verification command:
mandu agent verify --changed --json --write
Common failures:
- Running broad watch-mode tests as an agent default
- Adding tests that bypass the route/slot/contract path under change
- Applying ATE healing before reading the verify report
Repair path:
mandu agent repair --from .mandu/agent-verify.json --json
When to Apply
Reference these guidelines when:
- Writing unit tests for slots
- Testing Island components
- Setting up E2E tests with Playwright
- Mocking external dependencies
- Testing authentication flows
Rule Categories by Priority
| Priority | Category | Impact | Prefix |
|---|---|---|---|
| 1 | Slot Testing | HIGH | test-slot- |
| 2 | Component Testing | HIGH | test-component- |
| 3 | E2E Testing | MEDIUM | test-e2e- |
| 4 | Mocking | MEDIUM | test-mock- |
Quick Reference
1. Slot Testing (HIGH)
test-slot-unit- Unit test slot handlerstest-slot-guard- Test guard authenticationtest-slot-integration- Integration test with database
2. Component Testing (HIGH)
test-component-island- Test Island componentstest-component-render- Test rendering outputtest-component-interaction- Test user interactions
What ships with it
7 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.
- 1mo ago First seen · 133 lines · 42 tokens per session scan A d45c3e2b80e8
mandu-testing is a skill published in the GitHub repository konamgil/mandu (47 stars, last pushed 1mo ago), licensed MPL-2.0. It adds 42 tokens to every session and 861 once invoked, about $0.0002 per session on Opus 5.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
test-strategist
This skill should be used when the user asks to "plan test strategy", "improve test coverage", "fix flaky tests", "optimize test performance", or needs guidance on testing infrastructure and quality assurance. Provides expert guidance on test strategy design, coverage analysis, and test quality improvement.
vue-component-testing
Applies the three-tier test taxonomy for Vue 3 applications: writes unit tests for composables and Pinia stores with Vitest, component tests for behaviour and user interactions with @testing-library/vue, and acceptance tests for full user flows with Playwright. Ensures tests focus on observable behaviour, not…
testing-strategy
Test naming conventions, fixture patterns, mocking strategies, and coverage thresholds by stage.
testing-automation-expert
Production-grade testing strategies for robust, maintainable systems. Covers unit/integration/E2E testing, contract testing, accessibility, mutation testing, and CI/CD patterns. Supports Python (pytest) and TypeScript (Jest/Vitest/Playwright).
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
axiom-testing
Use when writing ANY test, debugging flaky tests, making tests faster, or choosing Swift Testing vs XCTest. Covers unit tests, UI tests, async testing, test architecture.