implement

A command workflow for building a new feature in the VisionAgent project from start to finish. It covers planning, implementation, exports, tests, and quality checks.

In plain words
What is it for?
Use it to add source files, update the project’s public API, write tests with mocked network calls, and run the project’s checks.
Why use it?
It turns a feature request into a defined sequence of code and verification tasks, reducing the chance of missing public exports or tests.

Command 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 commands/sijeeshmiziha/visionagent/implement
Clone the repo
git clone --depth 1 https://github.com/sijeeshmiziha/visionagent

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 402 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.00000 $0.00402
Opus 5 $0.00000 $0.00201
Sonnet 5 $0.00000 $0.00080
Haiku 4.5 $0.00000 $0.00040

Measured 2d ago against content hash 41f608a8ddbb, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

implement 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 2d 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.

.claude/commands/implement.md · 65 lines

What it actually says

Implement Feature

You are in full autonomous implementation mode. Follow the VisionAgent agentic task approach from CLAUDE.md rigorously.

Task

$ARGUMENTS

Execution Plan

Work through these steps in order without stopping to ask unless genuinely blocked:

1. Understand & Plan

  • Read CLAUDE.md for project conventions
  • Identify all files that need to be created or modified
  • Trace the call chain from public API → implementation
  • Check src/index.ts to understand current exports
  • Read any existing similar code for patterns to follow

2. Implement

  • Write source code in src/
  • Follow naming conventions (kebab-case files, PascalCase interfaces, camelCase functions)
  • Use @/ imports internally, visionagent alias in examples
  • Add explicit return types on all public functions
  • No any in src/ — use Zod inference or proper typing

3. Export

  • Add exports through the module's index.ts
  • Add to src/index.ts if it's part of the public API

4. Test

  • Write tests in tests/ (not co-located)
  • Use MSW mocks for external API calls
  • Run: npm test
  • Fix any failures before proceeding

5. Quality Gates

Run these in sequence and fix all issues:

npm run typecheck
npm run lint:fix
npm run format
npm run build

6. Example (if new feature)

  • Add an example in examples/<module>/<feature>.ts
  • Register it in examples/lib/registry.ts
  • Verify it runs: npm run example -- examples/<module>/<feature>.ts

7. Final Verification

npm run ci

Report what was implemented, what tests were added, and confirm npm run ci passed.

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. 2d ago First seen · 65 lines · 0 tokens per session scan A 41f608a8ddbb

Subscribe to this mod's changes

implement is a command published in the GitHub repository sijeeshmiziha/visionagent (2 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 402 tokens. 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-08-31.