prototype

A throwaway-code tool for testing an uncertain technical approach before committing to a full implementation. It can explore either program logic or different user-interface designs.

In plain words
What is it for?
Use it to try a state machine, algorithm, data model, or several UI concepts with temporary code.
Why use it?
It provides quick feedback when the right algorithm, data model, layout, or interaction is not yet clear.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/datit309/supergraph/prototype
Any agent
npx skills add datit309/supergraph --skill prototype
Clone the repo
git clone --depth 1 https://github.com/datit309/supergraph

Made for: Claude Code, Codex.

Per session 62 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 982 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00062 $0.00982
Opus 5 $0.00031 $0.00491
Sonnet 5 $0.00012 $0.00196
Haiku 4.5 $0.00006 $0.00098

Measured yesterday against content hash b45166b8078f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

plugins/supergraph/skills/prototype/SKILL.md · 137 lines

How it starts

The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/supergraph:prototype

Throwaway code to validate approach. Explore fast, decide, then delete or integrate.

Announce: "🧪 /supergraph:prototype — building throwaway prototype..."

When to Use

  • Between /supergraph:analyze and /supergraph:plan when approach is uncertain
  • Multiple valid UI designs need visual comparison
  • Core logic (state machine, algorithm, data model) needs validation before full TDD
  • User says "I'm not sure which approach" or "can we try both?"

Choose Branch

Ask user (or infer from task):

Logic branch — validate state, algorithm, or data model
UI branch — validate layout, interaction, or multiple designs


Logic Branch

Goal: validate core logic in a minimal terminal program.

Rules:

  • Single file (prototype-<slug>.ts / .py / etc.)
  • No database, no HTTP, no external services — in-memory only
  • No tests — feedback is the running output
  • Single command to run: npx ts-node prototype-<slug>.ts or equivalent
  • Hard-code sample data

Structure (TypeScript example):

// prototype-<slug>.ts — THROWAWAY, do not review
type State = "idle" | "processing" | "done" | "error"
type Event = { type: "start" } | { type: "finish" } | { type: "fail" }

function transition(state: State, event: Event): State {
  // ...
}

// Run through sample cases
const cases = [ ... ]
cases.forEach(({ from, event, expected }) => {
  const result = transition(from, event)
  console.log(result === expected ? "✅" : "❌", { from, event, result, expected })
})

Run and observe:

npx ts-node prototype-<slug>.ts

UI Branch

Goal: compare multiple visual/interaction designs without committing.

Rules:

  • All designs live on ONE route: /prototype/<slug>
  • URL param ?design=A|B|C switches between designs
  • Floating control bar (fixed position) lets user switch designs visually
  • No persistence layer — mock data only
  • No auth, no real API calls
  • Single command to start: npm run dev (or project equivalent)

Structure:

app/prototype/<slug>/page.tsx   (router + floating switcher)
app/prototype/<slug>/DesignA.tsx
app/prototype/<slug>/DesignB.tsx
app/prototype/<slug>/DesignC.tsx

Read the full file on GitHub · 137 lines

Changes

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.

  1. yesterday First seen · 137 lines · 62 tokens per session scan A b45166b8078f

Subscribe to this mod's changes

prototype is a skill published in the GitHub repository datit309/supergraph (21 stars, last pushed 4d ago), licensed MIT. It adds 62 tokens to every session and 982 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

playwright-cli

Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…

testdino-hq/playwright-skill · 64 tokens

migrate

Inventory an existing spec-driven project and apply bounded migrations to jig defaults: report, adopt-layout, rename-decisions, split-slices, slice-to-spec, seed-decisions, and copy-machinery. Use when the user says migrate this project to jig, adopt jig here, this repo already has specs — set up jig, scaffold-init…

ramboz/jig · 151 tokens

adr-workflow

Scaffold, accept, index, and link Architectural Decision Records (ADRs). Use when the user says "write an ADR", "record this decision", "resolve [deferred item] with an ADR", "supersede ADR-NNNN", or otherwise wants to capture a hard-to-reverse decision in docs/decisions/. Also use when a refinement-todo entry needs…

ramboz/jig · 122 tokens

bug-fix

Drive the teeth-gated lifecycle for reported defects: diagnose root cause, prove it, and prevent regression through REPORTED → DIAGNOSING → ROOTCAUSED → FIXING → REVIEWED → DONE, with VERIFIED, ESCALATED, and RESOLVEDONMAIN paths where needed. Auto-fires on fix this bug, debug this, root-cause this, this regressed…

ramboz/jig · 208 tokens

analyze

Cross-artifact consistency report for jig specs — a non-destructive six-category audit at CRITICAL/HIGH/MEDIUM/LOW severity, covering duplication, ambiguity, underspecification, principle violations, coverage gaps, and terminology drift. Auto-triggers when you say analyze this spec, check for inconsistencies, audit…

ramboz/jig · 160 tokens

arch-review

Team baseline for architecture, design-doc, and RFC review — produces summary, strengths, concerns, and open questions. Auto-triggers when you say review this design, review this architecture, review this proposal, review my RFC, poke holes in this proposal, is this design sound, or critique this tech spec. Defers to…

ramboz/jig · 207 tokens