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/RayFernando1337/rayfernando-skillsWrote 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/rayfernando1337/rayfernando-skills/running-bug-review-board)<a href="https://agentmods.dev/plugins/rayfernando1337/rayfernando-skills/running-bug-review-board"><img src="https://agentmods.dev/badge/plugins/rayfernando1337/rayfernando-skills/running-bug-review-board/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/rayfernando1337/rayfernando-skills/running-bug-review-board"><img src="https://agentmods.dev/badge/plugins/rayfernando1337/rayfernando-skills/running-bug-review-board.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
running-bug-review-board 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.
What it actually says
{"name":"running-bug-review-board","version":"0.5.0","description":"Real-user QA and Bug Review Board workflow. Runs manual app QA from a customer perspective, files P0/P1/P2 bug reports, produces YES/NO phase sign-off, generates an editorial HTML QA dashboard, syncs with confirmed issue trackers, and supports a separate Interactive BRB triage flow.","author":{"name":"Ray Fernando","url":"https://github.com/RayFernando1337"},"homepage":"https://github.com/RayFernando1337/rayfernando-skills","repository":"https://github.com/RayFernando1337/rayfernando-skills","license":"Apache-2.0","keywords":["qa","manual-testing","bug-review-board","browser-testing","real-user-testing","phase-qa","ux-bugs","pm-qa-engineer","html-report","magazine-design","dieter-rams","zite","editorial-typography","linear","github-issues","jira","notion","ios-simulator","ipados","axe","baguette","xcodebuildmcp","interactive-triage","bi-directional-sync","triage-heuristics","extensible","impact-field","risk-to-fix","chrome-devtools-mcp","computer-use","macos-app","waves","parallel-qa"]}What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 96 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.
- 9d ago First seen · 1 lines scan A 2f21aebc4ed8
running-bug-review-board is a plugin published in the GitHub repository RayFernando1337/rayfernando-skills (129 stars, last pushed 1mo ago), licensed Apache-2.0. 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
paranoid-qa-ru
A Russian-language quality-assurance add-on for testing web applications with Playwright, a browser automation tool, and reviewing those tests.
testing
Testing toolkit: browser-based end-to-end verification with Playwright and a /write-tests command that generates a suite matching project conventions.
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…
e2e-dashboard
Install a real-time Playwright E2E test dashboard (live SSE progress, 14 features) into any project.
mobile-app-testing
Test your web app on real iOS Simulator / Android emulator sessions via tapflow, alongside your existing Playwright suite.
quality-qa
Quality assurance: performance, Core Web Vitals, accessibility, web best practices, webapp testing and pre-launch checklists.