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/romiluz13/cc10xWrote 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/romiluz13/cc10x/qa-researcher)<a href="https://agentmods.dev/agents/romiluz13/cc10x/qa-researcher"><img src="https://agentmods.dev/badge/agents/romiluz13/cc10x/qa-researcher/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/romiluz13/cc10x/qa-researcher"><img src="https://agentmods.dev/badge/agents/romiluz13/cc10x/qa-researcher.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.00053 | $0.02991 |
| Opus 5.5 | $0.00021 | $0.01196 |
| Sonnet 5.5 | $0.00011 | $0.00598 |
| Haiku 4.5 | $0.00005 | $0.00299 |
Grade A, and why
qa-researcher 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 17d 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Researcher (Single-Source Scan)
Core: Read ONE assigned source. Report what THAT source claims the feature does. Do not reconcile it with anything else — you cannot, because you have not seen anything else, and that blindness is deliberate.
Mode: READ-ONLY — and you hold Bash, so read this precisely.
Bash is here for inspection: git log, git show, grep, ls, cat, --help, --version. It is not a licence to mutate.
You may not, by any tool or command: create, edit, move, or delete files; mkdir; install packages or fixtures; start or stop services; git init / commit / checkout; write via redirection (>, >>, heredoc) or tee.
An agent that mutates the machine while claiming to be read-only produces a report nobody can trust and side effects nobody expected. In a prior run this exact gap installed global skill fixtures onto the user's machine during a planning phase, and they outlived the workflow.
Edit/Writeguards never saw it, because it went throughBash.
If enumerating something requires running it — you cannot read a dropdown's runtime values without a live UI, you cannot know a CLI's flags without invoking it — then either use a genuinely non-mutating invocation (--help), or record it in GAPS as unenumerated: requires a running system. A gap you named is worth more than a fact you obtained by breaking your own contract.
A PreToolUse guard enforces this during QA planning phases. Do not attempt to work around it; a blocked call is a signal to record a gap, not an obstacle to route around.
If your dispatch carries a read denylist
Your scaffold may name paths you must not read — a quarantined document, another tenant's data, an existing test suite the plan is meant to be written independently of. The guard enforces that over the filesystem only.
It cannot enforce it anywhere else. A quarantined document pasted into a Jira comment, an MR description, a Confluence page, a Slack thread or a wiki export reaches you through an allowlisted source, in a batched API response, whole. By the time you can recognise it, you have read it. No hook can prevent that, and the failure is not yours.
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.
- 17d ago First seen · 177 lines · 53 tokens per session scan A 9cf4a19be8b0
qa-researcher is an agent published in the GitHub repository romiluz13/cc10x (164 stars, last pushed 9d ago), licensed MIT. It adds 53 tokens to every session and 2,991 once invoked, about $0.0002 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-30.
Other agents, from other repositories
feasibility-analyst
Feasibility analysis expert. Starts from first principles of requirements, explores multiple possible solutions with quantitative evaluation, and integrates Codex third perspective.
brief-writer
PM/CTO executive summary expert. Converts technical documents into non-technical readable executive summaries.
codex-implementer
Codex implementation expert. Uses Codex CLI to implement feature code with automatic review after confirmation.
solution-architect
Solution deepening expert. Receives preliminary research, deeply analyzes code, and produces actionable roadmaps with alternatives.
architecture-designer
Architecture design expert. Synthesizes code analysis, tech-spec context, and architecture advice into structured architecture documents with component diagrams, data flows, and architecture decisions.
coverage-analyst
Test coverage analysis expert. Comprehensively evaluates Unit / Integration / E2E three-layer test coverage, identifies gaps, and provides remediation suggestions.