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 Justinmendezai/The-Adam-Repo --skill review-runtimegit clone --depth 1 https://github.com/Justinmendezai/The-Adam-RepoWrote 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/justinmendezai/the-adam-repo/review-runtime)<a href="https://agentmods.dev/skills/justinmendezai/the-adam-repo/review-runtime"><img src="https://agentmods.dev/badge/skills/justinmendezai/the-adam-repo/review-runtime/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/justinmendezai/the-adam-repo/review-runtime"><img src="https://agentmods.dev/badge/skills/justinmendezai/the-adam-repo/review-runtime.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00080 | $0.01370 |
| Opus 5 | $0.00040 | $0.00685 |
| Sonnet 5 | $0.00016 | $0.00274 |
| Haiku 4.5 | $0.00008 | $0.00137 |
Grade A, and why
review-runtime 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
review-runtime
Tests prove the contract. Runtime review proves the experience. The orchestrator drives the app via the browser MCP configured for the project (see Browser MCP below) and inspects logs via the logger MCPs, checking that the slice's user-visible ACs hold against the real running thing.
When to use
- After
review-via-graphpasses. - For any slice with a user-facing behavior in its ACs.
- Skip for purely internal slices (lib refactor, infra) —
review-via-graphis enough there.
Inputs
- A slice on its branch (
adam/<slice-id>). - The project's dev server start command (in
plan/CONTEXT.md, orpacket/PACKET.mde2e.commands.devwhen present). - A list of user-visible ACs from
slices/<id>/SPEC.md.
Browser MCP
Read adam.json in the project repo.
- If
browser_mcpis set (for example"playwright"or"cursor-ide-browser"), use that server's tools forbrowser_navigate,browser_snapshot,browser_click, etc. - Otherwise, pick the first entry in
review_mcpsthat names a browser driver: preferplaywrightor any id containingplaywright(some workspaces useuser-playwright), elsecursor-ide-browser.
Use the same server for the whole review. Log which server key was used in review_findings / notes with source set to playwright or cursor-ide-browser as appropriate.
Workflow
1. Bring up the app on the slice's branch
Either:
- Switch to the branch in the main worktree (only if the orchestrator's own work is committed), OR
- Use the slice's
best-of-n-runnerworktree directly (preferred — it's already there).
Start the dev server in a background shell, then Await a ready line before driving the UI:
Shell(command="<dev command>", block_until_ms=0, description="Start dev server for review")
Await(task_id=<id>, pattern="Local:|listening|Ready in", block_until_ms=120000)
Capture the URL from the ready line. If Await times out, read terminal output, fix, retry — do not ask the operator to start the server.
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 · 95 lines · 80 tokens per session scan A 456013a474a2
review-runtime is a skill published in the GitHub repository Justinmendezai/The-Adam-Repo (12 stars, last pushed 18d ago), licensed Apache-2.0. It adds 80 tokens to every session and 1,370 once invoked, about $0.0004 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
browse
Drive a real browser through Aside: open a page, read it, click through a flow, take screenshots, check console errors. (gstack).
playwright-cli
A command-line tool for controlling Chromium, Firefox, and WebKit browsers, including navigation, page interaction, screenshots, PDFs, and recorded actions.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
create-verification-skill
Create a repo-local verification skill and exhaustive feature map for driving a real app through its UI, CLI, or API. Use for "create a verification skill", "make a verify skill for this repo", or "document how agents can verify this app".
browser-qa
A browser-based quality check for deployed web pages and user flows. It uses browser automation to test rendering, navigation, forms, interactions, responsive behaviour, and accessibility-related issues.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…