Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/bdfinst/agentic-dev-teamnpx agentmods add skills/bdfinst/agentic-dev-team/browseWrote 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/bdfinst/agentic-dev-team/browse)<a href="https://agentmods.dev/skills/bdfinst/agentic-dev-team/browse"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/browse/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/bdfinst/agentic-dev-team/browse"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/browse.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 Tool Misuse · line 109 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- medium MCP Rug Pull · line 8 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 41 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 50 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 144 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00033 | $0.01486 |
| Opus 5.5 | $0.00013 | $0.00594 |
| Sonnet 5.5 | $0.00007 | $0.00297 |
| Haiku 4.5 | $0.00003 | $0.00149 |
Grade A, and why
browse 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 1mo 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Browse
Role: worker. This command provides browser-based interaction for visual verification and e2e testing.
You have been invoked with the /browse command.
Worker constraints
- Drive the browser only; do not edit source.
- Capture evidence (screenshots/logs); do not assert pass/fail beyond what was observed.
- Be concise. Report observations and artifacts, no preamble.
Parse Arguments
Arguments: $ARGUMENTS
- Positional:
<url>(required) — the URL to navigate to --screenshot <path>: Save screenshot to this path (default:tmp/screenshots/<timestamp>.png)--click <selector>: CSS selector to click after page load--fill <selector> <value>: CSS selector and value for form input (can be repeated)--wait <ms>: Wait this many milliseconds after page load (default: 1000)--viewport <WxH>: Viewport dimensions (default:1280x720)
Steps
1. Check Playwright availability
Run:
npx playwright --version 2>/dev/null
If Playwright is not available, ask the user:
Playwright is required for browser interaction. Run
/project-initto set up this repo's tooling (installs Playwright + Chromium for frontend projects), or install it directly now:npx playwright install chromium
Do not proceed until Playwright is confirmed available.
2. Ensure screenshot directory exists
mkdir -p tmp/screenshots
3. Execute browser action
Write a temporary Node.js script and execute it with node. Use Playwright's API directly for reliable, scriptable interaction.
Template (adapt based on parsed arguments):
const { chromium } = require('playwright');
(async () => {
const browser = await chromium.launch({ headless: true });
const context = await browser.newContext({
viewport: { width: VIEWPORT_WIDTH, height: VIEWPORT_HEIGHT }
});
const page = await context.newPage();
try {
await page.goto('URL', { waitUntil: 'networkidle', timeout: 30000 });
await page.waitForTimeout(WAIT_MS);
// -- Click actions (if --click provided) --
// await page.click('SELECTOR');
// -- Fill actions (if --fill provided) --
// await page.fill('SELECTOR', 'VALUE');
// -- Screenshot --
await page.screenshot({ path: 'SCREENSHOT_PATH', fullPage: true });
console.log('Screenshot saved to: SCREENSHOT_PATH');
console.log('Page title:', await page.title());
console.log('Page URL:', page.url());
} catch (err) {
console.error('Browser error:', err.message);
// Take a screenshot of the error state if possible
try {
await page.screenshot({ path: 'SCREENSHOT_PATH', fullPage: true });
console.log('Error-state screenshot saved to: SCREENSHOT_PATH');
} catch {}
} finally {
await browser.close();
}
})();
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.
- 1mo ago First seen · 185 lines · 33 tokens per session scan A 049b542bd1b5
browse is a skill published in the GitHub repository bdfinst/agentic-dev-team (295 stars, last pushed 4d ago), licensed MIT. It adds 33 tokens to every session and 1,486 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
interactive-login
Log a CLI in with a browser/device-code flow (aws sso, gh, glab, gcloud, …) and save the result to the keychain so later commands can request it through execute.credentials.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
azure-messaging-webpubsub-java
Build real-time web applications with Azure Web PubSub SDK for Java. Use when implementing WebSocket-based messaging, live updates, chat applications, or server-to-client push notifications.
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
open-design-browser
Inspect and exercise local HTML design artifacts with the existing agent-browser CLI, including screenshots and keyboard or interaction checks. Use when rendered evidence helps author or review a design; excludes browser installation, remote services, and unrelated browser automation.