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/akovalion/paranoid-qaWrote 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/plugins/akovalion/paranoid-qa/ru)<a href="https://agentmods.dev/plugins/akovalion/paranoid-qa/ru"><img src="https://agentmods.dev/badge/plugins/akovalion/paranoid-qa/ru/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/plugins/akovalion/paranoid-qa/ru"><img src="https://agentmods.dev/badge/plugins/akovalion/paranoid-qa/ru.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
paranoid-qa-ru 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 6d 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
{
"name": "paranoid-qa-ru",
"description": "Русская версия paranoid-qa: дотошный QA-агент с доказательной дисциплиной - каждый вердикт только по наблюдённому артефакту. Фреймворк тестирования, ревью Playwright-тестов, тест-кейсы, баг-репорты в Jira.",
"author": {
"name": "Aleksei Kovalev"
},
"homepage": "https://github.com/akovalion/paranoid-qa",
"license": "MIT",
"keywords": ["qa", "testing", "playwright", "test-review", "evidence"]
}
What it installs
The manifest is a name and a version. 5 skills travel with it, and installing the plugin installs all of them — 391 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 6d ago Changed · -1 lines e5c3a5f44cf9
- 1mo ago First seen · 12 lines scan A c2a2b4ec07d5
paranoid-qa-ru is a plugin published in the GitHub repository akovalion/paranoid-qa (13 stars, last pushed 6d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
sniff
Autonomous QA scanner via sniff-qa: walks your running app in a real browser and reports real bugs (broken pages/links, console/network errors, broken forms, state-loss, empty/placeholder data, bad loading/error states, responsive + a11y) with reproduction proof, severity, confidence, and a fix. No API key.
verefi
AI-assisted pipeline that turns product specs into human-reviewed test plans and executable Playwright automation.
browser-test
E2E browser test pipeline for Claude Code: author, refine, compile, and run Playwright tests using browser automation.
naive-user
Drive a live web app as a source-blind, naive first-time user and report UX/behavior gaps (bugs, broken expectations, UX surprises, a11y) before deploy. Config-driven, Playwright-MCP powered.
DAA-Master
Declarative Action Architecture (DAA) — a strict three-layer separation pattern for E2E automation testing. Provides skills for generating, reviewing, and architecting DAA-compliant test code.
playwright-autopilot
Playwright E2E test debugging and interactive browser exploration. Runs tests with action capture (DOM snapshots, network, console, screenshots), diagnoses failures, and provides browser tools for navigating, clicking, and inspecting pages through ARIA snapshots.