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 skills add dangnhit/qa-tester --skill evidence-collectorgit clone --depth 1 https://github.com/dangnhit/qa-testerWrote 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/skills/dangnhit/qa-tester/evidence-collector)<a href="https://agentmods.dev/skills/dangnhit/qa-tester/evidence-collector"><img src="https://agentmods.dev/badge/skills/dangnhit/qa-tester/evidence-collector/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/skills/dangnhit/qa-tester/evidence-collector"><img src="https://agentmods.dev/badge/skills/dangnhit/qa-tester/evidence-collector.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.00037 | $0.00636 |
| Opus 5 | $0.00018 | $0.00318 |
| Sonnet 5 | $0.00007 | $0.00127 |
| Haiku 4.5 | $0.00004 | $0.00064 |
Grade A, and why
evidence-collector 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 12d 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
Evidence collector
Execution kind: runtime-backed. Read safety, artifact contracts, browser adapters, and recovery. Ask the runtime to capture and redact evidence; record an evidence gap instead of persisting unsafe pixels or secrets.
Resolve ./node_modules/.bin/qa-skill, then qa-skill on PATH; otherwise stop with setup guidance. Never use remote npx.
Example — full-workflow run producing this skill's evidence:
QA_SKILL="${PWD}/node_modules/.bin/qa-skill"; [ -x "$QA_SKILL" ] || QA_SKILL="$(command -v qa-skill)" || exit 1
"$QA_SKILL" runtime verify --range ">=1.0.0 <2.0.0"
SOURCE_RUN_ID="$("$QA_SKILL" workflow bootstrap --root . --environment-file environment.json --requirement-file drafts/requirements.json --plan-file drafts/plan.json --test-case-file drafts/case.json --coverage-file drafts/coverage.json | node -p 'JSON.parse(require("fs").readFileSync(0, "utf8")).runId')"
"$QA_SKILL" workflow scaffold --root . --mode execute --output execute-workflow.json --source-root . --source-run-id "$SOURCE_RUN_ID"
"$QA_SKILL" workflow run --input execute-workflow.json
PowerShell:
$QaSkill = Join-Path $PWD "node_modules/.bin/qa-skill.cmd"
if (-not (Test-Path $QaSkill)) { $QaSkill = (Get-Command qa-skill -ErrorAction Stop).Source }
& $QaSkill runtime verify --range ">=1.0.0 <2.0.0"
$Bootstrap = (& $QaSkill workflow bootstrap --root . --environment-file environment.json --requirement-file drafts/requirements.json --plan-file drafts/plan.json --test-case-file drafts/case.json --coverage-file drafts/coverage.json | ConvertFrom-Json)
& $QaSkill workflow scaffold --root . --mode execute --output execute-workflow.json --source-root . --source-run-id $Bootstrap.runId
& $QaSkill workflow run --input execute-workflow.json
Expected outputs are redacted evidence descriptors/binaries or evidence-gap artifacts — see recovery for what a gap means. Example — full run: scaffold with --mode full --source-root . --source-run-id "$SOURCE_RUN_ID" (the same captured source run ID), then run the returned JSON.
Example — full run: retain registered evidence or gaps for runtime defect and report generation after validation.
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.
- 12d ago First seen · 36 lines · 37 tokens per session scan A 9f5f14ed0514
evidence-collector is a skill published in the GitHub repository dangnhit/qa-tester (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 37 tokens to every session and 636 once invoked, about $0.0002 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
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; request automation of…
playwright-expert
Expert in Playwright E2E testing framework, auto-waiting mechanisms, test generation, trace viewer, and CI/CD integration. Use when the user mentions testing, end-to-end tests, QA, automation, end-to-end testing, or test automation, or when the task involves Playwright Framework, Test Organization, Advanced Features…
test-review
A review checklist for newly written or changed automated tests using TypeScript and Playwright. Playwright is a tool for testing web browsers, and automated tests check software without repeating the steps by hand.
e2e-setup
Set up Playwright e2e automation tailored to this team and app. Probes the running app (auth mechanism, API surface, spec availability), interviews with recommendations instead of open questions, scaffolds the playwright/ folder, and records every decision in playwright/AUTOMATION.md for the other e2e skills to read.…
test-cases
Generate test cases from a Jira ticket's acceptance criteria. Produces e2e test scenarios (steps and expected results, no code) and a unit test checklist for developers. Test cases map back to requirements for traceability. Use when: "write test cases", "generate tests", "e2e tests for PROJ-789", "test cases for this…
verify-fix
Re-test a bug fix after a developer resolves it. Pulls the original bug from Jira, re-executes the repro steps in the browser, checks for regressions, and updates the bug status. The final step in the SDT workflow before a ticket moves to Done. Use when: "verify fix", "retest", "is this fixed?", "check BUG-123"…