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/ozzeron/prompt-pack/backend-apinpx 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.svg" alt="Measured on agentmods" 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 | $0.00025 | $0.01115 |
| Opus 5 | $0.00013 | $0.00558 |
| Sonnet 5 | $0.00005 | $0.00223 |
| Haiku 4.5 | $0.00003 | $0.00112 |
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 5d 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 — 108 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.
- 5d 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 25 tokens to every session and 1,115 once invoked, about $0.0001 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
chinese-git-workflow
国内 Git 平台配置参考——Gitee、Coding.net、极狐 GitLab、CNB 的 SSH/HTTPS/凭据/CI 接入差异与镜像同步配置。仅在用户显式 /chinese-git-workflow 时调用，不要根据上下文自动触发。.
chinese-documentation
中文文档排版参考——中英文空格、全半角标点、术语保留、链接格式、中文文案排版指北约定。仅在用户显式 /chinese-documentation 时调用，不要根据上下文自动触发。.
memorix-troubleshooting
Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.
ijfw-workflow
Use when the user says: 'build', 'create', 'plan', 'new project', 'brainstorm', 'design', 'UI', 'website', 'dashboard', 'app', 'help me build', 'launch', 'book', 'campaign', or anything project-level. Skill body decides Quick vs Deep path.
ijfw-plan
Use when the user says 'plan this', 'plan it', 'make a plan', 'let's plan', 'draft a plan', 'how should we tackle this', 'break this down', or invokes '/ijfw-plan'. Produces a falsifiable PLAN.md (software, book, campaign, design, research) with task breakdown, dependency wave-table, and success criteria — gated by…
ijfw-writing-skills
Authoring discipline for new IJFW skills. Use when creating a new skill, writing a skill, making a skill that does X, or asked to add a skill. Trigger: create a new skill, write a skill, new skill, make me a skill, skill that does, /ijfw-writing-skills.