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 agents/abs1294/fulin-claude-plugins/qa-engineergit clone --depth 1 https://github.com/abs1294/fulin-claude-pluginsWrote 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/abs1294/fulin-claude-plugins/qa-engineer)<a href="https://agentmods.dev/agents/abs1294/fulin-claude-plugins/qa-engineer"><img src="https://agentmods.dev/badge/agents/abs1294/fulin-claude-plugins/qa-engineer.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.00198 | $0.02356 |
| Opus 5 | $0.00099 | $0.01178 |
| Sonnet 5 | $0.00040 | $0.00471 |
| Haiku 4.5 | $0.00020 | $0.00236 |
Grade A, and why
qa-engineer 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 3d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 3d ago First seen · 97 lines · 198 tokens per session scan A ffebc83552bd
qa-engineer is an agent published in the GitHub repository abs1294/fulin-claude-plugins (2 stars, last pushed 2d ago), with no licence file. It adds 198 tokens to every session and 2,356 once invoked, about $0.0010 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 agents, from other repositories
browser-verifier
Uses Playwright MCP to smoke-test the running application in a browser. Dispatched by /ship for pass/fail verification.
inventory-javascript-mapper
Discovers JavaScript-rendered pages, SPA client-side routes, dynamically-loaded scripts, AJAX-triggered endpoints, and hidden features invisible to standard scanners. Uses Playwright headless browser automation to execute JavaScript and extract framework route registries (React Router, Vue Router, Angular). Follows…
opentable-agent
OpenTable-specific agent. Handles venue search (live via browser automation) and hand-off to the OpenTable booking URL for the user to confirm in their own browser.
dast-crawler
PlaywrightベースのURL自動発見エージェント。動的生成されるエンドポイントを検出。.
dev-agent-visual-qa
Read-only. Browser-based QA using the project's existing Playwright setup -- runs existing Playwright tests, inspects screenshots/console/network evidence, checks functional flows, visual layout, responsive breakpoints, UX states, and basic accessibility. Only invoked when Playwright is genuinely available in the…
ui-tester
ON-DEMAND browser smoke testing using Playwright MCP. This agent is NOT part of the automatic upgrade pipeline. Use it manually when you want to visually verify the app works after an upgrade. Triggers: "test the ui", "browser test", "smoke test", "playwright test", "check if app works in browser", "visual check"…