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 figranium/figranium-mcp --skill figranium-browser-automationgit clone --depth 1 https://github.com/figranium/figranium-mcpWrote 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/figranium/figranium-mcp/figranium-browser-automation)<a href="https://agentmods.dev/skills/figranium/figranium-mcp/figranium-browser-automation"><img src="https://agentmods.dev/badge/skills/figranium/figranium-mcp/figranium-browser-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/figranium/figranium-mcp/figranium-browser-automation"><img src="https://agentmods.dev/badge/skills/figranium/figranium-mcp/figranium-browser-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.00047 | $0.00209 |
| Opus 5.5 | $0.00019 | $0.00084 |
| Sonnet 5 | $0.00009 | $0.00042 |
| Haiku 4.5 | $0.00005 | $0.00021 |
Grade A, and why
figranium-browser-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 14d 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.
What it actually says
Figranium browser automation
Use the Figranium MCP tools to turn browser work into reusable tasks.
Workflow
- Check whether an existing task already matches the user's goal.
- For repeatable work, create or update a task instead of relying on a one-off sequence.
- Use browser tools to inspect or interact with the target when needed.
- Execute the task and inspect the actual returned result to validate selectors, configuration, and extracted output.
- Correct and rerun when output is empty, malformed, duplicated, irrelevant, or unexpectedly null.
- Add a schedule only when recurring execution is requested.
- Use Cabinets when the workflow needs persistent downloaded/generated files.
Do not claim an automation works until a real execution result supports that conclusion.
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.
- 14d ago First seen · 21 lines · 47 tokens per session scan A 8eb41a734c4f
figranium-browser-automation is a skill published in the GitHub repository figranium/figranium-mcp (6 stars, last pushed 2d ago), licensed Apache-2.0. It adds 47 tokens to every session and 209 once invoked, about $0.0002 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-14.
Other skills, from other repositories
chrome-devtools-cli
Use this skill to write shell scripts or run shell commands to automate tasks in the browser or otherwise use Chrome DevTools via CLI.
a11y-debugging
Uses Chrome DevTools MCP for accessibility (a11y) debugging and auditing based on web.dev guidelines. Use when testing semantic HTML, ARIA labels, focus states, keyboard navigation, tap targets, and color contrast.
chrome-devtools
Uses Chrome DevTools via MCP for efficient debugging, troubleshooting and browser automation. Use when debugging web pages, automating browser interactions, analyzing performance, or inspecting network requests. This skill does not apply to --slim mode (MCP configuration).
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…
memory-leak-debugging
Diagnoses and resolves memory leaks in JavaScript/Node.js applications. Use when a user reports high memory usage, OOM errors, or wants to capture, compare, or inspect heap snapshots with Chrome DevTools MCP memory tools.
x-reader
Read source URLs from X/Twitter, articles, YouTube, Bilibili, podcasts, WeChat, Xiaohongshu, Telegram, RSS, and the open web. Use when the user provides a link and wants the original content, evidence, transcript, summary, or source-grounded analysis.