What is vibe-seed-fix-worker?

An automated worker that repairs test seed data for the Vibe feature in the Symphony Alpha codebase. Seed data is sample database content used to prepare an environment for testing or demonstration.

Use it to create an isolated Git worktree, add missing or outdated model data through the application's normal data producers, update coverage data, and fix related pull-request or merge-queue problems.

It fixes seed data that no longer matches the application and checks the result until the required checks pass. It can also respond to failures found after a pull request is opened.

vibe-seed-fix-worker — Agent for Claude Code by closedloop-ai

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.

Clone the repo

git clone --depth 1 https://github.com/closedloop-ai/claude-plugins

Made for: Claude Code.

Or install vibe, the plugin that ships this one along with the rest of its 10 skills, 16 agents.

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/closedloop-ai/claude-plugins/vibe-seed-fix-worker/github.svg)](https://agentmods.dev/agents/closedloop-ai/claude-plugins/vibe-seed-fix-worker)

Your own site

<a href="https://agentmods.dev/agents/closedloop-ai/claude-plugins/vibe-seed-fix-worker"><img src="https://agentmods.dev/badge/agents/closedloop-ai/claude-plugins/vibe-seed-fix-worker/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/closedloop-ai/claude-plugins/vibe-seed-fix-worker"><img src="https://agentmods.dev/badge/agents/closedloop-ai/claude-plugins/vibe-seed-fix-worker.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 831 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.00087	$0.00831
Opus 5.5	$0.00035	$0.00332
Sonnet 5.5	$0.00017	$0.00166
Haiku 4.5	$0.00009	$0.00083

Measured yesterday against content hash 2991554e4c82, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

vibe-seed-fix-worker 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 yesterday.

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.

plugins/vibe/agents/vibe-seed-fix-worker.md · 63 lines

How it starts

The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You fix the vibe seed. The orchestrator never reads your logs; return a short result. You never commit or push: the orchestrator commits, because a commit runs the repository's commit hooks.

Inputs

Fix mode: the checkout path, the ticket slug, the drift list. Follow-up mode: the fix worktree, the PR URL, and what woke the orchestrator.

Read first

../skills/vibe/references/closedloop-graph.md; in the repo, packages/database/AGENTS.md, apps/api/AGENTS.md, the coverage README in packages/database/prisma/seeds/coverage/ and apps/desktop/prisma/seed-coverage/, apps/api/scripts/vibe-seed/stage.ts and stages/index.ts.

Fix mode

In the checkout: git fetch origin main, then git worktree add --no-track -b fix/<iss-slug>-vibe-seed .claude/worktrees/<iss-slug> origin/main and ./.closedloop-ai/loops-setup.sh in it.
For each drifted model, find the producer that writes it in production (closedloop-graph code_symbols, code_callers; the introducing ticket's intent via ticket_detail) and add it to the stage that owns that area (or a new stage registered in stages/index.ts in dependency order). Use the producer, not raw inserts, wherever one exists; realistic data tied to the seeded org; idempotent on re-run.
- todo: seed it and flip the coverage file to seeded with the stage name, or to skipped with a reason you can defend from the code when no screen reads it.
- missing: add the coverage file with a decided status.
- stale: delete the coverage file.
- seedError / emptyRows / red walk: fix the seed code, never the schema. Never edit migrations or schema.prisma; never modify packages/golden-sessions/.
Run until all pass: pnpm vibe check (no drift), the affected tests (code_tests_for on changed files, plus pnpm --filter @repo/database test and the apps/api/scripts/__tests__ vibe-seed suites), pnpm check:source-gates, Biome on changed files, and the screen walk (pnpm vibe up --ci, pnpm vibe walk, then pnpm vibe down even when the walk fails).

Read the full file on GitHub · 63 lines

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.

yesterday Changed · +2 lines 2991554e4c82
4d ago First seen · 61 lines · 87 tokens per session scan A 8b5a8ca37da1

Subscribe to this mod's changes

vibe-seed-fix-worker is an agent published in the GitHub repository closedloop-ai/claude-plugins (122 stars, last pushed today), licensed Apache-2.0. It adds 87 tokens to every session and 831 once invoked, about $0.0003 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-10-06.

Claude Code Git and workflow LLM Testing agentic-ai ai-agents anthropic developer-tools

gan-evaluator

GAN Harness — Evaluator agent. Tests the live running application via Playwright, scores against rubric, and provides actionable feedback to the Generator.

affaan-m/ECC · 32 tokens

gan-generator

GAN Harness — Generator agent. Implements features according to the spec, reads evaluator feedback, and iterates until quality threshold is met.

affaan-m/ECC · 29 tokens

pr-test-analyzer

Review pull request test coverage quality and completeness, with emphasis on behavioral coverage and real bug prevention.

affaan-m/ECC · 24 tokens

e2e-runner

An end-to-end testing role for checking complete user journeys through a website or application. End-to-end tests simulate actions such as opening pages, filling forms, and clicking buttons.

xu-xiang/everything-claude-code-zh · 84 tokens

qa-engineer

Test author / runner persona. Authors per-acceptance-criterion test plans and the tests that realize them, then runs the verify/test recipes and reports pass/fail evidence against the contract. Dispatch it to build and execute the test coverage for an authorized atom. It writes and runs tests in a confined tree; it…

lukasrepublic/agentic-foundry · 85 tokens

history-analyst

Reviews a diff against the git history of the files it touches. Uses git log and git blame to catch changes that undo a previous fix, reintroduce a reverted pattern, or contradict the intent recorded in earlier commits. Adds the dimension a code-only reviewer misses — the past. Use when the changed files have…

MANOJ21K/agentic-code-review · 73 tokens