Borrowing it
Nothing to install: this file belongs to TEAM-DONGCHIMI/DONGCHIMI-CLIENT. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/TEAM-DONGCHIMI/DONGCHIMI-CLIENT/develop/.agents/skills/verify-route-boundaries/SKILL.mdgit clone --depth 1 https://github.com/TEAM-DONGCHIMI/DONGCHIMI-CLIENTWrote 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/team-dongchimi/dongchimi-client/verify-route-boundaries)<a href="https://agentmods.dev/skills/team-dongchimi/dongchimi-client/verify-route-boundaries"><img src="https://agentmods.dev/badge/skills/team-dongchimi/dongchimi-client/verify-route-boundaries/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/team-dongchimi/dongchimi-client/verify-route-boundaries"><img src="https://agentmods.dev/badge/skills/team-dongchimi/dongchimi-client/verify-route-boundaries.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00026 | $0.00711 |
| Opus 5 | $0.00013 | $0.00356 |
| Sonnet 5 | $0.00005 | $0.00142 |
| Haiku 4.5 | $0.00003 | $0.00071 |
Grade A, and why
verify-route-boundaries 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 90 lines · 26 tokens per session scan A 10fd28e00a8e
verify-route-boundaries is a skill published in the GitHub repository TEAM-DONGCHIMI/DONGCHIMI-CLIENT (11 stars, last pushed 1mo ago), with no licence file. It adds 26 tokens to every session and 711 once invoked, about $0.0001 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
spotpatch
A development workflow for React that connects a selected page element to its JSX or TSX source code and gathers context for review.
figma-fetch
Extract frame/component structure and all visible text from a Figma design URL. Use whenever a prompt or a fetched issue contains a figma.com/design or figma.com/file link.
next-application-structure
Establishes or reviews directory layout, server/client boundaries, routing, data-fetching strategy, and testing structure for Next.js 14+ App Router TypeScript applications. Invoked when the user asks to structure a Next app, set App Router conventions, or review architecture for React parity.
e2e-generate
Create or update end-to-end tests for a user-facing flow that changed, using whatever e2e framework the repo already uses. Use after implementing a user story that alters UI behavior, routing, forms, or API-driven views.
Component Test Scaffold (Next.js)
Generate React/Next.js component test skeletons (RTL) from specifications.
fe-spec
Converts requirements for a new frontend feature into a structured spec. Use when: before starting a new feature, when feature.md needs to be written, or when converting a planning doc into a dev spec. Do NOT load for: bug fixes, refactoring, simple style changes.