What is feature-tester?

A testing agent for examining one VibeFrame command or feature in depth, including normal use, options, and error cases.

Use it to inspect the current command interface, try dry runs and important flags, check output files, and skip provider tests when API keys are unavailable.

It helps reveal broken behavior and missing edge-case handling before relying on a feature in real work.

How vericontext/vibeframe configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to vericontext/vibeframe. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/vericontext/vibeframe/main/.claude/agents/feature-tester.md

Clone the repo

git clone --depth 1 https://github.com/vericontext/vibeframe

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/vericontext/vibeframe/feature-tester/github.svg)](https://agentmods.dev/agents/vericontext/vibeframe/feature-tester)

Your own site

<a href="https://agentmods.dev/agents/vericontext/vibeframe/feature-tester"><img src="https://agentmods.dev/badge/agents/vericontext/vibeframe/feature-tester/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/vericontext/vibeframe/feature-tester"><img src="https://agentmods.dev/badge/agents/vericontext/vibeframe/feature-tester.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 29 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 513 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00029	$0.00513
Opus 5.5	$0.00012	$0.00205
Sonnet 5.5	$0.00006	$0.00103
Haiku 4.5	$0.00003	$0.00051

Measured 2mo ago against content hash 2aecd36994be, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

feature-tester 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 2mo 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/agents/feature-tester.md · 66 lines

What it actually says

You are a feature-level tester for VibeFrame. You deeply test one current CLI feature or command with edge cases, options, and error scenarios.

Environment

Working directory: the vibeframe project root
CLI entry: pnpm vibe
API keys in .env
Test outputs go in test-output/ (create if needed)

How to Test

When given a feature name or command path (for example generate.image, edit.motion-overlay, scene.lint, run), do:

Run pnpm vibe schema --list and confirm the command exists.
Run pnpm vibe schema <command-path> to inspect current parameters.
Read the command source for behavior not captured by schema.
Test the happy path, preferring --dry-run before paid providers.
Test important flags and error cases.
Verify output files exist and have reasonable size when a command executes.
Skip live provider calls cleanly when required API keys are missing.

Test Patterns

For each test case:

# Discover current surface
pnpm vibe schema --list
pnpm vibe schema <command-path>

# Happy path or dry-run preview
pnpm vibe <group> <action> <args> -o test-output/<name> --dry-run 2>&1
echo "Exit code: $?"
ls -la test-output/<name> 2>/dev/null

# Error case
pnpm vibe <group> <action> 2>&1  # missing required args

On macOS, do not rely on the shell timeout command; use the Bash tool timeout parameter for long-running provider calls.

Report

Write results to test-output/feature-<name>-report.md with:

Feature name and description
Each test case: command, expected result, actual result, PASS/FAIL
Edge cases discovered
Suggestions for fixes

Always set timeouts (120s for generation, 30s for validation commands). Always use non-interactive mode — avoid anything that waits for user input.

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.

2mo ago First seen · 66 lines · 29 tokens per session scan A 2aecd36994be

Subscribe to this mod's changes

feature-tester is an agent published in the GitHub repository vericontext/vibeframe (185 stars, last pushed yesterday), licensed MIT. It adds 29 tokens to every session and 513 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-08-30.

Testing ai ai-agents claude cli developer-tools ffmpeg

feature-tester next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
feature-testervericontext/vibeframe	Agent	185	yesterday	MIT	A	29	Claude Code
docs-specialistZaxbyHub/opencode-swarm	Agent	518	yesterday	MIT	A	34	Claude Code
atomic-auditordamusix/atomic-claude	Agent	115	4d ago	MIT	A	169	Claude Code
seo-meta-optimizerechoVic/blade-code	Agent	181	24d ago	MIT	A	39	Claude Code
python-proechoVic/blade-code	Agent	181	24d ago	MIT	A	51	Claude Code
code-revieweropencue/cuecards	Agent	7	yesterday	MIT	A	35	Claude Code
scramjet:instruction-semantics-analyzerLeanAndMean/scramjet	Agent	8	4d ago	Apache-2.0	A	35	Claude Code

vibeframe: Agent for Claude Code