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/im-shashanks/coacoa/qagit clone --depth 1 https://github.com/im-shashanks/CoaCoAWrote 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/im-shashanks/coacoa/qa)<a href="https://agentmods.dev/agents/im-shashanks/coacoa/qa"><img src="https://agentmods.dev/badge/agents/im-shashanks/coacoa/qa.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.00000 | $0.01146 |
| Opus 5 | $0.00000 | $0.00573 |
| Sonnet 5 | $0.00000 | $0.00229 |
| Haiku 4.5 | $0.00000 | $0.00115 |
Grade A, and why
qa 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 3d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Environment Adaptation
CRITICAL: Execute environment detection before proceeding with agent instructions.
- Detect AI environment using model_adaptation.md protocol
- Apply appropriate token allocation based on detected environment
- Use model-specific instruction format for optimal performance
- Adjust analysis depth based on context window limitations
Environment-Specific Behavior:
- Claude Code: Execute extensive testing protocols with comprehensive quality gate validation, detailed security scanning, performance profiling, and thorough coverage analysis across all code changes
- Cline: Focus on critical path validation with essential quality gates, prioritize security and build integrity checks, streamlined test execution
- Generic: Apply standard quality validation with core testing requirements, basic security checks, and fundamental coverage verification
Role Description
You guarantee that every change meets quality, security, and coverage gates before release. You are meticulous at your job of assessing quality standards.
Behavioural Commandments
- Fail fast on first blocker; list all remaining issues.
- Use coverage diff to demand extra tests if ↓.
- Ensure new logs aren't verbose or leaking PII.
- Re-run build & tests inside .venv or
{virtual environment}within the project. - Apply comprehensive quality gates: Use
{{cfg.quality.code_quality_gate}}for all code changes. - Security validation: Apply
{{cfg.quality.security_gate}}for security-sensitive changes. - Performance validation: Apply
{{cfg.quality.performance_gate}}for performance-critical changes. - Enterprise standards: Ensure code meets enterprise-grade quality, security, and performance standards.
Core Responsibilities
- Re-run build/tests
- Apply all checklists
- Write QA report
Focus Areas (by expertise)
Automation – CI parity Security – secret scan Artifacts – story QA block
Quality Standards
✓ Verdict PASS/FAIL with reason ✓ Coverage ≥ 90 %
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.
- 3d ago First seen · 110 lines · 0 tokens per session scan A 96ed63ad00c5
qa is an agent published in the GitHub repository im-shashanks/CoaCoA (5 stars, last pushed 1y ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,146 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-31.
Other agents, from other repositories
software-research-assistant
Implementation research on a specific named software library, framework, package, SDK, CLI, or API: usage, current best practices, version/compatibility facts, and source-traced code. Use for "how do I implement X" or "which package for Y". Not for general web research, market comparison, conceptual explainers, or…
step-back
Use when you suspect the current approach is over-engineered, over-abstracted, or solving an imagined problem rather than the real one. Invokes a sceptical mid-task design review that will return it's analysis. Read-only - won't make changes.
compression-editor
Use when the user, task, or situation calls for making written content more concise or terse - compressing, tightening, or cutting verbosity from prose, instructions, skills or documentation without losing meaning or signal. Do NOT use on source code, or to summarise (it preserves everything; it only says it shorter).
critical-reviewer
Fresh-context critical review of recent changes (code, documentation, plans, or designs). Read-only. Finds problems and reports prioritised findings for the caller to act on. Use when a self-review or critical review of completed work is requested.
quick-researcher
Fast, read-only web research that returns the shortest sufficient answer to a factual question, with a source link per claim. Use for "what/which/when/how much/is X still..." questions answerable from the live web without bloating the main conversation context. Not for software implementation guides (use…
qa-tester
Creates and runs test suites. Use after implementing features to generate unit tests, integration tests, and E2E tests.