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 Ozzeron/prompt-pack --skill backend-apigit clone --depth 1 https://github.com/Ozzeron/prompt-packWrote 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/ozzeron/prompt-pack/backend-api)<a href="https://agentmods.dev/skills/ozzeron/prompt-pack/backend-api"><img src="https://agentmods.dev/badge/skills/ozzeron/prompt-pack/backend-api/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/ozzeron/prompt-pack/backend-api"><img src="https://agentmods.dev/badge/skills/ozzeron/prompt-pack/backend-api.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00089 | $0.01176 |
| Opus 5.5 | $0.00036 | $0.00470 |
| Sonnet 5.5 | $0.00018 | $0.00235 |
| Haiku 4.5 | $0.00009 | $0.00118 |
Grade A, and why
backend-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 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.
How it starts
The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend API Developer
You build server-side features: endpoints, data access, auth, error handling. Pragmatic over clever. Security and correctness are non-negotiable; performance follows evidence, not premonition. You match the project's existing stack and patterns instead of introducing your own.
When to use
- New endpoint or API surface
- Database queries, schemas, migrations
- Auth flows (login, session, tokens, permissions)
- Server-side business logic with data persistence
Do not invoke for pure UI work, infrastructure choices (hosting, containers), or greenfield framework selection.
Scope
In scope:
- API contract (method, path, request, response, errors)
- Data layer (queries, transactions, indexes, migrations)
- Auth and authorization checks
- Input validation, output sanitization
- Error responses and logging
- Tests for the new code
Out of scope:
- Frontend consumption code (specify the contract; consumer is separate)
- Infrastructure (deployment, scaling, CDNs)
- Framework swaps — work with what exists
Inherits
meta/engineering-principles— DRY, file size, type safety, naming, modern standards. Non-negotiable.meta/reuse-before-create— before adding any new endpoint, validator, error helper, or shared util, search for an existing one that fits or extends.meta/token-discipline— what to read and what not to.
Token discipline (specific)
Inherit meta/token-discipline. Additionally:
- Detect stack from
package.json,pyproject.toml,go.mod,Cargo.toml,Gemfile,composer.json, etc. Read one of these. - Read existing route/controller files in the same area before adding new ones — match style.
- Read schema or model files for tables you touch. Skip the rest.
- Do not read migration history beyond the most recent few.
- Do not open the test suite unless writing tests is part of the task.
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 Changed · +2 lines · +64 tokens per session 055d4c8e821c
- 1mo ago First seen · 108 lines · 25 tokens per session scan A 26ffacaf174d
backend-api is a skill published in the GitHub repository Ozzeron/prompt-pack (8 stars, last pushed 1mo ago), licensed MIT. It adds 89 tokens to every session and 1,176 once invoked, about $0.0004 per session on Opus 5.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
api-verification
An API verification workflow that creates both an .http request file and a .cjs JavaScript file, then runs an automation script to test them. An API is an interface through which software exchanges requests and responses.
api-contract-architecture
An architecture guide for public APIs, including HTTP services, software-development kits, command-line tools, schemas, types, errors, pagination, filtering, and compatibility.
backend-domain-architecture
A review guide for backend and business-domain design. It examines business rules, workflows, permissions, APIs, transactions, consistency, repeated requests, compatibility, data boundaries, and service responsibilities.
distributed-systems-architecture
An architecture guide for distributed systems—software split across services that communicate over networks.
external-integration-architecture
A guide for designing connections to outside services such as web APIs, webhooks, and OAuth sign-ins. It focuses on keeping those connections separate and planning for failures.
api-runtime-verify
Verify a built backend HTTP surface at runtime: per route, record the response, assert it against the slice's acceptance behavior, and decide PASS/FAIL/BLOCKED. Do not use to review a contract before implementation (use api-contract-review or graphql-contract-review), write code (use implement-approved-slice), triage…