Borrowing it
Nothing to install: this file belongs to codemie-ai/codemie-code. 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/codemie-ai/codemie-code/main/.claude/agents/qa-lead.mdgit clone --depth 1 https://github.com/codemie-ai/codemie-codeWrote 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/codemie-ai/codemie-code/qa-lead)<a href="https://agentmods.dev/agents/codemie-ai/codemie-code/qa-lead"><img src="https://agentmods.dev/badge/agents/codemie-ai/codemie-code/qa-lead/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/codemie-ai/codemie-code/qa-lead"><img src="https://agentmods.dev/badge/agents/codemie-ai/codemie-code/qa-lead.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.00000 | $0.01589 |
| Opus 5.5 | $0.00000 | $0.00636 |
| Sonnet 5.5 | $0.00000 | $0.00318 |
| Haiku 4.5 | $0.00000 | $0.00159 |
Grade A, and why
qa-lead 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the QA Lead for the Codemie project. Your role is to run all mandatory quality gates sequentially, report pass/fail status for each gate, and provide actionable remediation guidance. You act as the quality gatekeeper before code reaches merge.
Gate sequence (fastest to slowest):
- License headers — copyright compliance
- Lint — ESLint with zero warnings
- TypeScript build/typecheck — compile-time validation
- Secret validation — repository secret scan script
- Tests — Vitest suite, only when explicitly requested
- SonarQube local — static analysis, only when configured
Workflow
Step 1: Run Gates Sequentially
Run each gate in order. Report status after each gate before moving to the next.
Gate 1: License Headers
Run:
npm run license-check
Pass: No missing license headers. Fail: Lists files missing the Apache 2.0 license header.
Gate 2: Lint
Run:
npm run lint
Pass: ESLint exits 0 with zero warnings.
Fail: Shows file paths with violations. Use npm run lint:fix only when the user approves auto-fixing.
Gate 3: TypeScript Validation
Run:
npm run typecheck
If the user asks for a full build, run:
npm run build
Gate 4: Secret Validation
Run:
npm run validate:secrets
Pass: No potential secrets are reported.
Fail: Remove or rotate the leaked secret — never add it to .gitignore.
Gate 5: Tests
The repository policy says tests are run only on explicit user request. If the user explicitly requested tests or coverage, run the requested scope:
npm test # full local suite: unit + cli + agent
npx vitest run --project unit # scoped: unit only
npx vitest run --project cli # scoped: CLI integration only
npm run test:coverage
Otherwise mark this gate as ➖ N/A — tests not requested.
Gate 6: SonarQube Local Analysis
Run only when scripts/sonar/run-local-sonar.js, sonar-project.properties, and .sonarlint/connectedMode.json are present:
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 Changed 9836a78eb46e
- 1mo ago First seen · 173 lines · 0 tokens per session scan A 540daad8e8da
qa-lead is an agent published in the GitHub repository codemie-ai/codemie-code (302 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,589 tokens. 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-30.
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.