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-slotgit 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-slot)<a href="https://agentmods.dev/skills/konamgil/mandu/mandu-slot"><img src="https://agentmods.dev/badge/skills/konamgil/mandu/mandu-slot/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-slot"><img src="https://agentmods.dev/badge/skills/konamgil/mandu/mandu-slot.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
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 →
- medium Excessive Agency · line 49 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00065 | $0.00937 |
| Opus 5 | $0.00032 | $0.00468 |
| Sonnet 5 | $0.00013 | $0.00187 |
| Haiku 4.5 | $0.00006 | $0.00094 |
Grade A, and why
mandu-slot 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 11d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mandu Slot
Slot은 비즈니스 로직을 작성하는 파일입니다. Mandu.filling() API를 사용하여
API 핸들러, 인증 가드, 라이프사이클 훅을 구현합니다.
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 slot, API, or security domain.
Canonical workflow step: plan -> apply -> verify -> repair.
Preferred MCP tools:
| Step | Tools |
|---|---|
| plan | mandu.agent.plan, mandu.slot.read, mandu.slot.constraints |
| apply | mandu.agent.apply, mandu.generate |
| verify | mandu.agent.verify, mandu.slot.validate, mandu.contract.validate |
| repair | mandu.agent.repair |
Allowed file edits:
spec/slots/**/*.slot.ts- Route handlers that bind to the planned slot
- Contract files only when the plan includes contract work
Verification command:
mandu agent verify --changed --json --write
Common failures:
- Creating slot logic without checking
mandu.slot.constraints - Mixing auth/security changes into slot edits without security verification
- Returning untyped responses that drift from the linked contract
Repair path:
mandu agent repair --from .mandu/agent-verify.json --json
When to Apply
Reference these guidelines when:
- Creating new API endpoints with business logic
- Implementing authentication or authorization
- Adding request/response lifecycle hooks
- Working with request body, params, or query
- Handling errors and responses
Rule Categories by Priority
| Priority | Category | Impact | Prefix |
|---|---|---|---|
| 1 | Basic Structure | CRITICAL | slot-basic- |
| 2 | HTTP Methods | HIGH | slot-http- |
| 3 | Context API | HIGH | slot-ctx- |
| 4 | Guard Pattern | MEDIUM | slot-guard- |
| 5 | Lifecycle Hooks | MEDIUM | slot-lifecycle- |
Quick Reference
1. Basic Structure (CRITICAL)
slot-basic-structure- Always use Mandu.filling() as default exportslot-basic-location- Place slot files in spec/slots/ directory
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.
- 11d ago First seen · 126 lines · 65 tokens per session scan A 9c4e98ba372f
mandu-slot is a skill published in the GitHub repository konamgil/mandu (46 stars, last pushed 14d ago), licensed MPL-2.0. It adds 65 tokens to every session and 937 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
api-design-patterns
Comprehensive API design patterns covering REST, GraphQL, gRPC, versioning, authentication, and modern API best practices.
architecture-patterns
Software architecture patterns and best practices.
Full Stack Engineer
Full Stack Engineer delivers production-grade technical work with clear architecture, tests, maintainability, and operational awareness.
pipeline
This skill should be used when the user asks to "create a pipeline spec", "document data transformations", "document data flow", "specify pipeline invariants", "wyx pipeline", or wants to design, retrofit, or discover data pipelines with quality invariants and boundary ownership. Produces PIPELINE.md specs.
add-service
Add a service capsule (or Kafka topic node) to the Cosmos map. Use when the user says "add service X to the cosmos", "wire X into the map", or "add a topic node for Y". Researches the service from source, maps all its connections, then adds SERVICES/TOPICS entries to src/scenarios/ with correct position, color, and…
api-reviewer
Use when the user asks to review or change an HTTP, RPC, event, CLI, or SDK API contract. Inspect routes, schemas, authorization, errors, compatibility, and consumers before editing, then verify request and response behavior with focused tests.