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 agentmods add skills/modiqo/skillspec/prose_onlynpx skills add modiqo/skillspec --skill prose_onlygit clone --depth 1 https://github.com/modiqo/skillspecWrote 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/modiqo/skillspec/prose_only)<a href="https://agentmods.dev/skills/modiqo/skillspec/prose_only"><img src="https://agentmods.dev/badge/skills/modiqo/skillspec/prose_only.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 | $0.00028 | $0.00469 |
| Opus 5 | $0.00014 | $0.00234 |
| Sonnet 5 | $0.00006 | $0.00094 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
browser-research-prose 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 5d 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.
Do not use curl, static HTML fetches, or search snippets as substitutes for What it actually says
Browser Research
Use this skill when the user asks you to browse a website, open a page, click through an interface, inspect page content, take a snapshot, extract evidence from a page, or verify what a page currently shows.
For browser tasks, use browser automation. Do not answer from native search when the user asked you to observe a page. Native search can be used only to discover the likely URL when the user did not provide one, and it must not be presented as page evidence.
If the user provides a URL, open that URL in the browser and inspect the page directly. If the user names a page but does not provide a URL, ask for the URL unless there is a clear, low-risk discovery path. If discovery is needed, search only long enough to identify the target URL, then switch to browser automation and verify the page itself.
Do not use curl, static HTML fetches, or search snippets as substitutes for browser evidence when the task depends on rendered page state, navigation, logged-in state, screenshots, dynamic content, or visible UI.
Before taking action, make sure a browser session is available and that network access is allowed. If a login, credential, or private workspace is needed, stop and ask before proceeding.
When the work is done, report what page was opened, what evidence was observed, which route was used, and any limitations. If there was URL discovery before browser inspection, say so clearly.
Good behavior examples:
- "browse https://example.com and take a snapshot" means open that URL in the browser and report browser evidence.
- "inspect the latest docs page but I do not have the URL" means discover the likely URL first, then verify the page in the browser.
- "summarize search results about this company" is not a browser-inspection task unless the user asks to open or inspect a page.
This skill relies on the agent following the prose carefully. There is no separate validation command, scenario test, dependency preflight, or trace contract in this prose-only version.
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.
- 5d ago First seen · 48 lines · 28 tokens per session scan A 007be7ea7823
browser-research-prose is a skill published in the GitHub repository modiqo/skillspec (739 stars, last pushed 27d ago), licensed Apache-2.0. It adds 28 tokens to every session and 469 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
v8-jit
V8 JIT optimization patterns for writing high-performance JavaScript in Next.js server internals. Use when writing or reviewing hot-path code in app-render, stream-utils, routing, caching, or any per-request code path. Covers hidden classes / shapes, monomorphic call sites, inline caches, megamorphic deopt, closure…
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
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…
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.
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.