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/markmhendrickson/neotoma/create_prototypenpx skills add markmhendrickson/neotoma --skill create_prototypegit clone --depth 1 https://github.com/markmhendrickson/neotomaWhat 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.00006 | $0.00684 |
| Opus 5 | $0.00003 | $0.00342 |
| Sonnet 5 | $0.00001 | $0.00137 |
| Haiku 4.5 | $0.00001 | $0.00068 |
Grade A, and why
create_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.
This is a copy
92% identical to create-prototype — 12 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Prototype
Create fully functional client-side prototype for Feature Unit {{input:feature_id}}.
Follow foundation/development/feature_unit_workflow.md Step 1 (Prototype Creation). Configuration is read from foundation-config.yaml.
This happens after Checkpoint 0 (spec creation) and before Checkpoint 1 (prototype review).
Implements prototype creation after Checkpoint 0 (spec) is complete. Creates a fully interactive, client-side prototype with mocked APIs.
Trigger
- Spec created with UI requirements (Checkpoint 0 complete, UI changes present) OR
- No UI changes required (skip prototype)
Tasks
-
Load configuration:
- Read
foundation-config.yamlto get feature unit settings - Determine directory structure and prototype paths
- Read
-
Load spec and manifest:
{configured_directory}/in_progress/{{input:feature_id}}/{{input:feature_id}}_spec.md(orcompleted/if completed){configured_directory}/in_progress/{{input:feature_id}}/manifest.yaml(orcompleted/if completed)
-
Check if UI changes present:
- Review spec and manifest for UI components
- Verify UX Requirements section exists in spec (from Checkpoint 0)
- If no UI changes → skip to implementation
- If UI changes present → proceed
-
Create prototype:
- Use configured prototype directory structure (or default:
frontend/src/prototype/) - Create prototype component(s):
{prototype_dir}/components/{{input:feature_id}}_*.tsx - Create mock API fixtures:
{prototype_dir}/fixtures/{{input:feature_id}}_*.ts - Integrate into prototype main file
- Use configured prototype directory structure (or default:
-
Prototype requirements:
- Fully interactive (click, type, navigate)
- All API calls mocked (no real backend)
- All UI states testable (empty, error, loading, success)
- Accessible (keyboard nav, ARIA if applicable)
- Uses existing design system components (if available)
- Documented mock API responses
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 · 91 lines · 6 tokens per session scan A c743ccfb98cd
create_prototype is a skill published in the GitHub repository markmhendrickson/neotoma (29 stars, last pushed 5d ago), licensed MIT. It adds 6 tokens to every session and 684 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to create-prototype, differing in 12 lines, and is treated as a copy.
Other skills, from other repositories
clean-user-facing-text
Clean and finalize authorized natural-language text intended for readers by auditing suspicious invisible Unicode and rewriting prose while preserving facts, meaning, and the writer's voice. Use when the user asks to clean, humanize, polish, or finalize articles, manuscripts, reports, documentation, emails, product…
openbiliclaw-adapter
Use OpenBiliClaw's versioned Agent Bridge CLI to read multi-source recommendations, profile state, dialogue, probes, saved lists, and submit explicit feedback.
writing-specs
Use when authoring a spec or implementation plan, or planning multi-task work.
release
Use when releasing a version, bumping project versions, or pushing release tags.
add-platform-source
Use when adding, integrating, repairing, hardening, completing, auditing, testing, or releasing an OpenBiliClaw platform/source adapter, including anonymous or credentialed APIs, browser-extension tasks and identity, source auth/status, bootstrap and incremental sync, formal discover, configuration, recommendation…
bilibili_browse
Browse Bilibili pages using agent-browser for visual exploration and DOM interaction.