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/nearform/lastlight/qa-testnpx skills add nearform/lastlight --skill qa-testgit clone --depth 1 https://github.com/nearform/lastlightWrote 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/nearform/lastlight/qa-test)<a href="https://agentmods.dev/skills/nearform/lastlight/qa-test"><img src="https://agentmods.dev/badge/skills/nearform/lastlight/qa-test.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.00051 | $0.01017 |
| Opus 5 | $0.00026 | $0.00508 |
| Sonnet 5 | $0.00010 | $0.00203 |
| Haiku 4.5 | $0.00005 | $0.00102 |
Grade A, and why
qa-test 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.
> background and exercising it with `curl` (status codes, response bodies, How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Test
Drive a target through a sequence of steps and report step-level pass/fail with evidence for each step. The deliverable is a QA report, not a single verdict — partial coverage with documented failures is the expected output.
This skill uses the building skill for installing dependencies and running the repo's build/run commands in the sandbox.
Scope (text-evidence path). In the default text phase the sandbox agent has bash, file read, and the github tools — no browser, no screenshots. QA a CLI directly, or a web service by starting its dev-server in the background and exercising it with
curl(status codes, response bodies, headers). Capture stdout/stderr, exit codes, and log excerpts as per-step evidence. Driving a real browser UI and attaching screenshots is the separatebrowser-qaskill, staged only in the gated browser phase running on the docker QA image (Playwright + Chromium). If that skill isn't in your catalogue, mark a step that genuinely needs rendered-UI interaction BLOCKED with the reason rather than faking a result — the browser phase will pick it up when available.
Parse the target
The Context block gives you what to test and (usually) a PR/issue. The target may be:
- A CLI command (
my-cli --flag, a subcommand) → run it directly. - A local web service (an app the repo serves on a port) → start it, hit it
with
curl. - A PR reference + focus area → read the diff and infer the flow that exercises what changed.
- A free-text flow ("create a project, then list it") → infer concrete steps.
When a PR/issue is given, read its description + diff (from the local checkout — see the building skill) to decide what's worth testing.
Define the steps
If the request specifies steps, use them. Otherwise design a reasonable flow:
- CLI: invoke with valid input → assert output/exit code → invoke an edge case (bad flag, missing arg) → assert it's handled → done.
- Web service: start the server → wait until it's ready → hit the primary endpoint(s) → assert status + body → hit an error case → assert handling → stop the server.
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 · 98 lines · 51 tokens per session scan A bde6c9a9074d
qa-test is a skill published in the GitHub repository nearform/lastlight (22 stars, last pushed 7d ago), licensed MIT. It adds 51 tokens to every session and 1,017 once invoked, about $0.0003 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 skills, from other repositories
penguin-harness-manual-test
Use when standing PenguinHarness up to try a change by hand — launching the Web App, the desktop shell, the landing page or the docs site to click through it, screenshot it, or reproduce a report. Covers the four dev entry points and their ports, which data root each writes to, and the four ways a healthy setup looks…
local-test
Build, run, and test IronClaw locally using Docker containers and Chrome MCP browser automation.
button-check
Traverse all interactive elements on the page — click clickables.
web-ui-test
Test the IronClaw web UI using the Claude for Chrome browser extension.
webqa
Use WebQA to test websites, web pages, URLs, login flows, search flows, forms, navigation, and core user journeys with an AI browser QA agent.
scout
Safely explore and adversarially test an authorized HTTP API using the scout CLI, with or without an OpenAPI spec. Use when asked to test, probe, validate, or explore an API, whether or not an OpenAPI/Swagger spec is available. Scout is the harness; you are the operator.