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 commands/orinks/accessiweather/qa-testergit clone --depth 1 https://github.com/Orinks/AccessiWeatherWrote 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/orinks/accessiweather/qa-tester)<a href="https://agentmods.dev/commands/orinks/accessiweather/qa-tester"><img src="https://agentmods.dev/badge/commands/orinks/accessiweather/qa-tester.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.00010 | $0.01556 |
| Opus 5 | $0.00005 | $0.00778 |
| Sonnet 5 | $0.00002 | $0.00311 |
| Haiku 4.5 | $0.00001 | $0.00156 |
Grade A, and why
qa-tester scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
**Good:** Testing API server: 1) Check port 3000 free. 2) Start server in tmux. 3) Poll for "Listening on port 3000" (30s timeout). 4) Send curl request. 5) Capture output, verify 200 response. 6) Kill session. All with How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unit tests verify code logic; QA testing verifies real behavior. These rules exist because an application can pass all unit tests but still fail when actually run. Interactive testing in tmux catches startup failures, integration issues, and user-facing bugs that automated tests miss. Always cleaning up sessions prevents orphaned processes that interfere with subsequent tests.
<ask_gate>
- Default to outcome-first, evidence-dense outputs; include the result, evidence, validation or uncertainty, and stop condition without padding.
- Treat newer user task updates as local overrides for the active task thread while preserving earlier non-conflicting criteria.
- If correctness depends on more reading, inspection, verification, or source gathering, keep using those tools until the test report is grounded. </ask_gate>
<execution_loop> <success_criteria>
- Prerequisites verified before testing (tmux available, ports free, directory exists)
- Each test case has: command sent, expected output, actual output, PASS/FAIL verdict
- All tmux sessions cleaned up after testing (no orphans)
- Evidence captured: actual tmux output for each assertion
- Clear summary: total tests, passed, failed </success_criteria>
<verification_loop>
- Default effort: medium (happy path + key error paths).
- Comprehensive (THOROUGH tier): happy path + edge cases + security + performance + concurrent access.
- Stop when all test cases are executed and results are documented.
- Continue through clear, low-risk next steps automatically; ask only when the next step materially changes scope or requires user preference. </verification_loop>
<tool_persistence>
- Use Bash for all tmux operations:
tmux new-session -d -s {name},tmux send-keys,tmux capture-pane -t {name} -p,tmux kill-session -t {name}. - Use wait loops for readiness: poll
tmux capture-panefor expected output ornc -z localhost {port}for port availability. - Add small delays between send-keys and capture-pane (allow output to appear).
- Prefer
omx sparkshellas an optional operator aid for noisy verification commands and tmux-pane summarization when compact inspection helps, but it does not replace rawtmux capture-paneevidence for PASS/FAIL assertions. - Use raw shell and direct
tmux capture-panewhen exact pane output or low-level debugging fidelity is required, or whenomx sparkshellis ambiguous/incomplete. </tool_persistence> </execution_loop>
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.
- 4d ago First seen · 125 lines · 10 tokens per session scan A 5e8a183c3c4a
qa-tester is a command published in the GitHub repository Orinks/AccessiWeather (24 stars, last pushed 10d ago), licensed MIT. It adds 10 tokens to every session and 1,556 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.