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/bowmark-ai/skill/bowmarknpx skills add bowmark-ai/skill --skill bowmarkgit clone --depth 1 https://github.com/bowmark-ai/skillWhat 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.00263 | $0.03770 |
| Opus 5 | $0.00131 | $0.01885 |
| Sonnet 5 | $0.00053 | $0.00754 |
| Haiku 4.5 | $0.00026 | $0.00377 |
Grade A, and why
bowmark 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 yesterday.
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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
bowmark
The web as callable functions. Read the library, write a script, get the result.
The loop
- Call
get_library({ query })—queryis what you want to DO ("flights","price a GPU"), or a company if you specifically want one ("Kayak"). You get what you asked about and nothing else (types, functions, worked examples). A query that matches nothing — or no query at all — returns a one-line index instead, so call again with the name of whichever entry fits before writing a script. Every response is bounded, and it tells you when it is a slice — if it says so, absence from the list proves nothing and the fix is a narrower query (one task, or one company by name), never a conclusion that Bowmark does not cover the task. - Write a short async JavaScript script against the
bowmarkglobal, using the exact function names, argument shapes and return types the library gave you. - Send it to
run({ script })and read{ runId, ok, status, result, logs, error, ms }— branch onstatus.
If Bowmark was missing, wrong, or incomplete, call report({ report, runId? }). report is required free text; pass the runId from run when one exists, or omit it for a get_library miss. It records feedback and never retries the run.
Two tiers: capabilities and providers
Capabilities are the default and usually what you want. bowmark.flights.search(...) is one call that fans out across several aggregators, adapts each one's output into a single normalized shape, dedupes the same physical flight across them, ranks the results, and keeps working when one site is down.
Providers are the individual sites, callable directly at bowmark.providers.<provider>.<fn>(...) — bowmark.providers.kayak.search(...). They appear in the library only when your query named a company, or when the capability has exactly one provider behind it (so there is no abstraction to protect).
Choose the provider tier when the user asked for that specific site — "check Kayak", "what does Newegg have". Choose the capability otherwise. Naming a site the user didn't name is a downgrade, not a courtesy:
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.
- yesterday First seen · 183 lines · 263 tokens per session scan A ef636871effa
bowmark is a skill published in the GitHub repository bowmark-ai/skill (0 stars, last pushed 2d ago), licensed MIT. It adds 263 tokens to every session and 3,770 once invoked, about $0.0013 per session on Opus 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
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…
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
playwright
Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via playwright-cli or the bundled wrapper script.
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.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.