dev

Implement features, fix bugs, and iterate until all quality checks pass. Use for autonomous development tasks that benefit from worktree isolation and self-correction.

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

Made for: Claude Code.

Per session 32 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 544 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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.00032 $0.00544
Opus 5 $0.00016 $0.00272
Sonnet 5 $0.00006 $0.00109
Haiku 4.5 $0.00003 $0.00054

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

Security

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 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/dev.md · 66 lines

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.ts for 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/scrollTop in generic code)
    • Zero allocations on hot paths
    • CSS via external files with BEM naming
    • const over let, early returns, pure functions
  • 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
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 · 66 lines · 32 tokens per session scan A d54cf5e40828

Subscribe to this mod's changes

dev is an agent published in the GitHub repository floor/vlist (16 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 544 once invoked, about $0.0002 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