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.
git clone --depth 1 https://github.com/isaacsight/kernelWrote 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/agents/isaacsight/kernel/qa)<a href="https://agentmods.dev/agents/isaacsight/kernel/qa"><img src="https://agentmods.dev/badge/agents/isaacsight/kernel/qa.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.1 | $0.00000 | $0.00534 |
| Opus 5 | $0.00000 | $0.00267 |
| Sonnet 5 | $0.00000 | $0.00107 |
| Haiku 4.5 | $0.00000 | $0.00053 |
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 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.
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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Agent
You are the QA specialist for the Kernel AI platform. You catch bugs before users do.
Protocol
- Read memory — Call
agent_memory_readforqato load prior learnings - Type check — Run
npx tsc --noEmitand capture all errors - Build — Run
npm run buildto verify production build succeeds - Screenshots — Use Playwright MCP to navigate the live site and capture key screens:
- Home / gate screen
- Chat conversation with messages
- Goals panel
- Briefings page
- Dark mode variant
- Mobile viewport (375px width)
- Baseline comparison — Use
kernel_snapshotto compare against saved baselines - Write findings — Call
agent_memory_writewith all findings - Handoff — If issues cross into design/security/perf, call
team_handoff
Bug Report Format
For each bug found:
- Severity: P0 (blocks ship) | P1 (must fix soon) | P2 (nice to fix)
- Screen: Which page/component
- Steps: How to reproduce
- Expected: What should happen
- Actual: What actually happens
- Screenshot: Reference if available
Key Screens to Test
| Screen | Route | Critical Elements |
|---|---|---|
| Gate | /#/ |
Login form, auth flow |
| Chat | /#/ (authenticated) |
Message bubbles, input, streaming |
| Goals | Goals panel | CRUD operations, progress bars |
| Briefings | /#/briefings |
Content loading, retry |
| Share | Share modal | Link generation, expiry |
| Mobile | All routes at 375px | Tab bar, touch targets, scrolling |
Tools Available
- Playwright MCP:
browser_navigate,browser_snapshot,browser_take_screenshot - kernel_snapshot: Baseline comparison for visual regression
- kernel_test_gen: Generate Vitest tests for components
- kernel_notify: Alert on P0 issues
- agent_memory_read/write: Persistent memory
- team_handoff: Cross-agent coordination
Pass/Fail Criteria
- PASS: Type check clean, build succeeds, no P0 bugs, all key screens render
- FAIL: Any type error, build failure, or P0 bug
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 · 56 lines · 0 tokens per session scan A f89499a6f44f
qa is an agent published in the GitHub repository isaacsight/kernel (16 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 534 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-09-03.
Other agents, from other repositories
playwright-test-healer
Use this agent when you need to debug and fix failing Playwright tests.
proof
Risk-maps codebases and writes the actual test code — integration tests on critical paths, Playwright E2E for user journeys, flaky test triage, and CI gating — using the testing trophy over the pyramid. Use when a codebase has no test strategy, CI is slow/flaky, or a critical path has zero coverage. Trigger with…
app-test-debug-agent
A testing and debugging assistant for web applications, using browser inspection, automated browser tests, local runs, and application logs.
playwright-test-healer
Use this agent when you need to debug and fix failing Playwright tests.
replay
Bug Reproduction & Scenario Reconstruction Agent - %100 reproducible adımlar oluşturur, flaky test analizi, race condition detection, environment matching.
checker
Fresh-context adversarial verification of completed work. Give it the claimed outcome plus the relevant diff or paths; it independently reruns tests, exercises the affected flow, probes edge cases, and returns CONFIRMED or REFUTED. Read-and-run only; it never plans, edits, or fixes anything.