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 CodeInfinity1/Stram --skill web-form-automationgit clone --depth 1 https://github.com/CodeInfinity1/StramWrote 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/codeinfinity1/stram/web-form-automation)<a href="https://agentmods.dev/skills/codeinfinity1/stram/web-form-automation"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/web-form-automation/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/codeinfinity1/stram/web-form-automation"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/web-form-automation.svg" alt="Reviewed on agentmods" width="80" 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.00031 | $0.00507 |
| Opus 5.5 | $0.00012 | $0.00203 |
| Sonnet 5.5 | $0.00006 | $0.00101 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
web-form-automation 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Web Form Automation
Purpose
Help the assistant complete browser forms without guessing fields or submitting unintended data. This skill applies Actionbook-style form discipline through Stram's native browser tools.
When To Use
Use for account forms, contact forms, filters, search boxes, checkout-like forms, surveys, onboarding screens, and browser workflows with text fields, selects, or submit buttons.
Inputs And Evidence
- Target URL or existing browser session.
- Exact field values and any fields the user wants left blank.
- Observed form or element IDs.
- Confirmation/submit policy and final page state.
Tool Map
browser_openbrowser_observebrowser_typebrowser_fill_formbrowser_submit_formbrowser_live_observebrowser_live_typebrowser_live_fill_formbrowser_live_select_optionbrowser_live_press_keybrowser_live_click
Workflow
- Observe the form and identify fields from structured browser evidence.
- Map each user-provided value to a field; ask or stop when mapping is ambiguous.
- Fill fields through native browser tools.
- Re-observe and verify values before any submission.
- Submit only when the user explicitly asked and policy approval is satisfied.
- Verify the post-submit state or report the exact blocker.
Native Implementation Boundaries
- Use Stram browser tools and schemas.
- Do not import external reference Actionbook, browser-use, or upstream automation code.
- Do not use deterministic keyword matching to decide field semantics; use observed labels and model reasoning.
Safety And Approval
- Submitting forms, purchases, applications, messages, uploads, or account changes requires approval.
- Do not enter secrets, credentials, or payment details unless the user explicitly provides them for that session.
Verification
- Field values must be observed before submission.
- Submit result must be verified by page text, URL, status, or screenshot.
- If a captcha/login/payment appears, stop and report.
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 · 73 lines · 31 tokens per session scan A e64415ec5ea1
web-form-automation is a skill published in the GitHub repository CodeInfinity1/Stram (11 stars, last pushed 2mo ago), licensed MIT. It adds 31 tokens to every session and 507 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-08-31.
Other skills, from other repositories
browser-use
Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work. Also covers hosted cloud browsers for AI agents: the browser-use Python library (Browser(usecloud=True)), Playwright, Puppeteer or any CDP client.
x402
Set up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key. Two setups it works out up front — "just use it" (set up a wallet so you or Claude Code can run cloud browser tasks paid from the wallet — Claude writes and runs throwaway scripts, nothing…
opencli-autofix
Automatically fix broken OpenCLI adapters when commands fail. Load this skill when an opencli command fails — it guides you through collecting a trace artifact, patching the adapter, retrying, and filing an upstream GitHub issue after a verified fix. Works with any AI agent.
browser-qa-delivery
Validate a Design Studio HTML artifact in the sandbox browser, fix rendering and runtime defects, then deliver exactly the tested file.
playwright-pro
Production-grade Playwright testing skill for E2E suites, flaky test diagnosis, browser automation, migration from Cypress/Selenium, CI integration, visual checks, and regression validation.
cypress-ops
Cypress end-to-end and component testing operations - selector/retry-ability strategy, cy.intercept network stubbing, cy.session auth, component vs e2e, flake diagnosis, CI, Test Replay. Use for: cypress, e2e test, component test, cy.get, cy.intercept, cy.session, data-cy, data-test, retry-ability, flake, flaky test…