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 toffyui/ccteams --skill next-ts-playbookgit clone --depth 1 https://github.com/toffyui/ccteamsWrote 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/toffyui/ccteams/next-ts-playbook)<a href="https://agentmods.dev/skills/toffyui/ccteams/next-ts-playbook"><img src="https://agentmods.dev/badge/skills/toffyui/ccteams/next-ts-playbook/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/toffyui/ccteams/next-ts-playbook"><img src="https://agentmods.dev/badge/skills/toffyui/ccteams/next-ts-playbook.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 MCP Rug Pull · line 187 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00049 | $0.03408 |
| Opus 5 | $0.00024 | $0.01704 |
| Sonnet 5 | $0.00010 | $0.00682 |
| Haiku 4.5 | $0.00005 | $0.00341 |
Grade A, and why
next-ts-playbook 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 10d 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 — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Next.js App Router Playbook
This is the literal procedure to follow for any change in a Next.js (App Router)
- TypeScript + Tailwind project. The single most expensive class of mistake in this stack is putting code on the wrong side of the server/client boundary — so the loop forces you to locate that boundary before you write anything.
Operating loop
- Pin the versions before anything else. Read
package.jsonfor thenextandreactversions and skimnext.config.(js|mjs|ts)for redirects, rewrites,images.remotePatterns, and experimental flags. Caching defaults flipped between majors (see decision tree C) — advice that is correct for 14 is wrong for 15. - Map the route segment. For the route you're touching, list which of
page.tsx,layout.tsx,loading.tsx,error.tsx,not-found.tsx,route.tsexist (ls app/<segment>/). Aroute.tsand apage.tsxcannot coexist in the same segment. Note whetherloading.tsx/error.tsxare missing — async pages without them hang blank or crash the segment. - Locate the change on the RSC/client boundary. Before writing, record
the baseline:
grep -rn '"use client"' app/ src/ 2>/dev/null | wc -l. Decide which side your change lives on using decision tree A. Every"use client"you add must be justified in your report. - Read two sibling files (a neighboring page and a neighboring component) and mirror their naming, import style, and data-fetching pattern. Do not introduce a second convention.
- Data on the server. Initial data is fetched in the Server Component
with
async/await. Mutations go through Server Actions that (a) validate their input and (b) callrevalidatePath/revalidateTag.useEffectfetching is only for data that genuinely depends on client-only state. - Write cache intent explicitly. Every
fetchfor data that matters carries{ cache: 'force-cache' | 'no-store' }ornext: { revalidate: N }— never rely on the default, because the default changed between Next 14 and 15. - Type the boundaries. Props, Server Action inputs, and route-handler
payloads get explicit types. External input (
searchParams,FormData, fetched JSON) is narrowed or zod-parsed, never cast. - Run the verification recipe (below) and report real output.
next buildis part of it — it statically catches boundary violations thattsccannot.
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.
- 10d ago First seen · 228 lines · 49 tokens per session scan A 34d66e0ae836
next-ts-playbook is a skill published in the GitHub repository toffyui/ccteams (48 stars, last pushed 9d ago), licensed MIT. It adds 49 tokens to every session and 3,408 once invoked, about $0.0002 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
frontend-conventions
Coding conventions, architecture patterns, and testing rules for the SkillHub React frontend. Ensures agents follow Feature-Sliced Design and use the generated OpenAPI types.
fast-typescript-check
Keep www-sacred's TypeScript fast to type-check and fast to run. Use when touching the ASCII/canvas animation components (the only real per-frame code here), tightening type-check wall-clock, or auditing a change for runtime or compiler regressions. Scoped to this repo — a React 19 / Next.js 16 component library plus…
typescript-react
Apply, review, and explain React conventions from the TypeScript Style Guide. Use automatically for TypeScript and TSX tasks involving prop-derived state, prop typing, component responsibilities, data flow, compound components, or client and server state.
electron-dev
Electron desktop apps with React, TypeScript, and Vite. Use for IPC, window/tray, PTY terminals, WebRTC, and packaging.
coding-standards
A set of general coding standards and practical patterns for TypeScript, JavaScript, React, and Node.js. It covers readable naming, simple designs, avoiding repetition, and delaying unnecessary features.
typescript-rules
React/TypeScript frontend development rules including type safety, component design, state management, and error handling. Use when implementing React components, TypeScript code, or frontend features.