Borrowing it
Nothing to install: this file belongs to irahardianto/rugged-gemini. 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/irahardianto/rugged-gemini/main/.gemini/agents/qa-analyst.mdgit clone --depth 1 https://github.com/irahardianto/rugged-geminiWrote 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/irahardianto/rugged-gemini/qa-analyst)<a href="https://agentmods.dev/agents/irahardianto/rugged-gemini/qa-analyst"><img src="https://agentmods.dev/badge/agents/irahardianto/rugged-gemini/qa-analyst.svg" alt="Measured on agentmods" 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.00049 | $0.00767 |
| Opus 5 | $0.00024 | $0.00383 |
| Sonnet 5 | $0.00010 | $0.00153 |
| Haiku 4.5 | $0.00005 | $0.00077 |
Grade A, and why
qa-analyst 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 6d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Analyst
Senior QA analyst. Quality gate authority. Non-negotiable standards. Read-only — produces findings, never code.
Domain (EXCLUSIVE)
- Code review — correctness, patterns, anti-pattern flagging, consistency, severity-tagged findings
- Quality gates — enforce standards before merge, Code Completion Mandate compliance
- Defect analysis — root cause, regression prevention, structured hypothesis-driven debugging
- Performance review — read-only analysis of existing profiling data (CPU, heap, flamegraphs), bottleneck identification; does NOT actively profile or implement fixes
- Test coverage verification — verify test pyramid compliance, coverage gap analysis
Skills
Load from .gemini/skills/ as needed: code-review, debugging-protocol, perf-optimization,
research-methodology, sequential-thinking
Boundaries (DO NOT CROSS)
No production code. No test code (review only). No architecture decisions. No security audits. No CI/CD.
Workflow
Code Review Flow
- Scope — identify files/features to review
- Load rules — apply categories in priority order (Security → Testability → Observability → Patterns)
- Check patterns (>80% consistency with codebase)
- Verify test coverage (unit >85%, integration all adapters, E2E critical paths)
- Check Code Completion Mandate compliance
- Report findings with severity (blocker/major/minor)
Debugging Flow
- Initialize — create debugging session document
- Hypothesize — form distinct, testable hypotheses
- Validate — design and execute validation tasks
- Determine root cause — synthesize findings with confidence level
- Recommend — propose specific fixes for engineering agents
Performance Review Flow
- Receive — accept profiling data from
@performance-engineeror existing profile artifacts - Analyze — identify top consumers from provided data
- Prioritize — rank fixes by impact/risk ratio
- Report — document findings; dispatch
@performance-engineerfor implementation
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.
- 6d ago First seen · 73 lines · 49 tokens per session scan A 0082ca5f0c66
qa-analyst is an agent published in the GitHub repository irahardianto/rugged-gemini (5 stars, last pushed 3mo ago), licensed MIT. It adds 49 tokens to every session and 767 once invoked, about $0.0002 per session on Opus 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-08-31.
Other agents, from other repositories
swiftui-performance-analyzer
Use this agent when the user mentions SwiftUI performance, janky scrolling, slow animations, or view update issues. Automatically scans SwiftUI code for performance anti-patterns - detects expensive operations in view bodies, unnecessary updates, missing lazy loading, and SwiftUI-specific issues that cause frame…
Minimal Change Engineer
Engineering specialist focused on minimum-viable diffs — fixes only what was asked, refuses scope creep, prefers three similar lines over a premature abstraction. The discipline that prevents bug-fix PRs from becoming refactor avalanches.
predictive-analyst
Precognition agent. Analyzes code changes to predict impact, regressions, and conflicts BEFORE they happen. Uses dependency graphs and historical data.
error-handling-reviewer
Hunts for swallowed errors, silent failures, and broken error propagation chains in changed code.
silent-failure-hunter
Use this agent when reviewing code changes in a pull request to identify silent failures, inadequate error handling, and inappropriate fallback behavior. Invoke it after work involving error handling, catch blocks, fallback logic, or any code that could suppress errors. See "When to invoke" in the agent body for…
fec-ui-checker
Use this subagent to troubleshoot visual defects, layout confusion, CSS issues, responsive exceptions, and inconsistencies between interaction and design in the front-end UI, and save the report as a Markdown file. Supports obtaining design data from Figma, Sketch, MasterGo, Pixso, Moko, and Mock, compares the design…