feature-scaffold

Scaffold a new vlist feature with all required files following project conventions. Use when creating a new feature plugin.

Agent for Claude Code

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 agents/floor/vlist/plugin-scaffold
Clone the repo
git clone --depth 1 https://github.com/floor/vlist

Made for: Claude Code.

Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 529 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.00027 $0.00529
Opus 5 $0.00014 $0.00264
Sonnet 5 $0.00005 $0.00106
Haiku 4.5 $0.00003 $0.00053

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

Security

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.

.claude/agents/plugin-scaffold.md · 57 lines

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

  1. The user provides a feature name and description.

  2. Read these reference files:

    • src/builder/types.tsVListFeature, BuilderContext, BuilderConfig interfaces
    • src/features/grid/feature.ts — canonical feature structure
    • src/features/grid/index.ts — barrel export pattern
    • test/plugins/grid/plugin.test.ts — test pattern
    • src/index.ts — how features are exported
  3. Create files:

    • src/features/{name}/feature.ts — implements VListFeature<T>
    • src/features/{name}/index.ts — barrel export
    • src/features/{name}/types.ts — config types (if needed)
    • test/plugins/{name}/plugin.test.ts — test skeleton
  4. Requirements:

    • Export a with{Name} factory function returning VListFeature<T>
    • Unique name string and priority number
    • Implement setup(ctx: BuilderContext<T>), optional destroy()
    • Follow all TypeScript rules (strict, no any, explicit types)
    • Add JSDoc on all public exports
  5. Add the export to src/index.ts.

  6. 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
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. today First seen · 57 lines · 27 tokens per session scan A 98c580566f26

Subscribe to this mod's changes

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.

Related

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…

andisab/swe-marketplace · 401 tokens

bun-runtime-optimizer

Bun JavaScript runtime and bundler optimization specialist.

viksant/vibe-coding-tools-content · 10 tokens

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…

module-federation/core · 264 tokens

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.

growthxai/output · 40 tokens

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…

sahithvibudhi/vibe-tree · 365 tokens

speckit-constitution

Review or amend the project constitution. Displays current principles and optionally proposes amendments through the governance process.

boussadjra/vuestrata · 25 tokens