Borrowing it
Nothing to install: this file belongs to iBrain-BVBA/gutt-claude-code-plugin. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/iBrain-BVBA/gutt-claude-code-plugin/main/.claude/agents/plugin-qa.mdgit clone --depth 1 https://github.com/iBrain-BVBA/gutt-claude-code-pluginWrote 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/ibrain-bvba/gutt-claude-code-plugin/plugin-qa)<a href="https://agentmods.dev/agents/ibrain-bvba/gutt-claude-code-plugin/plugin-qa"><img src="https://agentmods.dev/badge/agents/ibrain-bvba/gutt-claude-code-plugin/plugin-qa/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/ibrain-bvba/gutt-claude-code-plugin/plugin-qa"><img src="https://agentmods.dev/badge/agents/ibrain-bvba/gutt-claude-code-plugin/plugin-qa.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.00028 | $0.03199 |
| Opus 5.5 | $0.00011 | $0.01280 |
| Sonnet 5.5 | $0.00006 | $0.00640 |
| Haiku 4.5 | $0.00003 | $0.00320 |
Grade B, and why
plugin-qa scanned grade B with 1 finding 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 1mo 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.
Reads MCP configurationmediumAgent snooping
mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.
Read MCP configuration from `.claude/settings.json` and verify: How it starts
The opening of the file, as written. The whole thing — 408 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plugin QA Agent
Unified quality gate for the gutt-pro plugin. Runs five validation passes covering structure, agent definitions, hooks, IDE compatibility, and MCP integration, then produces a single consolidated report with pass/fail verdicts.
Trigger
Invoke this agent when:
- Preparing a release or version bump
- After adding/removing hooks, agents, or skills
- After modifying manifests or hook registration
- After changing MCP configuration or hook shared libraries
- When CI reports plugin loading errors
- When user asks "validate the plugin", "run QA checks", or "is the plugin healthy?"
Workflow
Pass 1: Structure Validation
Validate that the plugin is structurally sound with valid manifests and consistent cross-references.
1a. JSON Manifest Validation
Parse each manifest and verify required fields:
| File | Required Fields |
|---|---|
.claude-plugin/plugin.json |
name, version, description |
.cursor-plugin/plugin.json |
name, version, description |
.claude-plugin/marketplace.json |
Valid JSON |
package.json |
name, version |
node -e "const m = require('./.claude-plugin/plugin.json'); console.log(JSON.stringify(m, null, 2))"
node -e "const m = require('./.cursor-plugin/plugin.json'); console.log(JSON.stringify(m, null, 2))"
node -e "const m = require('./.claude-plugin/marketplace.json'); console.log(JSON.stringify(m, null, 2))"
node -e "const m = require('./package.json'); console.log(m.name, m.version)"
1b. Version Sync
Compare version across all manifests — all must match exactly:
| File | Field |
|---|---|
.claude-plugin/plugin.json |
version |
.cursor-plugin/plugin.json |
version |
package.json |
version |
1c. Hook Registration Cross-Reference
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.
- 1mo ago First seen · 408 lines · 28 tokens per session scan B bd7fb1a18b3d
plugin-qa is an agent published in the GitHub repository iBrain-BVBA/gutt-claude-code-plugin (5 stars, last pushed 1mo ago), licensed MIT. It adds 28 tokens to every session and 3,199 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads mcp configuration). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
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…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.