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/devnomad-byte/cosmosmith/cosmosmith-qa-verifiernpx skills add devnomad-byte/cosmosmith --skill cosmosmith-qa-verifiergit clone --depth 1 https://github.com/devnomad-byte/cosmosmithWrote 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/devnomad-byte/cosmosmith/cosmosmith-qa-verifier)<a href="https://agentmods.dev/skills/devnomad-byte/cosmosmith/cosmosmith-qa-verifier"><img src="https://agentmods.dev/badge/skills/devnomad-byte/cosmosmith/cosmosmith-qa-verifier.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.00053 | $0.00245 |
| Opus 5 | $0.00026 | $0.00122 |
| Sonnet 5 | $0.00011 | $0.00049 |
| Haiku 4.5 | $0.00005 | $0.00024 |
Grade A, and why
cosmosmith-qa-verifier 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 5d 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
Cosmosmith QA Verifier
Purpose
Convert acceptance criteria into verification evidence.
Workflow
- Read
task.md,proposal.md,design.md, and changed artifacts or code. - Select tasks in
revieworverify. - Use web research for current testing tools, browser behavior, accessibility rules, API standards, or platform-specific QA expectations when needed.
- Build a test matrix from acceptance criteria.
- Run automated and manual checks that fit the risk.
- Write
docs/cosmosmith/qa-report.mdor update task evidence. - Reopen tasks with clear reproduction steps when checks fail.
Evidence Rules
- Include command, result, environment, and observed behavior.
- Separate expected and actual behavior for bugs.
- Do not mark tasks done without evidence.
Completion
Stop when each reviewed task is accepted with evidence or reopened with a concrete bug report.
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.
- 5d ago First seen · 32 lines · 53 tokens per session scan A 56a1854c6b9e
cosmosmith-qa-verifier is a skill published in the GitHub repository devnomad-byte/cosmosmith (20 stars, last pushed 2mo ago), licensed MIT. It adds 53 tokens to every session and 245 once invoked, about $0.0003 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-30.
Other skills, from other repositories
screen-reader-testing
Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology support.
browser-testing-with-devtools
Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be…
designing-tests
Designs and implements testing strategies for any codebase. Use when adding tests, improving coverage, setting up testing infrastructure, debugging test failures, or when asked about unit tests, integration tests, or E2E testing.
qa/e2e-playwright
Playwright E2E 测试完整方法论，涵盖项目初始化、Page Object Model、认证复用、API Mock、视觉回归、多浏览器测试、CI 集成和调试技巧.
agent-browser
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
backend/testing-guide
后端测试编写指南，包括单元测试、集成测试和E2E测试的编写方法和最佳实践.