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 ErikaAX08/erikas-skills --skill backend-api-standardsgit clone --depth 1 https://github.com/ErikaAX08/erikas-skillsWrote 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/erikaax08/erikas-skills/backend-api-standards)<a href="https://agentmods.dev/skills/erikaax08/erikas-skills/backend-api-standards"><img src="https://agentmods.dev/badge/skills/erikaax08/erikas-skills/backend-api-standards/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/erikaax08/erikas-skills/backend-api-standards"><img src="https://agentmods.dev/badge/skills/erikaax08/erikas-skills/backend-api-standards.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.00061 | $0.04689 |
| Opus 5 | $0.00030 | $0.02344 |
| Sonnet 5 | $0.00012 | $0.00938 |
| Haiku 4.5 | $0.00006 | $0.00469 |
Grade A, and why
backend-api-standards 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 11d 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 — 579 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend API Standards Skill
This skill establishes mandatory standards for REST API contracts and data format. It defines what the API must return and how data must be shaped — it does not prescribe backend structure, folders, or implementation details.
When to Use This Skill
- When designing or documenting a new API endpoint
- When the user mentions "API", "endpoint", "REST", "response format"
- When defining request/response schemas or data models
- To ensure all APIs follow the same contract conventions
Core Standards
1. Unified Response Format
Every single API response MUST follow this exact structure:
{
"status": "success",
"message": "Human-readable description of the result",
"data": {},
"meta": null
}
Response Fields Specification
| Field | Type | Required | Description |
|---|---|---|---|
status |
"success" | "error" |
Always | Indicates if the request succeeded |
message |
string |
Always | Human-readable description |
data |
object | array | null |
Always | Response payload. Use null when there's no data to return |
meta |
object | null |
Always | Pagination, filters, or additional metadata. Use null when not needed |
Success Response Examples
Resource retrieved:
{
"status": "success",
"message": "Credit cards retrieved successfully.",
"data": [
{
"id": "01JQ5B3K7MNP9R8V2WX4Y6Z0A1",
"alias": "Mercado Pago",
"color": "#007bff",
"total_debt": "837.83",
"payment_due_day": 18,
"statement_close_day": 7,
"credit_limit": "2900.00",
"metadata": {},
"created_at": "2025-01-15T10:30:00Z",
"updated_at": "2025-01-15T10:30:00Z"
}
],
"meta": null
}
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.
- 11d ago First seen · 579 lines · 61 tokens per session scan A ef9a7027ae0e
backend-api-standards is a skill published in the GitHub repository ErikaAX08/erikas-skills (5 stars, last pushed 11d ago), licensed MIT. It adds 61 tokens to every session and 4,689 once invoked, about $0.0003 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
sdd-apply
Skill "sdd-apply" from Gentleman-Programming/gentle-ai, covering execution role, language domain contract, purpose, what you receive and execution and persistence contract.
n8n-architect
Use when the user explicitly wants to create, edit, validate, sync, or troubleshoot n8n workflows, asks about n8n nodes or automation, or wants to use n8n-as-code in the current context root.
bfl-api
BFL FLUX API integration guide covering endpoints, async polling patterns, rate limiting, error handling, webhooks, and regional endpoints with Python and TypeScript code examples.
api-doc-generator
Generate API documentation from source code, supporting REST APIs, GraphQL, and various documentation formats.
solr-extending
To build Solr plugins: SearchComponent, QParser, URP, DocTransformer.
api-aqa-flow
Workflow for backend API test automation: TMS / Issue Tracker test cases → automated API tests, HITL-gated.