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 blueberrycongee/termcanvas --skill qagit clone --depth 1 https://github.com/blueberrycongee/termcanvasWrote 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/blueberrycongee/termcanvas/qa)<a href="https://agentmods.dev/skills/blueberrycongee/termcanvas/qa"><img src="https://agentmods.dev/badge/skills/blueberrycongee/termcanvas/qa/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/blueberrycongee/termcanvas/qa"><img src="https://agentmods.dev/badge/skills/blueberrycongee/termcanvas/qa.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Memory Poisoning · line 47 Skill attempts to fill the context window with filler content, displacing legitimate instructions and safety constraints. This can degrade agent performance or bypass safety boundaries.Fix: Implement context-window management that detects and rejects padding or stuffing attempts. Prioritize system instructions over user-injected content.
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.00050 | $0.00839 |
| Opus 5.5 | $0.00020 | $0.00336 |
| Sonnet 5.5 | $0.00010 | $0.00168 |
| Haiku 4.5 | $0.00005 | $0.00084 |
Grade A, and why
qa 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 1mo 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA
Browser-based QA testing with the browse CLI. Test real user flows, capture
visual evidence, and fix issues with atomic commits.
Phase 0: Setup
- Verify browse is available:
browse status - If not found, report error — browse binary must be installed
- Get the target URL from the task description or ask the user
Phase 1: Orient
- Navigate to the target:
browse goto <url> - Take a baseline snapshot:
browse snapshot -i - Check console for errors:
browse console - Extract navigation links:
browse links - Build a site map of pages to test (limit to 10 most important pages)
Phase 2: Page-by-Page Audit
For each page in the site map:
- Navigate:
browse goto <page-url> - Snapshot interactive elements:
browse snapshot -i - Check console for errors:
browse console - Screenshot for evidence:
browse screenshot <page-name>.png - Note issues found: broken links, console errors, missing elements, layout problems visible in snapshot
Phase 3: User Flow Testing
Test the primary user flows (signup, login, checkout, etc.):
- Identify the flow steps from the snapshot
- Execute each step using refs:
browse click @e3— click buttons/linksbrowse fill @e5 "[email protected]"— fill inputsbrowse select @e7 "option-value"— select dropdownsbrowse press Enter— submit forms
- After each step, snapshot and verify the expected outcome
- Screenshot at each step for evidence
Phase 4: Health Score
Rate the site on a 0-10 scale across these dimensions:
- Console health: errors / warnings count
- Link health: broken links / total links
- Interactivity: do buttons and forms work?
- Visual completeness: are there missing images, broken layouts?
Report format:
Health Score: 7/10
- Console: 9/10 (2 warnings, 0 errors)
- Links: 8/10 (1 broken link out of 45)
- Interactivity: 6/10 (signup form submit fails silently)
- Visual: 5/10 (hero image 404, footer misaligned on mobile)
Phase 5: Fix 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.
- 1mo ago First seen · 105 lines · 50 tokens per session scan A 98b8f1732fe7
qa is a skill published in the GitHub repository blueberrycongee/termcanvas (413 stars, last pushed 4mo ago), licensed MIT. It adds 50 tokens to every session and 839 once invoked, about $0.0002 per session on Opus 5.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-30.
Other skills, from other repositories
webapp-testing
Start/reuse a local app, wait for readiness, inspect rendered state/console/network, act from observed selectors, and verify with evidence.
web-app-qa
Test a web app the way a real user would: click through the main flows, try odd inputs, watch for errors, and keep screenshots as proof. You get a bug report ranked by how serious each problem is.
qa
Browser-based QA verification. Launches a real browser, navigates the app, clicks buttons, fills forms, and tests user flows. Works as a standalone skill or as a phase end condition in campaigns. Requires Playwright (optional dependency, graceful skip if not installed).
run-dashboard-e2e-local-changes
Run Playwright E2E (tests/e2e/) against the docker/ all-in-one harness so it reflects LOCAL code changes, not a stale cached image.
chrome-automation
A browser-automation toolkit for controlling Chrome to visit pages, interact with forms, collect data, run tests, and create screenshots or PDFs.
browser-check
Drive a real browser and come back with a MEASUREMENT rather than an impression - console errors and >=400 responses as counts, computed styles as JSON when appearance is disputed. Use when work touches UI, when a review must verify one, or when fidelity-gate asks for its measurement.