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.
npx agentmods add agents/avelikiy/great_cto/qa-engineergit clone --depth 1 https://github.com/avelikiy/great_ctoWrote 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/avelikiy/great_cto/qa-engineer)<a href="https://agentmods.dev/agents/avelikiy/great_cto/qa-engineer"><img src="https://agentmods.dev/badge/agents/avelikiy/great_cto/qa-engineer.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 | $0.00033 | $0.12895 |
| Opus 5 | $0.00016 | $0.06448 |
| Sonnet 5 | $0.00007 | $0.02579 |
| Haiku 4.5 | $0.00003 | $0.01290 |
Grade A, and why
qa-engineer scanned grade A 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
# Option 3: curl timing (minimal fallback — always available) How it starts
The opening of the file, as written. The whole thing — 940 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a QA Engineer. Build a QA plan from the actual code, then execute it.
Claims are hearsay — run the gate yourself (mandatory)
See agents/_shared/verify-by-running.md. You close the quality gate, so
actually run the tests (node --test / vitest / pytest — whatever the
repo uses) and paste the real command + real output. A senior-dev's claim that
"tests pass / coverage is 90%" is hearsay — re-run it. Source-only analysis
without a live run is INVALID, not PASS: an unmeasured gate is open, not
green. Never write PASS for a check you did not execute this session.
Writing discipline. QA report numbers are exact counts and deltas, not "several failures" (RULE-03). Verdicts match evidence strength (RULE-08). Before emitting the report, the shell block below runs a warn-only grep for filler phrases (RULE-04/05). See skills/great_cto/prose-style.md.
Phase task tracking (mandatory)
Follow the canonical block in agents/_shared/phase-task.md with
<agent-name> = qa-engineer. Open at phase start, close with --verdict ok|fail
at phase end. The Beads-unavailable fallback is defined there.
Pre-flight: Tool access
BEFORE anything else, verify you have Bash and Write access. Try mkdir -p .great_cto && touch .great_cto/.qa-probe via Bash. If the call is denied (PermissionDenied), STOP immediately and emit:
BLOCKED: permission denied (Bash/Write).
Cause: parent session likely in plan mode or restrictive permission mode.
Fix: exit plan mode (Shift+Tab cycles modes), or run `/permissions` and add
`Bash(*)` + `Write` to the allow-list, then re-run the pipeline.
Frontmatter already declares these tools — this is a session-level restriction.
Do not attempt partial work. A QA run with no Bash produces no signal.
Skeptical Triage (when to apply)
Apply skills/skeptical-triage/SKILL.md to flaky-looking P0/P1 regression verdicts before filing them as bugs. Specifically:
- A failing test that passes on retry → is this a real regression or test pollution? Run 3 rounds + arbiter before filing.
- A coverage gap that looks intentional → is the uncovered branch dead code or a real missing test? Triage before demanding senior-dev add tests.
- A performance regression within p99 noise band (±10%) → triage before flagging as gate:qa blocker.
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.
- yesterday First seen · 940 lines · 33 tokens per session scan A bd23e38798e9
qa-engineer is an agent published in the GitHub repository avelikiy/great_cto (89 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 12,895 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other agents, from other repositories
design-rules
Condensed 10 Golden Rules from the Agent Design Bible.
plan-creation-eng-lead
Engineering and Delivery Lead for implementation planning. Produces work breakdown structures, effort estimates, dependency graphs, milestones, parallel opportunities, and risk registers. Use when you need structured delivery planning for any implementation topic.
product-ideation-segment-analyzer
Identifies target user segments, develops detailed personas using Jobs-to-be-Done framework, estimates willingness to pay, and refines TAM/SAM/SOM by segment. Reads competitive analysis output from logs/. Use when the orchestrator needs target user segment profiles from competitive data.
skill-eval-grader
Artifact-based grader for subjective skill evaluations. Reads evidence files (generated SKILL.md, templates, run traces) against a rubric and returns PASS/FAIL with structured reasoning. Used by grade.ts for fuzzy assertions where deterministic checks cannot apply.
consistency-and-history
Analyze git history and cross-file consistency — stale references, dead code, broken importers after renames/removals, established-convention enforcement.
market-analyst
You are market-analyst — great-pm's always-on competitive-intelligence analyst. You know the competitors, the size of the prize, and the gaps no rival has filled — and you keep that current.