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 DataSQRL/sqrl --skill design-apigit clone --depth 1 https://github.com/DataSQRL/sqrlWrote 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/datasqrl/sqrl/design-api)<a href="https://agentmods.dev/skills/datasqrl/sqrl/design-api"><img src="https://agentmods.dev/badge/skills/datasqrl/sqrl/design-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/datasqrl/sqrl/design-api"><img src="https://agentmods.dev/badge/skills/datasqrl/sqrl/design-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.00046 | $0.01568 |
| Opus 5.5 | $0.00018 | $0.00627 |
| Sonnet 5.5 | $0.00009 | $0.00314 |
| Haiku 4.5 | $0.00005 | $0.00157 |
Grade A, and why
design-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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prefer designing the API implicitly by defining tables, functions, and relationships in SQRL that map to the desired API. After compiling, the generated API schema is found in build/inferred_schema.graphqls.
Only configure an explicit schema in the package.json configuration if:
- the schema needs to be static (e.g. to align with consumers of the API)
- the user wants to adjust the schema (e.g. introduce enums, add interfaces, remove fields, or rename/consolidate types)
Use the /configure-sqrl skill to configure the API, which protocols to expose, and how the exposed API endpoints are generated.
Key Concepts
DataSQRL generates APIs from SQRL scripts with support for GraphQL, REST, MCP, and Data Products.
Critical: GraphQL is the authoritative model. All API requests (REST, MCP) are executed by the GraphQL query engine.
SQRL to GraphQL Mapping
Tables/Functions → Endpoints:
- Default: Query endpoints (name and arguments match)
- With
SUBSCRIBE: Subscription endpoints. Before compiling any SUBSCRIBE statement, addkafkatoenabled-enginesin ALL package.json files. Omitting kafka produces BUILD SUCCESS but the Subscription type will be silently absent from the generated schema. CREATE TABLEwith+enginehint: Mutations (input excludes computed/metadata columns)
IMPORTANT: Only tables defined in the main script (or imported inline with IMPORT otherscript.*) are exposed in the API.
Schema Generation:
- Tables → GraphQL types (columns → fields, nested rows → child objects)
- Relationships → relationship fields on types
- Compiler infers base tables to avoid redundant result types
- Hidden columns (starting with
_) excluded from result types
Example:
Customer := SELECT customerId, email, name FROM RawCustomer WHERE email IS NOT NULL;
Maps to GraphQL query Customer: [Customer!]! with type containing the three fields.
Schema Customization (preserving object-relationship mapping):
- Change cardinalities, scalar types, mutation argument names, field types
- Add enums and interfaces
- Compiler validates compatibility with SQRL script(s)
What ships with it
2 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 · 136 lines · 46 tokens per session scan A 7c6ab7eadea7
design-api is a skill published in the GitHub repository DataSQRL/sqrl (230 stars, last pushed today), licensed Apache-2.0. It adds 46 tokens to every session and 1,568 once invoked, about $0.0002 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-09-30.
Other skills, from other repositories
grpc-expert
Expert-level gRPC, Protocol Buffers, microservices communication, and streaming. Use when the user mentions Protocol Buffers, microservices, RPC, or streaming, or when the task involves gRPC Fundamentals, Communication Patterns, or Production Features.
kafka-expert
Expert-level Apache Kafka, event streaming, Kafka Streams, and distributed messaging. Use when the user mentions streaming, messaging, event driven, or Kafka Streams.
openrouter
OpenRouter unified AI API - Access 200+ LLMs through single interface with intelligent routing, streaming, cost optimization, and model fallbacks.
llm-integration
Claude and OpenAI API patterns, prompt design, context management, streaming, tool use, cost control, multi-model routing.
fastapi-patterns
FastAPI production patterns — routing, dependency injection, background tasks, streaming, error handling, and async. Use when building or reviewing a FastAPI service.
gRPC Testing
You are an expert QA engineer specializing in grpc testing. When the user asks you to write, review, debug, or set up grpc related tests or configurations, follow these detailed instructions.