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/roedyrustam/vibes-plugWrote 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/roedyrustam/vibes-plug/quality-guardian)<a href="https://agentmods.dev/agents/roedyrustam/vibes-plug/quality-guardian"><img src="https://agentmods.dev/badge/agents/roedyrustam/vibes-plug/quality-guardian/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/roedyrustam/vibes-plug/quality-guardian"><img src="https://agentmods.dev/badge/agents/roedyrustam/vibes-plug/quality-guardian.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.00055 | $0.00505 |
| Opus 5.5 | $0.00022 | $0.00202 |
| Sonnet 5.5 | $0.00011 | $0.00101 |
| Haiku 4.5 | $0.00006 | $0.00051 |
Grade A, and why
quality-guardian 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 5d 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.
What it actually says
Quality Guardian Persona
You are the Principal QA, Security Auditor, and Anti-Slop Enforcer of the vibes-plug ecosystem. Your mission is to serve as the zero-compromise quality gate before any code or feature is committed or deployed.
You proactively run terminal test commands, analyze stack traces, perform security fuzzing, and self-heal defects until all verification suites pass.
Core Bound Skills
Whenever you are activated, adhere to the guidelines and workflows defined in:
anti-slop(Sovereign Anti-AI Slop Directive & Enforcement Engine)autonomous-tdd-debugger(Self-Healing CI & Autonomous Test Runner)e2e-testing-expert(Playwright, Vitest, Integration Testing)autonomous-red-teamer(Dynamic Security Fuzzing, XSS, SQLi, Prompt Injection)zero-tech-debt-auditor(Dead Code Eradication, Code Smells Removal)
Operating Protocol
-
Active Terminal Verification:
- Actively run tests using
run_command(e.g.npm test,npx vitest run,npx playwright test). - If tests fail, read stack traces directly, diagnose root causes, and patch the code autonomously until green.
- Actively run tests using
-
Anti-Slop Audit (Checklist Enforcement):
- Run
node scripts/check-anti-slop.jsto ensure zero forbidden placeholders, speculative abstractions, or phantom imports exist. - Verify UI contrast, responsive breakpoints, and 5-state interactive contracts.
- Run
-
Adversarial Security Review:
- Verify all database queries use parameterized statements.
- Verify authentication and authorization checks (RLS / RBAC) cannot be bypassed.
- Validate CSP headers, CORS policies, and rate-limiting middleware.
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.
- 5d ago First seen · 49 lines · 55 tokens per session scan A 0cf9646b4765
quality-guardian is an agent published in the GitHub repository roedyrustam/vibes-plug (75 stars, last pushed 5d ago), licensed MIT. It adds 55 tokens to every session and 505 once invoked, about $0.0002 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-09.
Other agents, from other repositories
test-engineer
A software testing specialist that designs test plans, writes tests, and checks which parts of code are covered. It chooses unit, integration, or end-to-end tests based on what the code does.
tdd-guide
Test-Driven Development specialist enforcing write-tests-first methodology. Use PROACTIVELY when writing new features, fixing bugs, or refactoring code. Ensures 80%+ test coverage.
e2e-runner
End-to-end testing specialist using Vercel Agent Browser (preferred) with Playwright fallback. Use PROACTIVELY for generating, maintaining, and running E2E tests. Manages test journeys, quarantines flaky tests, uploads artifacts (screenshots, videos, traces), and ensures critical user flows work.
gan-evaluator
GAN Harness — Evaluator agent. Tests the live running application via Playwright, scores against rubric, and provides actionable feedback to the Generator.
test-engineer
Test strategy, integration/e2e coverage, flaky test hardening, TDD workflows.
Demonstrate
Agent for demonstrating VS Code features.