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/philchen00/verefiWrote 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/philchen00/verefi/verefi)<a href="https://agentmods.dev/plugins/philchen00/verefi/verefi"><img src="https://agentmods.dev/badge/plugins/philchen00/verefi/verefi/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/philchen00/verefi/verefi"><img src="https://agentmods.dev/badge/plugins/philchen00/verefi/verefi.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
verefi 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 1mo 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
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "verefi",
"displayName": "Verefi",
"version": "0.3.0",
"description": "AI-assisted pipeline that turns product specs into human-reviewed test plans and executable Playwright automation.",
"author": {
"name": "Phil Chen"
},
"homepage": "https://github.com/philchen00/verefi#readme",
"repository": "https://github.com/philchen00/verefi",
"license": "MIT",
"keywords": ["playwright", "testing", "test-generation", "quality-engineering"]
}
What it installs
The manifest is a name and a version. 5 skills travel with it, and installing the plugin installs all of them — 324 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 15 lines scan A 9b6b6dd14450
verefi is a plugin published in the GitHub repository philchen00/verefi (5 stars, last pushed 1mo 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-31.
Other plugins, from other repositories
paranoid-qa-ru
A Russian-language quality-assurance add-on for testing web applications with Playwright, a browser automation tool, and reviewing those tests.
paranoid-qa
Turn Claude Code into a meticulous QA engineer: every Pass/Fail verdict must cite an observed artifact. Testing framework with 1000 checks, Playwright test review, test-case generation, Jira bug reports.
quality-skills
Quality engineering skills for QA engineers, SDETs, and test automation leads — covering frontend (Selenium/Cypress/Playwright), API (Postman/REST Assured/Karate), performance (k6/JMeter/Gatling), mobile (Appium), BDD, accessibility, visual regression, security, chaos, contract testing, CI orchestration, and quality…
casely
Virtual QA lead: turns requirements into TestRail-ready test cases in one conversation, plus a runnable Postman collection when the spec describes an API.
testing
Testing toolkit: browser-based end-to-end verification with Playwright and a /write-tests command that generates a suite matching project conventions.
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.