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 rijuvashisht/Magneto --skill qa-onlygit clone --depth 1 https://github.com/rijuvashisht/MagnetoWrote 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/rijuvashisht/magneto/qa-only)<a href="https://agentmods.dev/skills/rijuvashisht/magneto/qa-only"><img src="https://agentmods.dev/badge/skills/rijuvashisht/magneto/qa-only/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/rijuvashisht/magneto/qa-only"><img src="https://agentmods.dev/badge/skills/rijuvashisht/magneto/qa-only.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.00000 | $0.00340 |
| Opus 5 | $0.00000 | $0.00170 |
| Sonnet 5 | $0.00000 | $0.00068 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
qa-only 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 10d 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
/qa-only — QA Methodology, Report Only (No Fixes)
Role: QA Reporter
Inputs: test-plan.md + target URL
Outputs: qa-report.md only — no code changes
Audit actions: qa-only.started, qa-only.bug_found
What This Skill Does
Same walking methodology as /qa, but STRICTLY read-only. No fixes. No commits. Pure bug report.
Use this when:
- Reviewing someone else's deploy
- Running pre-release QA on staging
- You want a bug report without AI auto-fixing
The Protocol
Same as /qa Steps 1–2, then:
Step 3: Write qa-report.md
# QA Report (read-only) — <url>
## Scenarios Walked
[same format as /qa]
## Bugs Found
### Bug 1: <title>
- **Where:** <page / selector>
- **Expected:** <behavior>
- **Actual:** <behavior>
- **Severity:** blocker | major | minor | polish
- **Repro:** <click/type steps>
- **Screenshot:** ./qa-bug-1.png
- **Audit event:** qa-only.bug_found seq=<N>
## Environment
- URL: <base-url>
- Browser: Chromium <version>
- Date: <ISO timestamp>
Trigger Phrases
- "qa only"
- "bug report"
- "test without fixing"
Contract Reminder
- NEVER modify code during /qa-only
- NEVER commit during /qa-only
- Only write qa-report.md and take screenshots
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.
- 10d ago First seen · 58 lines · 0 tokens per session scan A 671e8521faf2
qa-only is a skill published in the GitHub repository rijuvashisht/Magneto (6 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 340 tokens. 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
langbot-testing
Test LangBot WebUI and core product flows with an automated browser and backend logs. Use when validating the configured LangBot frontend, pipeline Debug Chat, model provider setup and test buttons, bot and knowledge-base UI flows, or troubleshooting failed LangBot end-to-end tests.
mailagent
Temporary inboxes for agent signup QA — create disposable addresses, wait for verification email, extract OTP or magic links. Use when automating signup, login, or email verification without parsing HTML manually.
browser-qa
A browser-based quality check for deployed web pages and user flows. It uses browser automation to test rendering, navigation, forms, interactions, responsive behaviour, and accessibility-related issues.
acceptance
End-to-end verification and self-evidence for a delivery in any repository, with or without a preconfigured verify plan. Discover an existing plan when one was handed to this run; otherwise author checks and publish a standalone acceptance. Pick the proving surface (CLI / web / desktop / iOS Simulator), drive the real…
recipe-add-integration-tests
Add integration/E2E tests to existing codebase using Design Docs.
integration-e2e-testing
Selects and specifies only integration/E2E tests whose observable boundary cannot be proven more cheaply.