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 agentmods add skills/casemark/casedotdev-starter-app/apinpx skills add CaseMark/casedotdev-starter-app --skill apigit clone --depth 1 https://github.com/CaseMark/casedotdev-starter-appWhat 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 | $0.00000 | $0.02613 |
| Opus 5 | $0.00000 | $0.01307 |
| Sonnet 5 | $0.00000 | $0.00523 |
| Haiku 4.5 | $0.00000 | $0.00261 |
Grade A, and why
api 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 2d 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 — 458 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Routes Skill
Purpose
This skill covers creating and working with API routes in Next.js 15+, including REST endpoints, server actions, and data fetching patterns.
Key Concepts
- Route Handlers: API endpoints in the
app/api/directory - Server Actions: Server-side functions that can be called from client components
- Server Components: Can fetch data directly without API routes
- Edge Runtime: Optional edge runtime for global performance
Route Handlers
Basic GET Endpoint
// app/api/cases/route.ts
import { NextResponse } from 'next/server';
export async function GET() {
const cases = await getCases(); // Your data fetching logic
return NextResponse.json(cases);
}
POST Endpoint
// app/api/cases/route.ts
import { NextResponse } from 'next/server';
import type { NextRequest } from 'next/server';
export async function POST(request: NextRequest) {
try {
const body = await request.json();
// Validate the input
if (!body.title) {
return NextResponse.json(
{ error: 'Title is required' },
{ status: 400 }
);
}
const newCase = await createCase(body);
return NextResponse.json(newCase, { status: 201 });
} catch (error) {
return NextResponse.json(
{ error: 'Internal server error' },
{ status: 500 }
);
}
}
Dynamic Route Handler
// app/api/cases/[id]/route.ts
import { NextResponse } from 'next/server';
interface RouteContext {
params: Promise<{ id: string }>;
}
export async function GET(
request: Request,
context: RouteContext
) {
const { id } = await context.params;
const caseData = await getCaseById(id);
if (!caseData) {
return NextResponse.json(
{ error: 'Case not found' },
{ status: 404 }
);
}
return NextResponse.json(caseData);
}
export async function PATCH(
request: Request,
context: RouteContext
) {
const { id } = await context.params;
const body = await request.json();
const updated = await updateCase(id, body);
return NextResponse.json(updated);
}
export async function DELETE(
request: Request,
context: RouteContext
) {
const { id } = await context.params;
await deleteCase(id);
return NextResponse.json({ success: true });
}
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.
- 2d ago First seen · 458 lines · 0 tokens per session scan A 87feea6f2aae
api is a skill published in the GitHub repository CaseMark/casedotdev-starter-app (2 stars, last pushed 2mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,613 tokens. 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…