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/mtnyilmaz/agents/backend-developernpx skills add mtnyilmaz/agents --skill backend-developergit clone --depth 1 https://github.com/mtnyilmaz/agentsWhat 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.00048 | $0.01317 |
| Opus 5 | $0.00024 | $0.00659 |
| Sonnet 5 | $0.00010 | $0.00263 |
| Haiku 4.5 | $0.00005 | $0.00132 |
Grade A, and why
backend-developer 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend Developer
Expert in building production-grade backend APIs with the project's tech stack.
Layer References
Route→Service→Database architecture, tRPC router/service patterns, response format, and Zod schemas are covered in
layers/project/typescript/service-layer.mdandlayers/project/typescript/architecture.md. This skill adds the step-by-step new-feature guide, middleware order, and BullMQ patterns not found in layers.
Creating a New Domain Feature
Step 1: Zod Schema (shared)
// packages/utils/src/validation/schemas.ts
export const createProductSchema = z.object({
name: z.string().min(1),
price: z.number().positive(),
description: z.string().optional(),
});
Step 2: Service
// apps/api/src/services/product.service.ts
import { db } from "@repo/database";
import type { RequestContext } from "../context";
export const ProductService = {
async create(input: CreateProductInput, ctx: RequestContext) {
ctx.logger.info({ input }, "Creating product");
return db.product.create({ data: input });
},
async getById(id: string, ctx: RequestContext) {
const product = await db.product.findFirst({
where: { id, deletedAt: null },
});
if (!product) throw new AppError("NOT_FOUND", t("errors.product_not_found"), 404);
return product;
},
};
Step 3: tRPC Router
// apps/api/src/routes/product.router.ts
import { router, protectedProcedure } from "../trpc";
import { createProductSchema } from "@repo/utils/validation";
import { ProductService } from "../services/product.service";
export const productRouter = router({
create: protectedProcedure
.input(createProductSchema)
.mutation(({ input, ctx }) => ProductService.create(input, ctx)),
getById: protectedProcedure
.input(z.object({ id: z.string() }))
.query(({ input, ctx }) => ProductService.getById(input.id, ctx)),
});
Step 4: Register Router
// apps/api/src/routes/index.ts
export const appRouter = router({
auth: authRouter,
user: userRouter,
product: productRouter, // ← add here
});
What ships with it
1 file 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.
- 2d ago First seen · 189 lines · 48 tokens per session scan A cd70b0715205
backend-developer is a skill published in the GitHub repository mtnyilmaz/agents (6 stars, last pushed 3mo ago), licensed MIT. It adds 48 tokens to every session and 1,317 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-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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.