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-hydrationgit 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-hydration)<a href="https://agentmods.dev/skills/konamgil/mandu/mandu-hydration"><img src="https://agentmods.dev/badge/skills/konamgil/mandu/mandu-hydration/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-hydration"><img src="https://agentmods.dev/badge/skills/konamgil/mandu/mandu-hydration.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.00051 | $0.01087 |
| Opus 5 | $0.00026 | $0.00544 |
| Sonnet 5 | $0.00010 | $0.00217 |
| Haiku 4.5 | $0.00005 | $0.00109 |
Grade A, and why
mandu-hydration 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 9d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mandu Island Hydration
Island Hydration은 페이지의 일부분만 클라이언트에서 인터랙티브하게 만드는 기술입니다. 대부분의 페이지는 정적 HTML로 유지하고, 필요한 부분만 JavaScript를 로드합니다.
Agent Workflow Contract
This skill is a Domain addendum. It must not replace mandu-agent-workflow.
Use it only after mandu.agent.plan selects the hydration, island, partial, or route domain.
Canonical workflow step: plan -> apply -> verify -> repair.
Preferred MCP tools:
| Step | Tools |
|---|---|
| plan | mandu.agent.plan, mandu.island.list |
| apply | mandu.agent.apply, mandu.hydration.set, mandu.hydration.addClientSlot |
| verify | mandu.agent.verify, mandu.build, mandu.build.status |
| repair | mandu.agent.repair |
Allowed file edits:
app/**/*.partial.tsx,app/**/*.island.tsx, route-local client components- Page hydration metadata only when the plan names the route
- Shared client utilities only after inspecting existing client boundaries
Verification command:
mandu agent verify --changed --json --write
Common failures:
- Rendering page-level islands inline instead of using
partial().Render - Forgetting route hydration metadata when a server page renders partials
- Moving server-only imports into client bundles
Repair path:
mandu agent repair --from .mandu/agent-verify.json --json
When to Apply
Reference these guidelines when:
- Creating interactive client components
- Adding client-side state to pages
- Implementing partial hydration
- Setting up client-server data flow
- Working with Island communication
Rule Categories by Priority
| Priority | Category | Impact | Prefix |
|---|---|---|---|
| 1 | Client Directive | CRITICAL | hydration-directive- |
| 2 | Island Structure | HIGH | hydration-island- |
| 3 | Hydration Priority | MEDIUM | hydration-priority- |
| 4 | Data Flow | MEDIUM | hydration-data- |
Quick Reference
1. Client Directive (CRITICAL)
hydration-directive-use-client- Add "use client" directive for client componentshydration-directive-file-naming- Use .client.tsx for client component files
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.
- 9d ago First seen · 140 lines · 51 tokens per session scan A 15bbbd25496e
mandu-hydration is a skill published in the GitHub repository konamgil/mandu (46 stars, last pushed 12d ago), licensed MPL-2.0. It adds 51 tokens to every session and 1,087 once invoked, about $0.0003 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
Full Stack Engineer
Full Stack Engineer delivers production-grade technical work with clear architecture, tests, maintainability, and operational awareness.
accessibility-auditor
Use when the user asks to audit accessibility, keyboard usability, semantics, contrast, focus behavior, or assistive-technology support in a UI. Inspect the actual rendered page and interaction states, report evidence-backed findings, and only implement fixes when explicitly requested.
ui-implementer
Use when the user asks to implement or revise a web, desktop, or mobile interface from a requirement, design, or screenshot. Inspect the existing UI architecture and real runtime first, reuse established components and tokens, and verify the rendered DOM, responsive states, and browser errors.
visual-regression-tester
Use when the user asks to detect, review, prevent, or update visual regressions in a web, desktop, or mobile interface. Capture comparable rendered states, control viewport and data variance, inspect image differences, and distinguish intended design changes from rendering defects.
frontend-agent
Generate UI components from PRD + design tokens when no Figma design is provided. Activated when implementing frontend features without a Figma link.
apple-design
Apple's approach to interface design and fluid, physical motion, translated for the web. Use when building or reviewing gesture-driven UI, spring animations, drag/swipe/sheet interactions, momentum and interruptible transitions, translucent materials and depth, typography (optical sizing, tracking, leading)…