A test-writing agent for the Figma-Context-MCP project, using Vitest, a JavaScript and TypeScript testing tool. It follows the project's file locations, test structure, fixtures, and integration-test rules.

Use it to write unit tests with injected dependencies, integration tests controlled by environment variables, fixture files, and tests for known broken behavior.

It helps produce tests that match the existing codebase instead of introducing unfamiliar mocking or formatting patterns.

How felixAnhalt/figma-to-code-mcp configures Claude Code and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to felixAnhalt/figma-to-code-mcp. 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/felixAnhalt/figma-to-code-mcp/main/.opencode/agents/test-writer.md

Clone the repo

git clone --depth 1 https://github.com/felixAnhalt/figma-to-code-mcp

Made for: Claude Code, OpenCode.

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/felixanhalt/figma-to-code-mcp/test-writer.svg)](https://agentmods.dev/agents/felixanhalt/figma-to-code-mcp/test-writer)

Your own site

<a href="https://agentmods.dev/agents/felixanhalt/figma-to-code-mcp/test-writer"><img src="https://agentmods.dev/badge/agents/felixanhalt/figma-to-code-mcp/test-writer.svg" alt="Measured on agentmods" height="20"></a>

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

When invoked 420 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.00019	$0.00420
Opus 5	$0.00010	$0.00210
Sonnet 5	$0.00004	$0.00084
Haiku 4.5	$0.00002	$0.00042

Measured 8d ago against content hash ed90cbb7ee86, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

test-writer 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 8d 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.

.opencode/agents/test-writer.md · 66 lines

What it actually says

You write tests for the Figma-Context-MCP project. Follow these conventions strictly.

Test setup

// vitest.config.ts configures: 30s timeout, ~ alias, vitest globals enabled
// No imports needed for describe/it/expect/beforeAll/afterAll

File placement

All tests go in src/tests/ (excluded from TS compilation)
Test fixtures go in src/tests/resources/ (gitignored)

Testing patterns

Unit tests — no mocking frameworks. Use seam injection (pass dependencies as params):

const result = myFunction(input, stubService);

Integration tests — gate on env vars:

it("fetches from live API", () => {
  if (!process.env.RUN_FIGMA_INTEGRATION) return;
  // real API call
});

Known broken behavior:

it.fails("does not handle negative values", () => {
  handleNegative(-1);
});

Vitest commands

pnpm test — run all
pnpm vitest run src/tests/tokenizer.test.ts — single file
pnpm vitest run -t "test name" — filter by name

Style

Use describe/it blocks
One assertion concept per it
Use beforeAll/afterAll for setup/teardown only
No any in test code
Import from "vitest" only when explicitly needed (globals cover most)

After writing tests, run pnpm vitest run <your-test-file> to verify they pass.

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.

8d ago First seen · 66 lines · 0 tokens per session scan A ed90cbb7ee86

Subscribe to this mod's changes

test-writer is an agent published in the GitHub repository felixAnhalt/figma-to-code-mcp (5 stars, last pushed 10d ago), licensed MIT. It adds 19 tokens to every session and 420 once invoked, about $0.0001 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-08-31.

Testing Unit testing

ai-hygiene-auditor

Audit codebases for AI-generation warning signs: vibe coding patterns, agent psychosis indicators, slop artifacts, and Tab-completion bloat. Specialized complement to bloat-auditor.

athola/claude-night-market · 48 tokens

tester

A test-writing agent that designs and implements unit, integration, and end-to-end tests. End-to-end tests check a complete user or system flow from start to finish.

Insajin/autopus-adk · 38 tokens

pydantic-ai-validator

Testing and validation specialist for Pydantic AI agents. USE AUTOMATICALLY after agent implementation to create comprehensive tests, validate functionality, and ensure readiness. Uses TestModel and FunctionModel for thorough validation.

coleam00/context-engineering-intro · 46 tokens

test-expert-csk

Test expert. Use proactively after new handler/endpoint/agent behavior is added: writes and runs unit/integration tests and guarantees the DoD's "tests are green".

byerlikaya/claude-starter-kit · 41 tokens

test-writer

Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…

HirogaKatageri/hirokata · 77 tokens

verify-app

Full verification - unit tests, migration check, lint, types.

pablomarin/claude-codex-forge · 15 tokens

figma-to-code-mcp: Agent for Claude Code