Borrowing it
Nothing to install: this file belongs to talayash/agentrium. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/talayash/agentrium/master/.claude/skills/local-qa/SKILL.mdgit clone --depth 1 https://github.com/talayash/agentriumWrote 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/talayash/agentrium/local-qa)<a href="https://agentmods.dev/skills/talayash/agentrium/local-qa"><img src="https://agentmods.dev/badge/skills/talayash/agentrium/local-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/talayash/agentrium/local-qa"><img src="https://agentmods.dev/badge/skills/talayash/agentrium/local-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.00059 | $0.01838 |
| Opus 5.5 | $0.00024 | $0.00735 |
| Sonnet 5.5 | $0.00012 | $0.00368 |
| Haiku 4.5 | $0.00006 | $0.00184 |
Grade A, and why
local-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 24d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Running Agentrium locally for QA
The hard rule (never violate)
The user runs their real Agentrium client on this machine, all day, with live Claude Code sessions in it. It is production. It is their actual work.
NEVER, under any circumstances, for any reason:
- Kill, stop, close,
Stop-Process,CloseMainWindow,taskkill, or otherwise terminate a runningclaude-terminal.exe/Agentriumprocess. - Take, free, or kill whatever is holding port 5173. That is the production client's dev port.
- Ask the user to close their client so your build can launch.
- Run bare
npm run tauri devornpm run devin this repo. Both default to 5173 and to the production app identifier, which collides.
There is no exception. Not "just this once", not "it's only a dev build", not "the app restores sessions anyway", not if a launch fails and killing it would be the quick fix. If QA seems to require stopping their client, you are using the wrong recipe - use the one below instead.
If something still will not run after following this file, report that and stop. Do not escalate to touching their process.
Why a plain tauri dev cannot work here
Three separate collisions, all of which must be solved at once:
| Collision | Cause | Fix |
|---|---|---|
| App never launches, exits code 0 | tauri-plugin-single-instance (src-tauri/src/main.rs) keys on the app identifier; a second launch just focuses the first and quits |
override identifier |
| Port in use / hijacks their dev server | vite.config.ts pins port: 5173, strictPort: true |
override port AND build.devUrl |
| Shares the production SQLite DB and keychain sign-in | data dir and keychain service default to the prod names | set AGENTRIUM_INSTANCE_ID=.qa |
Fixing only one of the first two is what causes the damage. Fix both.
Isolating the database (know this before you QA)
Always export AGENTRIUM_INSTANCE_ID=.qa before launching. Rust reads it
through crate::instance_suffix() (src-tauri/src/main.rs) and appends it to:
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.
- 24d ago Changed · +14 lines e998407cd274
- 1mo ago First seen · 146 lines · 59 tokens per session scan A 595330d39b45
local-qa is a skill published in the GitHub repository talayash/agentrium (46 stars, last pushed 2d ago), licensed MIT. It adds 59 tokens to every session and 1,838 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-09-22.
Other skills, from other repositories
moai-ref-testing-pyramid
Test pyramid strategy, coverage targets, test patterns, and quality metrics reference. Agent-extending skill that amplifies manager-develop test-creation and quality-validation work with production-grade testing patterns. NOT for: production code implementation, architecture design, DevOps, security audits.
cherry-regression-test
Run Cherry Studio critical-path system regression tasks through the repository-owned Playwright E2E workflow. Use for full regression, release acceptance, development-branch system validation, or a named cherry-regression-test task on GitHub-hosted macOS and Windows runners.
integration-e2e-testing
Defines integration/E2E skeleton annotations, lane and file contracts, and route-parity review criteria. Use when generating or consuming test skeletons or reviewing shared mutation routes.
vibe-verify
Exercise a running product against acceptance criteria and report evidence. Build success alone does not verify behavior.
memstack-development-test-writer
Use this skill when the user says 'write tests', 'add tests', 'test coverage', 'unit tests', 'integration tests', 'component tests', 'mocking', 'edge cases', or needs to generate tests with proper mocking and edge case coverage. Do NOT use for refactoring plans or database migrations.
memstack-development-webapp-testing
Use when the user says 'write browser tests', 'test this page', 'playwright test', 'e2e test', 'end to end test', 'browser test', 'test the UI', or needs Playwright-based browser testing for a web application. Do NOT use for unit tests, API tests, or non-browser testing.