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/TechGardenCode/naive-userWrote 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/commands/techgardencode/naive-user/naive-test)<a href="https://agentmods.dev/commands/techgardencode/naive-user/naive-test"><img src="https://agentmods.dev/badge/commands/techgardencode/naive-user/naive-test/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/commands/techgardencode/naive-user/naive-test"><img src="https://agentmods.dev/badge/commands/techgardencode/naive-user/naive-test.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.00018 | $0.00218 |
| Opus 5.5 | $0.00007 | $0.00087 |
| Sonnet 5.5 | $0.00004 | $0.00044 |
| Haiku 4.5 | $0.00002 | $0.00022 |
Grade A, and why
naive-test 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.
What it actually says
Run the naive-user skill against the app named in $ARGUMENTS, or, if none is
given, the app in naive-user.config.json.
Invoke the skill and follow it exactly: read naive-user.config.json, make sure the app is
running, sign in via the configured auth steps, then explore the live UI as an uninformed
first-time user, source-blind, producing an updated mental model and a dated findings
report under qa/naive-user/<app>/.
This needs the Playwright MCP server (browser tools). See the project README if the browser_*
tools are not available. Run it on demand while developing, or dispatch it as a subagent to run
in parallel. It complements scripted end-to-end tests: those assert known flows, this discovers
unknown gaps.
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 First seen · 18 lines · 18 tokens per session scan A 301729b9181f
naive-test is a command published in the GitHub repository TechGardenCode/naive-user (1 stars, last pushed 2mo ago), licensed MIT. It adds 18 tokens to every session and 218 once invoked, about $0.0001 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-08-31.
Other commands, from other repositories
qawolf-cli
Manage QA Wolf through the qawolf CLI. Use when asked to create, update, or list coverage requests, bug reports, or maintenance reports; start a run of flows or tags on the QA Wolf platform or read a run's results; list, set, or delete environment variables; manage environments, flows, or tags; run or list flows…
ui-aqa-flow-selector-identification
Phase 4 Selector Identification of ui-aqa-flow.
ui-aqa-flow-selector-implementation
Phase 5 Selector Implementation of ui-aqa-flow.
verify-pr
Verify a PR's frontend changes through browser automation.
record
Record browser actions into a test definition.
qa
Dispatch a verifiable browser task to the qa-tester subagent. Use for regression checks, smoke tests, and any task with a clean pass/fail outcome. Supports an EXHAUSTIVE mode that verifies every control behind an honesty gate.