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.
npx skills add RayFernando1337/rayfernando-skills --skill running-bug-review-boardgit 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/skills/rayfernando1337/rayfernando-skills/running-bug-review-board)<a href="https://agentmods.dev/skills/rayfernando1337/rayfernando-skills/running-bug-review-board"><img src="https://agentmods.dev/badge/skills/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/skills/rayfernando1337/rayfernando-skills/running-bug-review-board"><img src="https://agentmods.dev/badge/skills/rayfernando1337/rayfernando-skills/running-bug-review-board.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 5 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Rogue Agent · line 269 Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
- medium Excessive Agency · line 340 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 344 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Rogue Agent · line 180 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 181 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00096 | $0.06959 |
| Opus 5 | $0.00048 | $0.03479 |
| Sonnet 5 | $0.00019 | $0.01392 |
| Haiku 4.5 | $0.00010 | $0.00696 |
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 12d 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 — 498 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Running the Bug Review Board (BRB) QA pass
This skill runs a real-user QA pass on an app and feeds the output into a Bug Review Board: a folder of structured bug reports, per-pass run reports, a self-contained HTML dashboard, and a final YES/NO sign-off the team can act on. Engineering's tracker (Linear / GitHub / Jira / Notion) syncs bi-directionally so QA and engineering stay in step.
It generalizes a battle-tested workflow that already shipped phase QA on Mokuhoe — the techniques are repo-agnostic.
Why this exists
Most engineers test their own code. They confirm what they wrote works. That misses the bugs real users hit first — stale state across flows, mobile overflow, copy that lies, paths that 404 mid-onboarding, race conditions between auth and routing.
This skill simulates a real user. The QA agent acts like a careful, mildly unforgiving customer who does not read the source code.
Two workflows — Auto QA and Interactive BRB
The skill splits the work into two distinct modes that share artifacts but run in separate sessions on purpose:
- Auto QA pass — the agent drives the app, runs scenarios, files bugs, generates the HTML report, writes a verdict. Optimized for thoroughness and speed.
- Interactive BRB — a different agent meets with the user to triage open / in-progress / fixed bugs. Runs the bi-directional pull first, applies pattern-based heuristics to surface duplicates and clusters, walks each bug, flips statuses, syncs to the tracker, regenerates HTML, writes minutes. Optimized for shared judgment.
Keep them separate. Running BRB inside an auto pass lets triage bias contaminate discovery and confuses attribution. See references/brb-interactive.md.
The trifecta — three hats, one pass
For every pass, wear all three hats:
- Product Manager. Confirm the build delivers the user-visible promise documented in the product spec or phase doc. If it does not, that is a product gap, not a bug — flag it in the run report.
- QA. Execute every scenario from a real user's perspective on the primary supported viewport(s). Capture evidence (snapshot, console, server data when relevant). Pass / Fail / Blocked.
- Engineer. Watch for invalidated assumptions: phase doc says "X uses function Y" but Y was renamed; new client orchestration appeared in a flow the docs say is server-driven; fields exist in UI that aren't in the spec. Finding gaps is the point — don't reverse- engineer the docs to match buggy behavior.
What ships with it
38 files beside SKILL.md 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.
- references/brb-interactive.md 7.9 KB
- references/browser-playbook.md 15 KB
- references/bug-filing.md 5.6 KB
- references/computer-use-playbook.md 8.3 KB
- references/discovering-the-app.md 8.3 KB
- references/extending-the-skill.md 12 KB
- references/gate-merge.md 5.0 KB
- references/html-report-style-guide.md 18 KB
- references/ios-simulator-playbook.md 15 KB
- references/issue-trackers.md 16 KB
- references/parallel-coordinator.md 9.9 KB
- references/sequential-wrapup.md 5.1 KB
- references/session-hygiene.md 6.9 KB
- references/templates/brb-interactive-prompt.md 4.0 KB
- references/templates/brb-minutes.md 3.1 KB
- references/templates/bug-report.md 3.3 KB
- references/templates/coordinator-merge.md 3.5 KB
- references/templates/html-report/assets.css 20 KB
- references/templates/html-report/bug.html 9.0 KB
- references/templates/html-report/index.html 6.9 KB
- references/templates/html-report/README.md 2.4 KB
- references/templates/html-report/run.html 3.6 KB
- references/templates/html-report/samples/bug-detail-desktop.png 242 KB
- references/templates/html-report/samples/dashboard-desktop.png 177 KB
- references/templates/html-report/samples/dashboard-mobile.png 140 KB
- references/templates/html-report/samples/README.md 1.1 KB
- references/templates/qa-config.example.json 4.3 KB
- references/templates/run-report.md 1.6 KB
- references/templates/sequential-prompt.md 2.7 KB
- references/templates/shard-prompt.md 3.1 KB
- references/templates/test-plan.md 2.5 KB
- references/test-accounts.md 6.1 KB
- references/test-plan.md 6.6 KB
- references/triage-heuristics.md 8.4 KB
- references/workflow.md 8.2 KB
- scripts/bugs-needing-pull.sh 4.0 KB runs code
- scripts/bugs-needing-sync.sh 3.6 KB runs code
- scripts/scaffold-qa.sh 13 KB runs code
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.
- 12d ago First seen · 498 lines · 96 tokens per session scan A 618d63443128
running-bug-review-board is a skill published in the GitHub repository RayFernando1337/rayfernando-skills (129 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 96 tokens to every session and 6,959 once invoked, about $0.0005 per session on Opus 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-08-30.
Other skills, from other repositories
agent-browser
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
flutter-skill
Automate and test Flutter applications — launch apps, inspect widgets, tap elements, enter text, scroll, swipe, take screenshots, validate state, and debug via Dart VM Service Protocol. Use when the user wants to run Flutter app tests, automate Flutter UI interactions, inspect widget trees, debug a running Flutter…
debugging
Playwright test debugging conventions for the scaffold — reading failure messages, classifying failure modes (TimeoutError, ZodError, strict-mode violation, locator not found, network errors, schema drift), the playwright.config.ts capture defaults (trace on-first-retry, screenshot only-on-failure, video…
Flaky Test Doctor
Diagnose flaky test failures from Playwright reports, traces, and rerun history. Classify each failure as product, test, environment, data, or unknown with cited evidence and a proposed fix. Never auto-modifies code without opt-in.
flake-triage
Decide whether a preview the visual-diff bot flagged actually regressed or is simply nondeterministic, using a repeat-render oracle at a single commit. Use when a PR's preview diff reports a changed preview whose source the PR does not touch, or when a render, GIF or filmstrip is suspected of being unstable.
qa-knowledge
To run QA engineering — requirements/gap analysis, scenario & spec design, test implementation, failure triage — over the QA knowledge base.