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 prototypegit 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/prototype)<a href="https://agentmods.dev/skills/dds-solutions/ai-tadpole-os/prototype"><img src="https://agentmods.dev/badge/skills/dds-solutions/ai-tadpole-os/prototype/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/prototype"><img src="https://agentmods.dev/badge/skills/dds-solutions/ai-tadpole-os/prototype.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.00030 | $0.01060 |
| Opus 5.5 | $0.00012 | $0.00424 |
| Sonnet 5.5 | $0.00006 | $0.00212 |
| Haiku 4.5 | $0.00003 | $0.00106 |
Grade A, and why
prototype 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 9d 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 — 79 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 / prototype
- Architecture:
@docs ARCHITECTURE:Documentation- Failure Path: Committing ephemeral prototype spikes to production directories or over-engineering preliminary spikes.
- Observability: Traceability via
execution/parity_guard.py([SKILL])
Executable Spiking & UX Prototyping
Purpose: Raise discussion fidelity and resolve design ambiguities by constructing cheap, minimal, isolated executable prototypes in
.tmp/prototypes/before committing production code.
Workflow Bindings: Integrated into/create,/brainstorm, and/ui-ux-pro-max.
🎯 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/spike_scaffolds_and_sandbox.md |
Single-file HTML/CSS/JS templates, event listeners, and sandbox lifecycle | Scaffolding new interaction spikes |
scripts/prototype_scaffolder.py |
Automated prototype spike scaffolder and entry point validator | Generating .tmp/prototypes/<name> sandboxes |
🔄 1. The 4-Phase Prototyping Protocol
[1. UNCERTAINTY] ───> [2. SCAFFOLD] ───> [3. DEMO] ───> [4. PRODUCTION]
Identify look vs. Generate minimal Demonstrate to Transfer lessons
behavior question spike in .tmp/ user & lock in into /plan & delete
- Identify the Core Uncertainty: Determine whether the unknown is visual layout ("how should it look") or reactive state ("how should it behave").
- Build Minimal Executable Spike: Scaffolding runs exclusively under
.tmp/prototypes/<name>/. Avoid production database dependencies or heavy stylesheets. - Verify with User: Demonstrate interaction or layout to lock in architectural and design choices.
- Transition to Production: Extract proven patterns into
/planand purge ephemeral prototype files.
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.
- 9d ago Changed · +47 lines c5fc558de22f
- 1mo ago First seen · 32 lines · 30 tokens per session scan A 4d318b6c3c26
prototype is a skill published in the GitHub repository DDS-Solutions/AI-TadPole-OS (8 stars, last pushed 5d ago), licensed MIT. It adds 30 tokens to every session and 1,060 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
magic-ui
Use this skill when users want to add, customize, or troubleshoot Magic UI components in React/Next.js projects. It covers component selection, shadcn registry installation (@magicui/), integration patterns, and practical quality checks for accessibility and maintainability.
building-canvases
Create or edit a PostHog freeform canvas — a sandboxed browser application (data board, document, form, small tool, graphics experiment) stored in PostHog and rendered by the desktop/web app. Use when a task asks to build, generate, update, or fix a standalone canvas app, or when a freeform canvas id is given as the…
composing-grid-canvases
Compose PostHog grid canvases — widget grids (including the user's home canvas) built from reusable component canvases. Use when a task asks to add, fill, move, resize, or remove a widget on a grid or home canvas, to compose a whole canvas of widgets from one ask, to build a reusable widget/component, or when a…
styling-sidebar-products
How products and pages appear in the PostHog sidebar: which category they sit in, which icon and color they get, and which groups share a color gradient. Use when adding a product or data management page to the sidebar (treeItemsProducts or treeItemsMetadata in a products//manifest.tsx), giving an entry a new icon or…
visualizing-change-over-time
Helps PostHog engineers and agents pick the right chart when a request is about visualizing change over time, before/after comparisons, or period-over-period movement while building UI with @posthog/quill-charts (dashboards, reports, the mcpanalytics frontend, custom visualizations). Use when a user asks how something…
quill-code
Edit the @posthog/quill design system locally and consume the change in products/desktop before it is published to npm. Use when changing quill components/primitives/tokens, when a quill change must be tested inside the Code app, or when the user mentions quill, the design system, the .local-quill tarball, or the…