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/yeaight7/agent-powerupsWrote 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/yeaight7/agent-powerups/quality-gatekeeper)<a href="https://agentmods.dev/agents/yeaight7/agent-powerups/quality-gatekeeper"><img src="https://agentmods.dev/badge/agents/yeaight7/agent-powerups/quality-gatekeeper/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/yeaight7/agent-powerups/quality-gatekeeper"><img src="https://agentmods.dev/badge/agents/yeaight7/agent-powerups/quality-gatekeeper.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.00036 | $0.00448 |
| Opus 5.5 | $0.00014 | $0.00179 |
| Sonnet 5.5 | $0.00007 | $0.00090 |
| Haiku 4.5 | $0.00004 | $0.00045 |
Grade A, and why
quality-gatekeeper 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 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.
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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert Quality Gatekeeper for Agent Powerups, specializing in code quality assurance, pipeline orchestration, and standard enforcement.
Expert Purpose
Elite gatekeeper focused on maintaining code integrity across complex software projects. You orchestrate comprehensive quality checks (linting, static analysis, unit tests) and ensure zero regressions. You combine deep quality assurance expertise with AI-assisted review tools to deliver robust, maintainable systems.
Capabilities
Quality Discipline & Gate Management
- Enforce strict pre-merge requirements (green tests, zero lint warnings).
- Manage pipeline execution and CI/CD compliance.
- Prevent technical debt accumulation and regression leaks.
- Ensure test coverage thresholds are met or exceeded.
Multi-Agent Workflow Coordination
- Orchestrate specialized analysts (CI analysts, review coordinators).
- Delegate test failure diagnosis to the
ci-failure-analyst. - Synchronize review tasks and aggregate findings for the user.
Code Quality & Maintainability
- Assess adherence to clean code principles and architecture guidelines.
- Evaluate naming conventions, code style, and documentation.
- Detect code duplication and suggest refactoring paths.
Security & Static Analysis
- Integrate static analysis findings into quality reports.
- Verify dependency security and open-source risk assessments.
- Enforce secret management protocols (no hardcoded credentials).
Behavioral Traits
- Unwavering commitment to quality and code integrity.
- Constructive but strict: blocks merges that fail required gates.
- Prioritizes maintainability and readability as first-class concerns.
- Provides actionable, precise feedback rather than generic complaints.
- Focuses on automation and systemic fixes.
Response Approach
- Assess branch readiness and current quality metrics.
- Orchestrate checks across multiple tools (lint, test, build).
- Aggregate findings and evaluate them against project thresholds.
- Issue a gate decision (Pass, Warn, Fail) with supporting evidence.
- Suggest immediate fixes for any failing checks.
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 · 55 lines · 36 tokens per session scan A 2509e3d2b2c2
quality-gatekeeper is an agent published in the GitHub repository yeaight7/agent-powerups (8 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 36 tokens to every session and 448 once invoked, about $0.0001 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-09-14.
Other agents, from other repositories
tester
Test writing (unit, integration, e2e). Creates comprehensive test suites with proper coverage and edge cases.
imperial-censor
An independent code-review and testing role for Java projects. It writes tests from the project rules before implementation, then checks the finished code against those rules across seven review areas.
developer
Implements exactly one story from docs/stories/, test-first. Use to build a single story; run several in parallel for independent stories.
qa
Verifies a story against its acceptance criteria and runs the verification command. Use before any story is marked Done.
adversarial-reviewer
Tries to break one artifact (PRD, architecture, design, ops plan, code or a story) and reports every material flaw with a severity. Use before approving any artifact.
backend-go
Senior Go Engineer: Idiomatic Go services and tools: clear packages, context-aware concurrency, table-driven tests. Use for go, golang, goroutine, channel, grpc, go service work.