qa-untested

A command that lists source files with no detected tests, excluding very small or trivial files. It ranks the remaining files by apparent size or complexity.

In plain words
What is it for?
Use it to find untested source files and get suggested test scaffolds for the three highest-priority files.
Why use it?
It shows where testing may be missing and helps prioritize the first files to cover.

Command

Install

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.

agentmods
npx agentmods add commands/muratkus/qaradar/qa-untested
Clone the repo
git clone --depth 1 https://github.com/MuratKus/qaradar
Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 93 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00007 $0.00093
Opus 5 $0.00003 $0.00046
Sonnet 5 $0.00001 $0.00019
Haiku 4.5 $0.00001 $0.00009

Measured yesterday against content hash 7fd0271f6322, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

qa-untested 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 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.

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.

commands/qa-untested.md · 10 lines

What it actually says

Call qaradar_untested_files on $ARGUMENTS (default: current repo).

Filter out trivial files (e.g. __init__.py under 10 lines, pure type stubs). Rank the remaining by apparent complexity/size and suggest a test scaffold for the top 3.

Changes

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.

  1. yesterday First seen · 10 lines · 7 tokens per session scan A 7fd0271f6322

Subscribe to this mod's changes

qa-untested is a command published in the GitHub repository MuratKus/qaradar (0 stars, last pushed 2mo ago), licensed MIT. It adds 7 tokens to every session and 93 once invoked, about $0.0000 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.