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 qagit 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)<a href="https://agentmods.dev/skills/rijuvashisht/magneto/qa"><img src="https://agentmods.dev/badge/skills/rijuvashisht/magneto/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/rijuvashisht/magneto/qa"><img src="https://agentmods.dev/badge/skills/rijuvashisht/magneto/qa.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.00760 |
| Opus 5 | $0.00000 | $0.00380 |
| Sonnet 5 | $0.00000 | $0.00152 |
| Haiku 4.5 | $0.00000 | $0.00076 |
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 9d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/qa — Real Browser Automation: Walk, Find Bugs, Fix, Regression-Test
Role: QA Lead
Inputs: test-plan.md (from /plan-eng-review) + target URL
Outputs: qa-report.md, regression tests in tests/
Audit actions: qa.started, qa.bug_found, qa.bug_fixed, qa.tests_generated
What This Skill Does
Runs a real Chromium browser via Playwright. Walks through the test plan. Finds bugs, fixes them with atomic commits, generates regression tests.
Prerequisites
npx playwright install chromium
Magneto exposes browser control via magneto browse <command>:
magneto browse navigate <url>magneto browse click <selector>magneto browse fill <selector> <value>magneto browse screenshot <path>magneto browse eval <js>
The Protocol
Step 1: Load test-plan.md (or default flows)
Extract the test matrix. If no test-plan exists, default to:
- Landing → signup → confirm email
- Login → primary feature → logout
- Error path (invalid input, 5xx upstream)
Step 2: For each scenario
magneto browse navigate <url>
magneto browse screenshot qa-baseline.png
# walk the flow via click/fill/eval
# capture assertions: title, URL, visible text, network status
When an assertion fails:
- Screenshot the failure state
- Emit audit:
magneto audit add qa.bug_found --payload '{"scenario":"...","error":"..."}' - Classify: [CLIENT] bug, [SERVER] bug, or [FLAKY]
- If [CLIENT]: investigate via /investigate methodology, propose fix
- If [FLAKY]: retry 2x before calling it a bug
Step 3: Fix with atomic commits
Each bug fix is one commit: fix + regression test + "I SEE THE ISSUE" explanation.
Step 4: Regenerate regression tests
Convert each walked scenario into a Playwright test file:
// tests/qa/auth-flow.spec.ts (auto-generated)
import { test, expect } from '@playwright/test';
test('login flow — happy path', async ({ page }) => {
await page.goto(process.env.BASE_URL!);
await page.click('[data-testid="login"]');
await page.fill('[name="email"]', '[email protected]');
// ...
});
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.
- 9d ago First seen · 97 lines · 0 tokens per session scan A 3bb9c8047dfb
qa 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 760 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.
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.
browse
Drive a real browser through Aside: open a page, read it, click through a flow, take screenshots, check console errors. (gstack).
playwright-cli
A command-line tool for controlling Chromium, Firefox, and WebKit browsers, including navigation, page interaction, screenshots, PDFs, and recorded actions.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
create-verification-skill
Create a repo-local verification skill and exhaustive feature map for driving a real app through its UI, CLI, or API. Use for "create a verification skill", "make a verify skill for this repo", or "document how agents can verify this app".