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 supatest-ai/alan-skills --skill alan-test-featuregit clone --depth 1 https://github.com/supatest-ai/alan-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/supatest-ai/alan-skills/alan-test-feature)<a href="https://agentmods.dev/skills/supatest-ai/alan-skills/alan-test-feature"><img src="https://agentmods.dev/badge/skills/supatest-ai/alan-skills/alan-test-feature/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/supatest-ai/alan-skills/alan-test-feature"><img src="https://agentmods.dev/badge/skills/supatest-ai/alan-skills/alan-test-feature.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
- Snyk fail
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.00041 | $0.04458 |
| Opus 5 | $0.00020 | $0.02229 |
| Sonnet 5 | $0.00008 | $0.00892 |
| Haiku 4.5 | $0.00004 | $0.00446 |
Grade A, and why
alan-test-feature scanned grade A with 1 finding 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 10d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sf http://localhost:PORT >/dev/null 2>&1 && break How it starts
The opening of the file, as written. The whole thing — 440 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task: Test Feature & Generate Demo Report
Analyze the current branch's changes, scope the coverage level with the user, build an explicit testing strategy, start the app's dev server, test the feature in a real browser using agent-browser, capture screenshots and video (always — no exceptions), upload everything to S3, and generate a structured test report (always — never skip).
Phase 0: Environment Setup
1. Get artifact context IDs
Use the active task context when it is present in the prompt. Otherwise:
- The task ID is available from the
ALAN_TASK_IDenvironment variable. - The conversation ID is available from the
ALAN_SESSION_IDenvironment variable. - Resolve
teamIdwith Alan MCP context/tools before creating the report.
When calling create_test_report, always pass taskId, conversationId, and teamId explicitly. Do not substitute one ID for another.
2. Verify agent-browser is available
agent-browser is a CLI tool by Vercel Labs (npm: agent-browser) — it is NOT a skill or MCP tool. It provides headless browser automation via bash commands (open, click, fill, screenshot, record). In sandboxes it is pre-installed by runtime-bootstrap.ts.
command -v agent-browser >/dev/null 2>&1 && echo "agent-browser: OK" || echo "agent-browser: MISSING"
If missing, install it:
npm install -g agent-browser && agent-browser install
If installation fails (e.g. no network, no npm), STOP and tell the user:
"agent-browser is not available and could not be installed. Install it manually:
npm install -g agent-browser && agent-browser install"
Do NOT proceed to Phase 2 without a working agent-browser — all browser testing depends on it.
3. Create workspace
All captures (screenshots, videos) MUST be written to /tmp/alan-captures/.
mkdir -p /tmp/alan-captures
CRITICAL — file path rules:
- ONLY write capture files to
/tmp/alan-captures/. Never anywhere else.- NEVER write to
.claude/, project directories,reports/, or any path inside the repo..claude/is a sensitive system directory — writing to it will be blocked and will abort the test run.- If you are tempted to create a
reports/orscreenshots/folder anywhere other than/tmp/, stop and use/tmp/alan-captures/instead.
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.
- 10d ago First seen · 440 lines · 41 tokens per session scan A a8ce601a33ab
alan-test-feature is a skill published in the GitHub repository supatest-ai/alan-skills (0 stars, last pushed 21d ago), licensed Apache-2.0. It adds 41 tokens to every session and 4,458 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.
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…