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 agentmods add skills/agentic-development/adev-plugin/prototypenpx skills add agentic-development/adev-plugin --skill prototypegit clone --depth 1 https://github.com/agentic-development/adev-pluginWhat 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 | $0.00144 | $0.05356 |
| Opus 5 | $0.00072 | $0.02678 |
| Sonnet 5 | $0.00029 | $0.01071 |
| Haiku 4.5 | $0.00014 | $0.00536 |
Grade A, and why
adev: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 2d 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 — 471 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prototype a Feature
Generate tiered prototypes (wireframe, mockup, functional) from a Feature Charter, serve them via localhost for browser preview, iterate on conversational feedback, and persist or discard the result.
Arguments
--module <name>: Module name. Locates charter at.context-index/specs/features/<name>/charter.md. Required when invoked standalone.--tier <wireframe|mockup|functional>: Pre-select tier (skips interactive prompt).--framework <react|vue|svelte|vanilla>: Pre-select framework for functional tier (skips interactive prompt).
When invoked from /adev:brainstorm, the module name and approach context are passed automatically.
Prerequisites
- Context Index.
.context-index/must exist withconstitution.md. If missing, tell the user to run/adev:initfirst. - Charter. A charter must exist at
.context-index/specs/features/<module>/charter.md. If missing:No charter found at
.context-index/specs/features/<module>/charter.md. Run/adev:brainstormfirst. - Node.js runtime. Required for the HTTP server helper.
Process
Brainstorm Context Reception
If brainstorm context is provided (a BRAINSTORM_CONTEXT block), skip Step 0 entirely and proceed directly to Step 1 with the provided context:
moduleis used directly — no charter discovery needed, no--moduleargument requiredapproach_summaryis used to seed the initial prototype generation — it guides what the prototype demonstrates and what design direction to exploreplatform_contextsets framework defaults for the functional tier (e.g., if platform context specifies React, pre-select React as the framework)constitution_constraintsare used to validate generated prototype code against constitutional principles
When brainstorm context is present, skip the charter lookup in Step 0 entirely — the brainstorm already loaded the charter and extracted the relevant context.
Error handling: If brainstorm context is provided but missing required fields (module or approach_summary), report an error and stop. Error code: INCOMPLETE_CONTEXT.
What ships with it
1 file 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.
- 2d ago First seen · 471 lines · 144 tokens per session scan A 9105fcf5eeca
adev:prototype is a skill published in the GitHub repository agentic-development/adev-plugin (11 stars, last pushed 2d ago), licensed MIT. It adds 144 tokens to every session and 5,356 once invoked, about $0.0007 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-30.
Other skills, from other repositories
general-video
Author or edit a custom HyperFrames composition when no specialized workflow fits, or when BRIEF.md sets flow: companion. Use for longer or multi-scene pieces, brand and sizzle reels, montages, static loops, static title cards, footage remixes, and freeform builds. Use motion-graphics instead for a short unnarrated…
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
mintlify-preview
Run the public Mintlify product docs site locally for live preview. Use when previewing or iterating on docs under docs/ (.mdx/.md pages, docs.json nav), or when the user says "start the docs", "run mintlify", "preview the docs site".