api-design-safety

api-design-safety is a skill for Claude Code from doccker/cc-use-exp. It costs 73 tokens per session (4,116 once invoked), scanned A, original, no licence file.

A set of rules for designing REST API responses and creating files such as Excel spreadsheets, CSV files, PDFs, and reconciliation reports.

In plain words
What is it for?
It is for reviewing API return values and downstream files so their required data stays correct and complete.
Why use it?
It helps prevent misplaced fields, unclear data types, and important fields being missing even when file generation appears to succeed.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the cc-use-exp plugin — 63 skills, 25 commands shipped together

Good fit It is for reviewing API return values and downstream files so their required data stays correct and complete.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/doccker/cc-use-exp/api-design-safety
Install

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.

Any agent
npx skills add doccker/cc-use-exp --skill api-design-safety
Clone the repo
git clone --depth 1 https://github.com/doccker/cc-use-exp

Made for: Claude Code.

Or install cc-use-exp, the plugin that ships this one along with the rest of its 63 skills, 25 commands.

Wrote 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.

agentmods badge for api-design-safety

README.md
[![agentmods](https://agentmods.dev/badge/skills/doccker/cc-use-exp/api-design-safety/github.svg)](https://agentmods.dev/skills/doccker/cc-use-exp/api-design-safety)
Your own site
<a href="https://agentmods.dev/skills/doccker/cc-use-exp/api-design-safety"><img src="https://agentmods.dev/badge/skills/doccker/cc-use-exp/api-design-safety/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.

agentmods 80×15 button for api-design-safety

Your own site · 80×15
<a href="https://agentmods.dev/skills/doccker/cc-use-exp/api-design-safety"><img src="https://agentmods.dev/badge/skills/doccker/cc-use-exp/api-design-safety.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 73 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,116 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00073 $0.04116
Opus 5.5 $0.00029 $0.01646
Sonnet 5.5 $0.00015 $0.00823
Haiku 4.5 $0.00007 $0.00412

Measured 1mo ago against content hash 2208c1af839e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

api-design-safety 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.

.antigravity/skills/api-design-safety/SKILL.md · 396 lines

The source is not reproduced here

A licence we could not identify

The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.

Read it on GitHub

Files

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.

Changes

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.

  1. 1mo ago First seen · 396 lines · 73 tokens per session scan A 2208c1af839e

Subscribe to this mod's changes

api-design-safety is a skill published in the GitHub repository doccker/cc-use-exp (1,064 stars, last pushed 1mo ago), with no licence file. It adds 73 tokens to every session and 4,116 once invoked, about $0.0003 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-30.

Related

Other skills, from other repositories

mantis-report

Generates a human-readable security review packet compiled from confirmed findings and exploit chains. Use at the end of a review cycle to produce stakeholder-facing documentation. Don't use for auditing code or verifying patches directly.

google/mantis · 44 tokens

ubiquitous-language

Maintain a project thesaurus (domain glossary) following DDD ubiquitous language principles. Use PROACTIVELY when naming anything: variables, functions, classes, modules, database fields, API endpoints, events, files, or directories. Also use when the user asks to "create thesaurus", "update glossary", "add term"…

CodeAlive-AI/ai-driven-development · 179 tokens

anthropic-api

Integrate the Anthropic Messages API with system prompts, tool calls, streaming, and client error handling.

alivirgo/Major-AI-Skills · 25 tokens

lanes-forms

Use when the user wants a form backend or contact form set up (a live POST endpoint that captures submissions and emails them), OR wants an agent to fill in / submit to a form on their behalf. Lanes Forms creates and manages hosted form endpoints from Claude Code. Triggers on "set up a contact form", "provision a…

lanes-sh/app · 105 tokens

apify-generate-output-schema

Generate output schemas (datasetschema.json, outputschema.json, keyvaluestoreschema.json) for an Apify Actor by analyzing its source code. Use when creating or updating Actor output schemas.

lingxling/awesome-skills-cn · 45 tokens

file-handling

File handling patterns — S3/R2/Vercel Blob storage, PDF generation, CSV/Excel import-export, file streaming, presigned URLs, multipart upload. Use when implementing file uploads to cloud storage, generating documents, processing large files, or building download endpoints.

PIXARTSeu/Synapse · 58 tokens