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/icosaedro-git/toolsnap-mcp/toolsnapnpx skills add icosaedro-git/toolsnap-mcp --skill toolsnapgit clone --depth 1 https://github.com/icosaedro-git/toolsnap-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/icosaedro-git/toolsnap-mcp/toolsnap)<a href="https://agentmods.dev/skills/icosaedro-git/toolsnap-mcp/toolsnap"><img src="https://agentmods.dev/badge/skills/icosaedro-git/toolsnap-mcp/toolsnap.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.00013 | $0.01039 |
| Opus 5 | $0.00006 | $0.00519 |
| Sonnet 5 | $0.00003 | $0.00208 |
| Haiku 4.5 | $0.00001 | $0.00104 |
Grade A, and why
toolsnap 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 4d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ToolSnap Skill
Extract exact, reproducible data from web pages and documents through the ToolSnap MCP server, which parses server-side and returns only the answer — large pages never enter the context window. It does not search the web and does not drive a browser; discovery and interaction stay with native tools.
When to Use
- Quoting or citing a page exactly, where an LLM summary could drift
- Turning HTML tables, CSV/JSON files, PDFs, RSS feeds, or sitemaps into structured data
- Querying a large dataset for a few rows instead of loading the whole file
- Auditing SEO metadata (title/canonical/og:*, JSON-LD) as data
- Checking token cost of a document before ingesting it
Keep native web_search for discovery (ToolSnap does not search) and
browser_navigate for JS-heavy SPAs, logins, and page interaction.
Prerequisites
The toolsnap MCP server, installed from the catalog:
hermes mcp install official/toolsnap
It is a remote server on Cloudflare Workers (streamable HTTP) — nothing runs locally and the free tools need no account, API key, or configuration.
How to Run
Call the MCP tools directly. Only a curated core appears in tools/list;
the rest of the catalog is reachable through two meta-tools:
tool_catalog()— families overview;tool_catalog(family="...")ortool_catalog(tool="...")returns a tool's schema.use_tool(name="...", args={...})— execute any cataloged tool, same behavior as a direct call.task_recipes()— ready multi-tool plans (clone a site, SEO audit, …).
Quick Reference
| Task | Tool |
|---|---|
| Quote or cite a page exactly | fetch_extract |
| Rebuild / migrate a page (clean DOM) | fetch_html |
| Tables on a page → JSON/CSV | html_table_extract |
| Query a big CSV/JSON without loading it | csv_query / json_query |
| PDF text | pdf_text_extract |
| Feeds, sitemaps, link audits | rss_parse / sitemap_parse / link_check |
| SEO metadata and JSON-LD | fetch_metadata / fetch_structured |
| Token budget check before ingesting | count_tokens |
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.
- 4d ago First seen · 103 lines · 13 tokens per session scan A e611c9419bcb
toolsnap is a skill published in the GitHub repository icosaedro-git/toolsnap-mcp (1 stars, last pushed 7d ago), licensed MIT. It adds 13 tokens to every session and 1,039 once invoked, about $0.0001 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
update-saasmail
Sync the local saasmail repo with the latest upstream changes from https://github.com/choyiny/saasmail. Use this skill whenever the user wants to update saasmail, pull upstream changes, sync with upstream, rebase on upstream, get the latest saasmail, or says "/update-saasmail". Handles adding the upstream remote if…
story-html-publisher
Final step of the AI Storybook pipeline. Consolidates the scenes, images, and per-scene audio into ONE self-contained HTML storybook — a swipe/tap player with every image and audio clip embedded as base64 so the single file works offline and can be shared as-is. Reads {slug}scenes.json, {slug}images.json, and…
Beads Workflow Optimizer
Optimizes Beads workflow activation, parallel processing, and task management. Use when working with Beads issues, managing dependencies, or optimizing development workflows in projects with complex task dependencies.
live-drift-resolution
Resolve a "Live service drift detected" issue — the daily CI that diffs the committed catalog against the live upstream surfaces (Lumenloop, Stellar Light/Scout, Stellar Docs). Regenerate the artifacts, classify the drift, decide whether it needs a policy or routing-baseline change or is a clean mechanical bump…
gjsify-publishing
Read BEFORE adding a new @gjsify/ package name, before running gjsify onboard/gjsify publish/gjsify trust, and before cutting or re-running a release. Covers the manual npm first-publish + Trusted Publisher bootstrap that OIDC requires, and the publish-order/closure rules that keep a partial release from shipping an…
review-pnpm
Review the pnpm workspace configuration for alignment with current official best practices - dependency management, supply-chain safety, and developer experience across this monorepo. Your reply must be a plan of suggested changes: concise, actionable, structured - not only prose.