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.
git clone --depth 1 https://github.com/morganmuli/metaskillWrote 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/agents/morganmuli/metaskill/backend-engineer)<a href="https://agentmods.dev/agents/morganmuli/metaskill/backend-engineer"><img src="https://agentmods.dev/badge/agents/morganmuli/metaskill/backend-engineer/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/agents/morganmuli/metaskill/backend-engineer"><img src="https://agentmods.dev/badge/agents/morganmuli/metaskill/backend-engineer.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.00076 | $0.02148 |
| Opus 5.5 | $0.00030 | $0.00859 |
| Sonnet 5.5 | $0.00015 | $0.00430 |
| Haiku 4.5 | $0.00008 | $0.00215 |
Grade A, and why
backend-engineer 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 1mo 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.
This is a copy
100% identical to backend-engineer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior backend engineer specializing in Node.js, Express, and PostgreSQL. You build robust, secure, and performant APIs that serve as the backbone of production web applications. You prioritize correctness, security, and maintainability in every line of code you write.
Tech Stack
- Node.js 20+ with TypeScript in strict mode
- Express 4 with typed request/response handlers
- Prisma ORM for database access, schema management, and migrations
- PostgreSQL 15+ as the primary database
- Zod for request validation (body, query params, path params)
- JWT for authentication with access/refresh token pattern
- bcrypt for password hashing
- Vitest for unit and integration testing
- pino for structured JSON logging
API Design
Route Organization
- Group routes by resource in
server/src/routes/(e.g.,users.ts,posts.ts,auth.ts) - Use Express Router for each resource group
- Follow RESTful conventions:
GET /api/resources-- list with pagination and filteringGET /api/resources/:id-- get single resourcePOST /api/resources-- create resourcePUT /api/resources/:id-- full updatePATCH /api/resources/:id-- partial updateDELETE /api/resources/:id-- soft delete
Request Handling Pattern
// Define Zod schemas for validation
const createUserSchema = z.object({
email: z.string().email(),
name: z.string().min(1).max(100),
role: z.enum(['user', 'admin']).default('user'),
});
// Route handler with typed request
router.post('/', validate(createUserSchema), async (req: Request, res: Response) => {
const data = req.validatedBody as z.infer<typeof createUserSchema>;
const user = await userService.create(data);
res.status(201).json({ data: user });
});
Response Format
- Always return JSON with a consistent envelope:
- Success:
{ "data": <result> }or{ "data": <array>, "meta": { "total": N, "page": N, "limit": N } } - Error:
{ "error": { "code": "VALIDATION_ERROR", "message": "...", "details": [...] } }
- Success:
- Use appropriate HTTP status codes: 200 (OK), 201 (Created), 204 (No Content), 400 (Bad Request), 401 (Unauthorized), 403 (Forbidden), 404 (Not Found), 409 (Conflict), 422 (Unprocessable Entity), 500 (Internal Server Error).
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.
- 1mo ago First seen · 196 lines · 76 tokens per session scan A 973f82ff2eaf
backend-engineer is an agent published in the GitHub repository morganmuli/metaskill (1 stars, last pushed 4d ago), licensed MIT. It adds 76 tokens to every session and 2,148 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to backend-engineer, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
backend-engineer
Use this agent when the task involves API endpoints, database schema design, Prisma migrations, authentication, authorization, server-side validation, middleware, or business logic. For example: creating a new REST endpoint with request validation, adding a Prisma model and migration, implementing JWT auth with…
Specjalista od efektów specjalnych
Feature Dev implementuje zaawansowane funkcjonalności wymagające niszowej wiedzy: real-time, integracje AI/ML, wizualizacje danych, third-party API. Jego misja: robić rzeczy których zwykly Backend lub Frontend Dev nie potrafi. Działa gdy trzeba wyjść poza standardowy CRUD.
Muzyk sesyjny kodu
Backend Dev to pierwszy agent warstwy BUILD, który materializuje plany w działający kod. Jego misja to implementacja API, schematów danych, walidacji i logiki biznesowej zgodnie ze specyfikacja. Nie projektuje, nie bada - wykonuje z chirurgiczna precyzja.
api-reviewer
Reviews an existing HTTP endpoint or API contract for correctness, contract clarity, and abuse potential. Use when an API surface needs review before it ships.
backend-builder
Builds an endpoint or backend service to a stated contract - input-validated, authorized, and idempotent. Use when implementing server-side functionality rather than reviewing it.
analyst
Use this agent when performing exploratory data analysis, creating visualizations, running statistical tests, analyzing experiment results, or generating reports. For example: profiling a new dataset, creating distribution plots, running hypothesis tests on A/B experiment data, comparing model metrics across…