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 BlackBeltTechnology/pi-agent-dashboard --skill browsergit clone --depth 1 https://github.com/BlackBeltTechnology/pi-agent-dashboardWrote 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/blackbelttechnology/pi-agent-dashboard/browser)<a href="https://agentmods.dev/skills/blackbelttechnology/pi-agent-dashboard/browser"><img src="https://agentmods.dev/badge/skills/blackbelttechnology/pi-agent-dashboard/browser.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.00092 | $0.01614 |
| Opus 5 | $0.00046 | $0.00807 |
| Sonnet 5 | $0.00018 | $0.00323 |
| Haiku 4.5 | $0.00009 | $0.00161 |
Grade A, and why
browser 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 3d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
browser
Composite skill that gives the agent eyes and hands for any browser-driven
task — web pages or Electron desktop apps — via the agent-browser CLI.
Three recipes:
- Web automation — generic web pages plus Pi Dashboard-specific helpers
(dashboard URL detection, responsive testing, console-error hunting).
Reference:
references/web.md. - Electron automation — drive any Chromium-based Electron app, including
a worked example for the Pi Dashboard's own shell via
--debug-cdp. Reference:references/electron.md. - The user's own logged-in browser — reach SSO/2FA-gated sites using the
user's real cookies via an extension bridge (Panerelay), plus how to list
and select Chrome profiles.
Reference:
references/own-browser.md.
Step 0a — Preflight: agent-browser CLI must be installed
The skill does not bundle the CLI. Verify it through the dashboard tool
registry — recommend-only, nothing installs without an explicit --install:
pi-dashboard-ensure <extension-package-root>/package.json
<extension-package-root> is the package that ships this skill — three levels
above this SKILL.md's .pi/skills/browser/ directory (in a global install:
$(npm root -g)/@blackbelt-technology/pi-dashboard/node_modules/@blackbelt-technology/pi-dashboard-extension).
The manifest (pi.tools) declares agent-browser (resolve) and chromium
(pw-browser); the registry answers present / recommended / blocked per
tool.
-
agent-browser: present→ continue to Step 0b. -
agent-browser: recommendedorblocked→ halt and tell the user:The
agent-browserCLI is not installed. Install it as a pi extension so thebrowsertool is registered in your pi session too:pi install npm:pi-agent-browserThen re-invoke the skill.
-
chromiummissing → mention the registry's Install hint (npx [email protected] install chromium) only when the chosen recipe needs a CDP browser; the dropdown on the Settings → Tools row carries it.
What ships with it
14 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.
- LICENSE 11 KB
- references/electron.agent.md 4.3 KB
- references/electron.md 9.0 KB
- references/electron.md.AGENTS.md 316 B
- references/own-browser.md 12 KB
- references/own-browser.md.AGENTS.md 1.0 KB
- references/web.agent.md 24 KB
- references/web.md 81 KB
- references/web.md.AGENTS.md 294 B
- scripts/check-panerelay.sh 6.4 KB runs code
- scripts/check-panerelay.sh.AGENTS.md 928 B
- scripts/detect-dashboard.sh 1.7 KB runs code
- SKILL.md.AGENTS.md 428 B
- UPSTREAM.md 2.8 KB
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.
- 3d ago Changed · +13 lines 90dd7f82cc93
- 7d ago First seen · 120 lines · 92 tokens per session scan A 433dc38a9bec
browser is a skill published in the GitHub repository BlackBeltTechnology/pi-agent-dashboard (274 stars, last pushed yesterday), licensed MIT. It adds 92 tokens to every session and 1,614 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
hep-browser
Use the Agentlas browser hardpoint for browser-required work.
agentlas-browser
Use when the user types /agentlas-browser , /agentlas browser, or /hep-browser for browser-required tasks, rendering pages, form flows, or visual evidence.
goga-cookbook
Principles for applying DSL specification in cell and CODEMANIFEST design.
rn-feature-development
This skill should be used when building any new feature in a React Native or Expo app, or when the /rn-dev-agent:rn-feature-dev command runs. Triggers on "build a feature", "add X to the app", "implement Y", "create a new screen", "rn-feature-dev", "feature development", "build me X", "add a screen", "wire up this…
goga-plan-by-design
Compile a design document into a ralphex execution plan.
rn-testing
This skill should be used when the user asks to "write a Maestro test", "create E2E flows", "add testIDs", "run UI tests", "run E2E tests", "verify a feature works", "test my screen", "set up maestro-runner", "mock network requests", "inspect store state", "write test assertions", or needs guidance on test timing…