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 to-specgit 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/to-spec)<a href="https://agentmods.dev/skills/dds-solutions/ai-tadpole-os/to-spec"><img src="https://agentmods.dev/badge/skills/dds-solutions/ai-tadpole-os/to-spec/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/to-spec"><img src="https://agentmods.dev/badge/skills/dds-solutions/ai-tadpole-os/to-spec.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00022 | $0.00990 |
| Opus 5.5 | $0.00009 | $0.00396 |
| Sonnet 5.5 | $0.00004 | $0.00198 |
| Haiku 4.5 | $0.00002 | $0.00099 |
Grade A, and why
to-spec 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 12d 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 — 93 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 / to-spec
- Architecture:
@docs ARCHITECTURE:Documentation- Failure Path: Scope creep, ambiguous requirements, unversioned verbal contracts, or omitted boundary seams.
- Observability: Traceability via
execution/parity_guard.py([SKILL])
Conversation to Published Spec Protocol
Purpose: Convert informal discussions, requirements, or brainstorm outputs into formal, version-controlled specification files saved under
docs/specs/<feature-name>.md.
Workflow Bindings: Integrated directly into/brainstormand/plan.
🎯 Progressive Disclosure & L3 Reference Index
Read the core Sovereign rules below; consult deep L3 Reference Guides on demand:
| L3 Reference Guide | Purpose | Trigger / When to Load |
|---|---|---|
references/specification_schema_and_examples.md |
Standard specification templates, boundary seam schemas, and non-goal definitions | Drafting full architectural feature specifications |
scripts/spec_linter.py |
Automated static linter verifying required sections, FR/NFR IDs, and out-of-scope boundaries | Validating specification documents in docs/specs/ |
🧭 1. Canonical Specification Schema (docs/specs/<name>.md)
# Feature Specification: <Name>
## 1. Overview & Objective
<High-level summary of problem statement and business/technical objective>
## 2. Ubiquitous Domain Terminology
<Key domain terms mapped to CONTEXT.md / docs/GLOSSARY.md>
## 3. Functional Requirements
- **FR-1**: <Requirement description>
- **FR-2**: <Requirement description>
## 4. Non-Functional Requirements (NFRs)
- **NFR-1**: Performance / Latency bounds (< 200ms)
- **NFR-2**: Security & Permission constraints (SEC-03)
## 5. System Boundary & Seams
- **IPC / API Schema**: <Expected signatures, request/response models>
- **State Changes**: <Store mutations, database migrations>
## 6. Out of Scope (Non-Goals)
<Explicitly excluded capabilities to prevent scope creep>
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.
- 12d ago Changed · +46 lines 0579a048e3dc
- 1mo ago First seen · 47 lines · 22 tokens per session scan A 266973d6eb5a
to-spec is a skill published in the GitHub repository DDS-Solutions/AI-TadPole-OS (8 stars, last pushed today), licensed MIT. It adds 22 tokens to every session and 990 once invoked, about $0.0001 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-03.
Other skills, from other repositories
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.
react-query-setup
Set up @trpc/tanstack-react-query with createTRPCContext(), TRPCProvider, useTRPC() hook, queryOptions/mutationOptions factories, query invalidation via queryClient.invalidateQueries with queryFilter, and type inference with inferInput/inferOutput.
trpc-router
Entry point for all tRPC skills. Decision tree routing by task: initTRPC.create(), t.router(), t.procedure, createTRPCClient, adapters, subscriptions, React Query, Next.js, links, middleware, validators, error handling, caching, FormData.
migrate-oxlint
Guide for migrating a project from ESLint to Oxlint. Use when asked to migrate, convert, or switch a JavaScript/TypeScript project's linter from ESLint to Oxlint.
build-with-tinybase
Scaffold, extend, and verify reactive local-first JavaScript or TypeScript applications with TinyBase. Use when choosing TinyBase for in-memory tabular or key-value state, generating an app with create-tinybase, adding schemas or UI bindings, resolving TinyBase import paths, configuring browser or database…
beui-pro
Choose, inspect, install, and compose licensed beUI Pro premium React blocks through authenticated MCP or the shadcn registry. Use when building or improving landing pages with beUI Pro, installing @beui-pro items, selecting premium heroes, features, pricing, social proof, CTAs, navigation, footers, or other page…