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 DDS-Solutions/AI-TadPole-OS --skill api-patternsgit clone --depth 1 https://github.com/DDS-Solutions/AI-TadPole-OSWrote 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/dds-solutions/ai-tadpole-os/api-patterns)<a href="https://agentmods.dev/skills/dds-solutions/ai-tadpole-os/api-patterns"><img src="https://agentmods.dev/badge/skills/dds-solutions/ai-tadpole-os/api-patterns/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/dds-solutions/ai-tadpole-os/api-patterns"><img src="https://agentmods.dev/badge/skills/dds-solutions/ai-tadpole-os/api-patterns.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.00028 | $0.01367 |
| Opus 5.5 | $0.00011 | $0.00547 |
| Sonnet 5.5 | $0.00006 | $0.00273 |
| Haiku 4.5 | $0.00003 | $0.00137 |
Grade A, and why
api-patterns 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 3d 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.
This is a copy
72% identical to api-patterns — 138 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
[!IMPORTANT] AI Context & Knowledge Heritage
- Subsystem: Agent Skills Registry / api-patterns
- Architecture:
@docs ARCHITECTURE:Documentation- Failure Path: Information drift, legacy terminology, or documentation mismatch.
- Observability: Traceability via
execution/parity_guard.py([SKILL])
API Patterns — Architectural Engineering Standards
API design principles and decision-making. Learn to THINK: select the right architectural paradigm for the specific deployment topology.
🏛️ Tadpole OS Native API Architecture
In this codebase, API communication follows strict sovereign principles:
- Core Engine Gateway: High-performance Axum Rust router (server-rs/src/router.rs) handling
/v1/*routes. - Contract as Source of Truth: OpenAPI 3.1 specification maintained at docs/openapi.yaml verified by
execution/parity_guard.py. - Frontend Clients: Strictly typed services located in
src/services/*_api*.tsconsuming typed contracts. - Envelope Standard: Predictable JSON response envelopes (
success,data,error). - Auth Model: Bearer tokens (
ADMIN_TOKEN,NEURAL_TOKEN,OVERSIGHT_PUBLIC_KEY).
🎯 Progressive Disclosure & L3 Topic Index
Read REQUIRED core standards below; consult deep L3 Topic Guides on demand:
| Guide / Tool | Topic & Scope | Trigger / When to Read |
|---|---|---|
references/api-style.md |
REST vs GraphQL vs tRPC decision tree | Choosing API communication style |
references/rest.md |
Resource naming, HTTP verbs, status code selection | Designing REST endpoints |
references/response.md |
Envelope pattern, error schema, pagination strategies | Structuring payload contracts |
references/auth.md |
JWT, Bearer token, Passkey/WebAuthn, API keys | Authentication & session security |
references/versioning.md |
URI (/v1), Header, Query, sunset headers |
Planning API lifecycle & evolution |
references/rate-limiting.md |
Token bucket, sliding window, 429 Retry-After headers | Protecting APIs from abuse/overload |
references/documentation.md |
OpenAPI/Swagger best practices, schema components | Writing API specs & docs |
references/security-testing.md |
OWASP API Top 10, BOLA/IDOR, authz bypass checks | Pre-release security auditing |
references/graphql.md |
Schema design, depth/complexity limiting | When evaluating GraphQL queries |
references/trpc.md |
End-to-end TS monorepo type inference | When evaluating tRPC architectures |
scripts/api_validator.py |
Deterministic Axum and OpenAPI endpoint validator with --test suite |
Automated API audit or self-test verification |
What ships with it
11 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.
- references/api-style.md 1.5 KB
- references/auth.md 988 B
- references/documentation.md 961 B
- references/graphql.md 1.3 KB
- references/rate-limiting.md 1.1 KB
- references/response.md 1.3 KB
- references/rest.md 1.6 KB
- references/security-testing.md 3.2 KB
- references/trpc.md 1.2 KB
- references/versioning.md 1.1 KB
- scripts/api_validator.py 13 KB runs code
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.
- 3d ago Changed · +10 lines 0d7294aae3b6
- 1mo ago First seen · 88 lines · 28 tokens per session scan A edd76883e4b3
api-patterns is a skill published in the GitHub repository DDS-Solutions/AI-TadPole-OS (8 stars, last pushed 3d ago), licensed MIT. It adds 28 tokens to every session and 1,367 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 72% identical to api-patterns, differing in 138 lines, and is treated as a copy.
Other skills, from other repositories
nextjs-app-router
Full end-to-end tRPC setup for Next.js App Router. Covers route handler with fetchRequestHandler (GET + POST exports), TRPCProvider with QueryClientProvider, createTRPCOptionsProxy for RSC prefetching, HydrateClient/HydrationBoundary for hydration, useSuspenseQuery for Suspense, and server-side callers.
nextjs-pages-router
Set up tRPC in Next.js Pages Router with createNextApiHandler, createTRPCNext, withTRPC HOC, SSR via ssr option and ssrPrepass, SSG via createServerSideHelpers with getStaticProps, and server-side helpers for getServerSideProps prefetching.
server-setup
Initialize tRPC with initTRPC.create(), define routers with t.router(), create procedures with .query()/.mutation()/.subscription(), configure context with createContext(), export AppRouter type, merge routers with t.mergeRouters(), lazy-load routers with lazy().
subscriptions
Set up real-time event streams with async generator subscriptions using .subscription(async function() { yield }). SSE via httpSubscriptionLink is recommended over WebSocket. Use tracked(id, data) from @trpc/server for reconnection recovery with lastEventId. WebSocket via wsLink and createWSClient from @trpc/client…
client-setup
Create a vanilla tRPC client with createTRPCClient (), configure link chain with httpBatchLink/httpLink, dynamic headers for auth, transformer on links (not client constructor). Infer types with inferRouterInputs and inferRouterOutputs. AbortController signal support. TRPCClientError typing.
links
Configure the tRPC client link chain: httpLink, httpBatchLink, httpBatchStreamLink, splitLink, loggerLink, wsLink, createWSClient, httpSubscriptionLink, unstablelocalLink, retryLink. Choose the right terminating link. Route subscriptions via splitLink. Build custom links for SOA routing. Link options: url, headers…