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 reganomalley/claudia --skill claudia-apigit clone --depth 1 https://github.com/reganomalley/claudiaWrote 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/reganomalley/claudia/claudia-api)<a href="https://agentmods.dev/skills/reganomalley/claudia/claudia-api"><img src="https://agentmods.dev/badge/skills/reganomalley/claudia/claudia-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/reganomalley/claudia/claudia-api"><img src="https://agentmods.dev/badge/skills/reganomalley/claudia/claudia-api.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.00105 | $0.00991 |
| Opus 5 | $0.00053 | $0.00495 |
| Sonnet 5 | $0.00021 | $0.00198 |
| Haiku 4.5 | $0.00011 | $0.00099 |
Grade A, and why
claudia-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 10d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claudia API Design Domain
Overview
Most APIs should be REST. GraphQL and gRPC solve specific problems -- if you don't have those problems, the added complexity isn't worth it. tRPC is a shortcut for TypeScript fullstack apps, not an architecture for the ages.
Pick the simplest style that fits your actual constraints. You can always add complexity later; removing it is much harder.
API Style Decision Tree
What are you building?
├── Internal service-to-service communication
│ ├── High throughput / streaming needed → gRPC
│ └── Simple request/response → REST (internal) or gRPC
├── TypeScript fullstack (Next.js, Remix, shared codebase)
│ └── tRPC (outgrow it when you need non-TS clients)
├── Mobile app with varied data needs
│ ├── Many different screens, each needing different data shapes → GraphQL
│ └── Straightforward CRUD → REST
├── Public API for third parties
│ └── REST (it's what everyone expects)
├── Browser SPA + backend
│ ├── Shared TypeScript → tRPC
│ └── Otherwise → REST
└── Not sure
└── REST (you can always add GraphQL later)
Quick Comparison
| REST | GraphQL | gRPC | tRPC | |
|---|---|---|---|---|
| Strengths | Universal, cacheable, simple tooling | Flexible queries, one endpoint, typed schema | Fast (protobuf), streaming, polyglot | Zero boilerplate, end-to-end type safety |
| Weaknesses | Over/under-fetching, many endpoints | Caching is hard, N+1 queries, complexity | No browser support (needs proxy), steep learning curve | TypeScript only, tight client-server coupling |
| Best for | Public APIs, most web apps, CRUD | Mobile apps, complex nested data, varied clients | Microservices, high throughput, streaming | TS fullstack apps, prototypes, internal tools |
| Avoid when | You need real-time streaming | Small teams, simple CRUD, caching matters | Browser-facing APIs, small projects | Non-TS clients exist or will exist |
REST Design Principles (The Short Version)
- Nouns, not verbs:
/users/:id/posts, not/getUserPosts - Plural resources:
/users, not/user - HTTP methods do the verb work: GET reads, POST creates, PUT replaces, PATCH updates, DELETE removes
- Status codes mean things: Don't return 200 with
{ "error": true }-- use proper HTTP status codes - Consistent naming: Pick
snake_caseorcamelCaseand stick with it everywhere
What ships with it
3 files 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.
- 10d ago First seen · 95 lines · 105 tokens per session scan A b16265216154
claudia-api is a skill published in the GitHub repository reganomalley/claudia (4 stars, last pushed 6mo ago), licensed MIT. It adds 105 tokens to every session and 991 once invoked, about $0.0005 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
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
agui-dotnet-protobuf
Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
fastapi-router-py
Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.
migrate-segw-to-rap
Reverse-engineer a SEGW-built OData V2 service (MPC/DPC/MPCEXT/DPCEXT) into a modern RAP V4 service — tables, CDS views (interface + projection), behavior definitions, draft entities, service definition + binding. Use when asked to "migrate this SEGW service to RAP", "convert OData V2 to V4 RAP", "modernize this…
telnyx-messaging-hosted-curl
Set up hosted SMS numbers, toll-free verification, and RCS messaging. Use when migrating numbers or enabling rich messaging features. This skill provides REST API (curl) examples.