prototype

A throwaway prototype built to answer one design question quickly. It can test whether a logic or state model feels right, or show several possible versions of a user interface.

In plain words
What is it for?
Use it to explore a backend state model or UI idea with a small runnable example, then record the validated decision and fold it into the real implementation.
Why use it?
It lets a team learn before committing to production code, databases, or polished design. Showing the full state after each action makes unclear behavior easier to discuss.

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/astordu/qoderharness/prototype
Any agent
npx skills add astordu/qoderharness --skill prototype
Clone the repo
git clone --depth 1 https://github.com/astordu/qoderharness

Made for: Claude Code, Codex.

Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 761 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.00049 $0.00761
Opus 5 $0.00024 $0.00380
Sonnet 5 $0.00010 $0.00152
Haiku 4.5 $0.00005 $0.00076

Measured 2d ago against content hash 50a6065e71f7, 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 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.

.qoder/skills/prototype/SKILL.md · 27 lines

What it actually says

原型(Prototype)

原型是 用来回答一个问题的、用完即弃的代码。问题决定了它的形态。

选择一个分支

弄清楚正在回答的是哪个问题——从用户的提示、周围的代码,或者在用户在场时直接问:

  • "这个逻辑 / 状态模型感觉对路吗?"LOGIC.md。构建一个小巧的交互式终端应用,把状态机推过那些在纸面上难以推演的情形。
  • "这东西应该长什么样?"UI.md。在单个路由上生成若干个彻底不同的 UI 变体,通过一个 URL 查询参数和一个浮动的底部栏来切换。

这两个分支产出的产物截然不同——搞错了会浪费整个原型。如果问题确实含糊、又联系不上用户,就默认选择与周围代码更匹配的那个分支(后端模块 → 逻辑;页面或组件 → UI),并在原型顶部注明这个假设。

两个分支都适用的规则

  1. 从第一天起就用完即弃,并明确标注为如此。 把原型代码放在它将实际被使用的地方附近(紧挨着它所要原型化的那个模块或页面),这样上下文一目了然——但要为它取名,让随手翻看的读者一眼就能看出这是原型,而非生产代码。对于用完即弃的 UI 路由,遵循项目已有的路由约定;不要发明新的顶层结构。
  2. 一条命令即可运行。 无论项目现有的任务运行器支持什么——pnpm <name>python <path>bun <path> 等等。用户不用动脑子就能启动它。
  3. 默认不做持久化。 状态放在内存里。持久化正是原型要 检验 的东西,而不应是它所依赖的东西。如果问题明确涉及数据库,就打一个临时数据库,或者用一个名字清晰标为 "PROTOTYPE — wipe me" 的本地文件。
  4. 跳过打磨。 没有测试,除了让原型 能跑 之外没有错误处理,没有抽象。目的是快速学到东西。
  5. 把状态暴露出来。 每次操作后(逻辑)或每次切换变体时(UI),打印或渲染完整的相关状态,让用户看清变了什么。
  6. 完成后把它归档保存。 把任何已验证的决策折叠进真实代码,然后把原型本身作为 一手资料(primary source) 保存下来:把它提交到一个用完即弃的分支上、不进主干,并在实现 issue 上留一个指向该分支的上下文指针。也把答案保存下来——结论以及它所解决的问题——记在 issue 或提交里。主干只保留经过验证的决策。
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.

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. 2d ago First seen · 27 lines · 49 tokens per session scan A 50a6065e71f7

Subscribe to this mod's changes

prototype is a skill published in the GitHub repository astordu/qoderharness (21 stars, last pushed 6d ago), licensed MIT. It adds 49 tokens to every session and 761 once invoked, about $0.0002 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

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens