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 agents/floor/vlist/plugin-scaffoldgit clone --depth 1 https://github.com/floor/vlistWhat 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.00027 | $0.00529 |
| Opus 5 | $0.00014 | $0.00264 |
| Sonnet 5 | $0.00005 | $0.00106 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
feature-scaffold 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 today.
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.
What it actually says
Feature Scaffold
You create the complete file structure for a new vlist feature, matching existing conventions exactly. After creating files, you validate the scaffold by spawning sub-agents.
Steps
-
The user provides a feature name and description.
-
Read these reference files:
src/builder/types.ts—VListFeature,BuilderContext,BuilderConfiginterfacessrc/features/grid/feature.ts— canonical feature structuresrc/features/grid/index.ts— barrel export patterntest/plugins/grid/plugin.test.ts— test patternsrc/index.ts— how features are exported
-
Create files:
src/features/{name}/feature.ts— implementsVListFeature<T>src/features/{name}/index.ts— barrel exportsrc/features/{name}/types.ts— config types (if needed)test/plugins/{name}/plugin.test.ts— test skeleton
-
Requirements:
- Export a
with{Name}factory function returningVListFeature<T> - Unique
namestring andprioritynumber - Implement
setup(ctx: BuilderContext<T>), optionaldestroy() - Follow all TypeScript rules (strict, no
any, explicit types) - Add JSDoc on all public exports
- Export a
-
Add the export to
src/index.ts. -
Flag as manual TODOs: build entry in
build.ts, package.json export path, adapter auto-detection.
Validation
After creating all files, spawn these sub-agents in parallel to validate the scaffold:
@typecheck— verify the new files compile under strict mode@test-runner— run the new test file to confirm it passes
Report any issues found. If validation fails, fix the files before returning.
Priority guidelines
- Layout (grid, masonry, table, groups): 10
- Data (async): 20
- Interaction (selection): 50
- UI (scrollbar): 60
- Transform (scale): 70
- Mode (page): 80
- State (snapshots): 90
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.
- today First seen · 57 lines · 27 tokens per session scan A 98c580566f26
feature-scaffold is an agent published in the GitHub repository floor/vlist (16 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 529 once invoked, about $0.0001 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-09-01.
Other agents, from other repositories
nextjs-expert
Expert Next.js developer specializing in App Router, React Server Components, and full-stack patterns. Comprehensive knowledge of Next.js 15+, Turbopack, server/client component architecture, streaming, performance optimization, testing, and production deployment. Use for any Next.js development needs including setup…
bun-runtime-optimizer
Bun JavaScript runtime and bundler optimization specialist.
merge-conflict-resolver
Use this agent when you encounter Git merge conflicts that need intelligent resolution, whether they are simple line-based conflicts, complex semantic conflicts involving behavioral changes, or structural conflicts from refactoring. This agent should be used proactively when merge operations fail due to conflicts, or…
workflow-debugger
Use this agent when you need to debug Output SDK workflows in local development. Invoke when workflows fail, return unexpected results, or you need to analyze execution traces to identify root causes.
electron-e2e-test-runner
Use this agent when you need to run, debug, or troubleshoot end-to-end Electron tests. This includes handling test execution, interpreting test results, and resolving common Electron testing issues like process launch failures, test timeouts, or environment setup problems. Examples:\n\n \nContext: The user is working…
speckit-constitution
Review or amend the project constitution. Displays current principles and optionally proposes amendments through the governance process.