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 skills/agentiqa/agentiqa-plugin/agentiqa-testnpx skills add Agentiqa/agentiqa-plugin --skill agentiqa-testgit clone --depth 1 https://github.com/Agentiqa/agentiqa-pluginWhat 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.00131 | $0.03250 |
| Opus 5 | $0.00066 | $0.01625 |
| Sonnet 5 | $0.00026 | $0.00650 |
| Haiku 4.5 | $0.00013 | $0.00325 |
Grade A, and why
agentiqa-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 2d 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 — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agentiqa Test Skill
You have access to the agentiqa CLI, which drives an independent AI testing agent against web apps. It has two commands:
agentiqa run— execute a saved or local test plan: fixed, enumerated, repeatablesetup/action/verifysteps with per-step verification. Use for regression re-checks and any "verify these specific things" request.agentiqa explore— open-ended discovery: turn the agent loose to find bugs from the UI, no predefined script.
Choosing the command
Pick by whether the check is scripted:
- Fixed / enumerated / repeatable steps, or a regression re-check →
agentiqa run. You (or the user) already know the exact steps and expected outcomes.runexecutes a deterministic test plan and verifies each step. Prefer this whenever the request reads like a checklist (e.g. "log in, add the Pro plan to the cart, verify the total is $19"). - Open-ended discovery ("find bugs", "QA this page", "what's broken") →
agentiqa explore. No predefined steps; the agent decides what to try.
Rule of thumb: if you can write the steps down, use run; if you're asking the agent to go looking, use explore.
CRITICAL RULES — READ BEFORE DOING ANYTHING
- NEVER explore the codebase — do NOT run
ls,find,rg,cat, or read any source files. The agentiqa CLI is an external tool, not part of this repo. Go straight to Step 0. - ALWAYS use the global
agentiqaCLI — runagentiqa run .../agentiqa explore ...directly. NEVER runnode apps/cli/dist/cli.js,npx agentiqa, or any local build from the repo. The globally installed CLI has its own bundled Chromium and dependencies. - Follow the steps below IN ORDER — do not skip, reorder, or improvise.
How the agent works
The testing agent:
- Navigates the app visually (screenshots + actions), like a real user
- Has NO knowledge of the codebase — works purely from the UI
- Reports issues (explore) or per-step verdicts (run) with severity, category, confidence, and reproduction steps
- Self-terminates when done
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 274 lines · 131 tokens per session scan A 90007fd2dda5
agentiqa-test is a skill published in the GitHub repository Agentiqa/agentiqa-plugin (2 stars, last pushed 1mo ago), licensed MIT. It adds 131 tokens to every session and 3,250 once invoked, about $0.0007 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.
Other skills, from other repositories
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
test-conversion
Workflow for converting unit tests to browser tests for Project Bedrock. Invoke this when the user wants to remove complex Browser dependencies from tests.
agui-dotnet-cross-language-tests
Author cross-language interop tests that verify the AG-UI .NET SDK is wire-compatible with the TypeScript SDK — a Vitest TS client driving a C# CrossLanguage.TestServer over HTTP, both directions, including protobuf byte-parity against @ag-ui/proto. USE FOR: adding or modifying cross-language interop coverage…
cli-e2e-testcase-writer
Use when adding or updating Go CLI E2E coverage for one tests/clie2e/{domain} domain of the compiled lark-cli, especially when the work requires live --help or schema exploration, scenario-based clie2e.RunCmd workflows, and per-domain coverage.md maintenance.
harness-test-writer
Add regression test cases to the Bifrost provider harness (the Postman collection run via make run-provider-harness-test) based on a merged PR or a GitHub issue. Fetches the PR/issue, traces the affected wire path in the codebase, checks existing harness coverage, designs cases following harness conventions, inserts…
develop-web-game
Use when Codex is building or iterating on a web game (HTML/JS) and needs a reliable development + testing loop: implement small changes, run a Playwright-based test script with short input bursts and intentional pauses, inspect screenshots/text, and review console errors with rendergametotext.