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-fs-routesgit 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-fs-routes)<a href="https://agentmods.dev/skills/konamgil/mandu/mandu-fs-routes"><img src="https://agentmods.dev/badge/skills/konamgil/mandu/mandu-fs-routes/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-fs-routes"><img src="https://agentmods.dev/badge/skills/konamgil/mandu/mandu-fs-routes.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.00058 | $0.00886 |
| Opus 5 | $0.00029 | $0.00443 |
| Sonnet 5 | $0.00012 | $0.00177 |
| Haiku 4.5 | $0.00006 | $0.00089 |
Grade A, and why
mandu-fs-routes 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mandu FS Routes
FS Routes는 파일 시스템 기반 라우팅입니다. app/ 폴더의 파일 구조가 URL이 됩니다.
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 route or API domain.
Canonical workflow step: plan -> apply -> verify.
Preferred MCP tools:
| Step | Tools |
|---|---|
| plan | mandu.agent.plan, mandu.route.list |
| apply | mandu.agent.apply, mandu.generate, mandu.route.add |
| verify | mandu.agent.verify, mandu.manifest.validate |
| repair | mandu.agent.repair |
Allowed file edits:
app/**/page.tsx,app/**/layout.tsx,app/**/route.ts- Route-local metadata files and co-located helpers
- Related contract/slot files only when the plan includes those domains
Verification command:
mandu agent verify --changed --json --write
Common failures:
- Creating a page or API route before reading the local
app/pattern - Editing generated route manifests by hand
- Adding API files without contract verification when the plan includes API work
Repair path:
mandu agent repair --from .mandu/agent-verify.json --json
When to Apply
Reference these guidelines when:
- Creating new pages or API endpoints
- Setting up dynamic routes with parameters
- Implementing shared layouts
- Organizing route groups
- Working with catch-all routes
Rule Categories by Priority
| Priority | Category | Impact | Prefix |
|---|---|---|---|
| 1 | File Naming | CRITICAL | routes-naming- |
| 2 | Page Routes | HIGH | routes-page- |
| 3 | API Routes | HIGH | routes-api- |
| 4 | Dynamic Routes | MEDIUM | routes-dynamic- |
| 5 | Layouts | MEDIUM | routes-layout- |
Quick Reference
1. File Naming (CRITICAL)
routes-naming-page- Use page.tsx for page componentsroutes-naming-route- Use route.ts for API handlersroutes-naming-layout- Use layout.tsx for shared layouts
2. Page Routes (HIGH)
routes-page-component- Export default function componentroutes-page-metadata- Export metadata object for SEO
What ships with it
6 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 · 123 lines · 58 tokens per session scan A 9ada30e37e7a
mandu-fs-routes is a skill published in the GitHub repository konamgil/mandu (46 stars, last pushed 15d ago), licensed MPL-2.0. It adds 58 tokens to every session and 886 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.
supabase-nextjs
Next.js with Supabase and Drizzle ORM.
design-patterns
Agents should invoke this skill when choosing patterns, designing traits/interfaces/components, deciding abstraction boundaries, evaluating dependency injection/callbacks, or comparing implementation approaches in Rust, TypeScript/React, or Django/Python.
api-design-patterns
Comprehensive API design patterns covering REST, GraphQL, gRPC, versioning, authentication, and modern API best practices.
tauri-django-react
Agents should invoke this skill for Tauri + Django + React desktop apps, especially backend lifecycle, CORS/auth, frontend integration, mandatory light/dark theming, German/English i18n, build packaging, dual desktop/web deployment, Rust commands, and platform-specific gotchas.
architecture-paradigm-client-server
Applies client-server architecture for web/mobile apps. Use when designing systems with centralized backend services, trust boundaries, or offline-first sync.