Borrowing it
Nothing to install: this file belongs to floor/vlist. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/floor/vlist/main/.claude/agents/plugin-scaffold.mdgit clone --depth 1 https://github.com/floor/vlistWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/floor/vlist/plugin-scaffold)<a href="https://agentmods.dev/agents/floor/vlist/plugin-scaffold"><img src="https://agentmods.dev/badge/agents/floor/vlist/plugin-scaffold/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/floor/vlist/plugin-scaffold"><img src="https://agentmods.dev/badge/agents/floor/vlist/plugin-scaffold.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00027 | $0.00529 |
| Opus 5.5 | $0.00011 | $0.00212 |
| Sonnet 5.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 1mo 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.
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.
- 1mo ago First seen · 57 lines · 27 tokens per session scan A 98c580566f26
feature-scaffold is an agent published in the GitHub repository floor/vlist (18 stars, last pushed 9d ago), licensed MIT. It adds 27 tokens to every session and 529 once invoked, about $0.0001 per session on Opus 5.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
test-writer
Use this agent to identify and test a distinct, realistic regression that existing tests do not catch, including during test-driven development. Do not generate a comprehensive suite by default. Invoke /writing-tests before changing test setup or assertions.\n\nExamples:\n \nContext: The user has just implemented a…
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…
test-engineer
TDD & Logic Verification Expert. Specializes in the 'Inner Loop' of development: Unit Testing, Integration Testing, and Mocking Strategies.
test-coverage-analyzer
Use this agent to map changed code paths to test coverage, identify untested error paths, and review test quality. Rates each gap 1-10 for criticality. Context: A PR adds a new validation function with no tests. user: "Check test coverage" assistant: "I'll use the test-coverage-analyzer to map coverage and identify…
typescript-pro
Master TypeScript with advanced types, generics, and strict type safety. Handles complex type systems, decorators, and enterprise-grade patterns. Use PROACTIVELY for TypeScript architecture, type inference optimization, or advanced typing patterns.
test-generator
Use this agent to generate high-quality TypeScript unit tests for a target file or directory. Detects the host project's test runner (Jest, Vitest, node:test) and follows the project's documented testing standards.