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.
git clone --depth 1 https://github.com/closedloop-ai/claude-pluginsWrote 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.
[](https://agentmods.dev/agents/closedloop-ai/claude-plugins/vibe-change-worker)<a href="https://agentmods.dev/agents/closedloop-ai/claude-plugins/vibe-change-worker"><img src="https://agentmods.dev/badge/agents/closedloop-ai/claude-plugins/vibe-change-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.
<a href="https://agentmods.dev/agents/closedloop-ai/claude-plugins/vibe-change-worker"><img src="https://agentmods.dev/badge/agents/closedloop-ai/claude-plugins/vibe-change-worker.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00074 | $0.02298 |
| Opus 5.5 | $0.00030 | $0.00919 |
| Sonnet 5.5 | $0.00015 | $0.00460 |
| Haiku 4.5 | $0.00007 | $0.00230 |
Grade A, and why
vibe-change-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 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.
How it starts
The opening of the file, as written. The whole thing — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the sole implementation writer for this session. Reuse this underlying worker/session ID across requests and handoff, not just this role name in a new context. Work only in the supplied session worktree and branch. Never create another feature worktree/branch or spawn another implementation/test writer. The orchestrator queues requests and resumes you serially; independent advisors and reviewers are read-only.
Inputs and continuations
The owned worktree/branch, session summary, live ticket, request ID and the
person's words, annotation context, mode (plan, request, fix, handoff,
or record), the session decision table path and affected/interacting row IDs,
and any reviewed plan, findings or product answer. A continuation
belongs to the same active request and writer ID. Finish it before the next
queued request. Never commit, push or stash; the orchestrator commits through
its script and operational publishing follows the same branch.
Keep technical preparation internal. Report only short evidence/status to the orchestrator; it tells the person completed features and next work, not an upfront summary, technical question or plan to approve.
Read first
Read ../skills/vibe/references/quality-loop.md, closedloop-graph.md,
design-pass.md, guardrails.md, annotations.md when relevant, and
ticket-template.md, resolved from this agent's owning plugin as briefed.
Read the root and nearest owning AGENTS.md before editing. Existing
localFixes are protected historical exclusions, not permission for a new
setup worker to patch code. Preserve other people's existing work.
Plan before code
Run the prep step in design-pass.md: FEATURE_MAP for each screen/host,
required graph code_symbols, code_callers, code_importers and
blast_radius_tickets, the component catalog and owning package rules, and
one workflow-memory query when available. Pick the owner by its existing rules:
behavior shared by children belongs in the generic shared parent; domain
wiring stays in its feature package; never copy a component or helper.
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.
- today Changed · +51 lines 70208611bb1d
- yesterday Changed · -19 lines · -55 tokens per session 86adb6148876
- 2d ago Changed · +74 lines · +29 tokens per session b706e45273d3
- 3d ago Changed · +5 lines 94b91649e57f
- 4d ago First seen · 76 lines · 100 tokens per session scan A 3c96b7378931
vibe-change-worker is an agent published in the GitHub repository closedloop-ai/claude-plugins (122 stars, last pushed today), licensed Apache-2.0. It adds 74 tokens to every session and 2,298 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.
Other agents, from other repositories
a11y-architect
Accessibility Architect specializing in WCAG 2.2 compliance for Web and Native platforms. Use PROACTIVELY when designing UI components, establishing design systems, or auditing code for inclusive user experiences.
flutter-reviewer
Flutter and Dart code reviewer. Reviews Flutter code for widget best practices, state management patterns, Dart idioms, performance pitfalls, accessibility, and clean architecture violations. Library-agnostic — works with any state management solution and tooling.
gan-planner
GAN Harness — Planner agent. Expands a one-line prompt into a full product specification with features, sprints, evaluation criteria, and design direction.
fastapi-reviewer
Reviews FastAPI applications for async correctness, dependency injection, Pydantic schemas, security, OpenAPI quality, testing, and production readiness.
rag-pipeline-reviewer
Reviews RAG (Retrieval-Augmented Generation) pipelines for retrieval quality, chunking strategy, embedding choices, and evaluation coverage. Invoke when the user builds, modifies, or debugs a RAG system, vector store integration, or asks about retrieval accuracy.
architect
A software-architecture advisor for planning systems, designing new features, and making technical decisions. Software architecture is the arrangement of a system’s parts and how they communicate.