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 2389-research/review-squad --skill regularsgit clone --depth 1 https://github.com/2389-research/review-squadWrote 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/2389-research/review-squad/regulars)<a href="https://agentmods.dev/skills/2389-research/review-squad/regulars"><img src="https://agentmods.dev/badge/skills/2389-research/review-squad/regulars.svg" alt="Measured on agentmods" 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.00047 | $0.01969 |
| Opus 5 | $0.00023 | $0.00984 |
| Sonnet 5 | $0.00009 | $0.00394 |
| Haiku 4.5 | $0.00005 | $0.00197 |
Grade A, and why
regulars 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 7d 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Regulars
Overview
Dispatch a panel of subagents, each role-playing a real user with a specific task to complete on the site. They navigate using browser MCP tools, attempt to complete their goal, and report what broke, what was frustrating, and whether they succeeded. The organizing principle is task completion — can users do what they came to do?
This is NOT a QA test suite or expert audit. Regulars agents behave like real users — they don't inspect source code, they don't check every element, and they don't follow a test matrix. They try to accomplish a goal the way a real person would.
When to Use
- Before launch: "Does the site actually work end-to-end?"
- After deploy: "Did we break any user flows?"
- After refactor: "Can users still do the important things?"
- Periodic check: "Are the critical paths still working?"
Workflow
digraph regulars {
rankdir=TB;
"User requests smoke test" -> "Identify key user tasks for this site";
"Identify key user tasks for this site" -> "Present task panel with personas";
"Present task panel with personas" -> "Ask: add, remove, or adjust?";
"Ask: add, remove, or adjust?" -> "Finalize panel";
"Finalize panel" -> "Ensure dev server is running";
"Ensure dev server is running" -> "Dispatch agents sequentially";
"Dispatch agents sequentially" -> "After each: report pass/fail + key issue";
"After each: report pass/fail + key issue" -> "All done?";
"All done?" -> "After each: report pass/fail + key issue" [label="no"];
"All done?" -> "Compile results scorecard" [label="yes"];
}
Sequential dispatch required. Browser MCP tools share a single browser instance.
Designing the Task Panel
Unlike review-squad:experts (fixed default panel) or review-squad:normies (fixed sophistication spectrum), regulars tasks are site-specific. You must design them based on what the site does.
Step 1: Ask the user what the key user flows are, OR read the site's navigation/content to identify them.
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.
- 7d ago First seen · 189 lines · 47 tokens per session scan A 4f8a79eeb093
regulars is a skill published in the GitHub repository 2389-research/review-squad (12 stars, last pushed 2mo ago), licensed MIT. It adds 47 tokens to every session and 1,969 once invoked, about $0.0002 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-31.
Other skills, from other repositories
nobrainer-browser
Use when the owner says nb-browser or nobrainer-browser, asks to inspect or operate a rendered website, attach to an existing approved Chrome/Edge session, restart an approved non-default Chromium profile for loopback CDP, reproduce a browser flow, run Playwright tests, or record and analyze a Playwright trace. Prefer…
webapp-testing
Automated webapp testing with Playwright. Server management, UI testing, visual debugging, and reconnaissance-first approach.
test-web-ui
Automated web QA skill: analyzes a website or project, generates end-user use cases, derives a structured test plan, executes tests via Playwright browser automation, and produces a full HTML/Markdown QA report with screenshots and pass/fail results. TRIGGER this skill whenever the user asks to: test a website, run QA…
playwright-cli
Automate browser interactions, test web pages and work with Playwright tests.
playwright-tabbed-orchestration
Parent Agent uses playwright-tabbed to allocate browser tabs and partition tasks, then spawns child agents in parallel — each operating on its assigned tabid — for browser acceptance testing or automation, with a final aggregated summary. Suitable for multi-page validation, parallel module checks, and…
browse
Drive a real browser through Aside: open a page, read it, click through a flow, take screenshots, check console errors. (gstack).