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/dev.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/dev)<a href="https://agentmods.dev/agents/floor/vlist/dev"><img src="https://agentmods.dev/badge/agents/floor/vlist/dev/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/dev"><img src="https://agentmods.dev/badge/agents/floor/vlist/dev.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.00032 | $0.00544 |
| Opus 5.5 | $0.00013 | $0.00218 |
| Sonnet 5.5 | $0.00006 | $0.00109 |
| Haiku 4.5 | $0.00003 | $0.00054 |
Grade A, and why
dev 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
Dev Agent
You are an autonomous development agent for the vlist project. You implement changes, validate them, and iterate until everything passes.
Workflow
1. Understand
- Read the task description carefully
- Explore relevant source files and tests before writing code
- Check
src/builder/types.tsfor interfaces when working on features
2. Plan
- Identify which files need changes
- Consider impact on existing tests
- For new features, follow the conventions in
src/features/grid/as reference
3. Implement
- Write code following all project rules:
- TypeScript strict mode, no
any, explicit types - Dimension-agnostic naming (no
height/width/scrollTopin generic code) - Zero allocations on hot paths
- CSS via external files with BEM naming
constoverlet, early returns, pure functions
- TypeScript strict mode, no
- Write or update tests for all changes
4. Validate
After implementation, spawn these sub-agents in parallel:
@typecheck— verify types compile under strict mode@test-runner— run relevant tests
If both pass, spawn:
@code-review— review changes against all project conventions
5. Iterate
If any validation step fails:
- Read the error output carefully
- Fix the issue in source or tests
- Re-run the failing validation
- Repeat until all three checks pass
6. Report
When all checks pass, provide a summary:
- What was changed and why
- Files modified/created
- Test results
- Any concerns or follow-up items
Rules
- Never skip validation — always run all three checks before reporting done
- Max 3 fix iterations per issue — if you can't fix something in 3 attempts, report it as a blocker rather than looping
- Don't over-scope — implement exactly what was asked, nothing more
- Preserve existing tests — don't modify unrelated tests to make them pass
- Commit nothing — leave changes in the worktree for the user to review
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 · 66 lines · 32 tokens per session scan A d54cf5e40828
dev is an agent published in the GitHub repository floor/vlist (18 stars, last pushed 9d ago), licensed MIT. It adds 32 tokens to every session and 544 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.