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 cyanheads/internet-archive-mcp-server --skill internet-archive-guidegit clone --depth 1 https://github.com/cyanheads/internet-archive-mcp-serverWrote 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/cyanheads/internet-archive-mcp-server/internet-archive-guide)<a href="https://agentmods.dev/skills/cyanheads/internet-archive-mcp-server/internet-archive-guide"><img src="https://agentmods.dev/badge/skills/cyanheads/internet-archive-mcp-server/internet-archive-guide/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/cyanheads/internet-archive-mcp-server/internet-archive-guide"><img src="https://agentmods.dev/badge/skills/cyanheads/internet-archive-mcp-server/internet-archive-guide.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.00044 | $0.00959 |
| Opus 5.5 | $0.00018 | $0.00384 |
| Sonnet 5.5 | $0.00009 | $0.00192 |
| Haiku 4.5 | $0.00004 | $0.00096 |
Grade A, and why
internet-archive-guide 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 — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scope
Use historical captures to establish what a page said at a captured time, and library items to investigate a particular edition or document. For the current page, use the live site. For page layout or raw HTML, follow the returned replay URL: snapshot text removes markup and can retain navigation alongside the page's content.
Identifiers
- Keep a web page's original URL separate from its Wayback replay URL.
ia_find_snapshotssupplies capture timestamps and replay URLs;ia_get_snapshottakes the original URL and a timestamp. - Take an item identifier from
ia_search_items, then retain it while inspecting metadata and reading text. A title identifies a candidate, not an edition. Collection values returned with items are collection identifiers; use those values rather than guessing an identifier from a collection's display name. - Take filenames and download URLs from
ia_get_item. Text pages name their selectedsource_file; retain that filename with the item identifier when citing a passage. - Keep history
resume_keyand textnext_continuationtokens separate. Both come from the preceding response in their own workflow; neither is an item identifier or a timestamp.
Gates
- Date the content actually served. Before comparing or citing captures, check
ia_get_snapshot's resolved timestamp and replay URL. Wayback can redirect a requested capture to another capture; the requested date alone does not date the returned text. - Establish history coverage before claiming a change was absent. Daily collapse can hide changes within a day. Use capture-second precision for that question, follow history continuations, and retain any incompleteness notice. Wildcard and legacy raw continuations can omit captures across pages; they cannot support an exhaustive-history claim.
- Distinguish absence from failure. A lookup outage does not establish that a URL was never captured. An archived error page does not contain the requested page's content; look for a successful capture. When the error says Wayback does not serve the URL at any timestamp, stop trying other dates for that URL and look for a different original URL.
- Inspect the manifest before declaring text unavailable. A filtered or partial file page is not the complete manifest. No
DjVuTXTmatch alone does not rule out plain text:ia_get_textalso considers other text formats and.txtfiles. A forbidden download means restricted access, not a missing item; use the Archive website for that access path. - Finish reading before claiming a document was searched completely. Continue until
has_moreis false. Keep the selected source filename consistent; the file's byte size is not a text length. If a text continuation becomes invalid, follow the recovery offset or restart when the file changed rather than joining pages from different representations. - Check search coverage before declaring an item absent. An empty page can be past the last result. A broad search cannot expose results beyond the 10,000-result window; narrow by metadata to investigate the remaining set. A snapshot's capped text likewise cannot establish that a phrase is absent from the full archived page.
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 · 37 lines · 44 tokens per session scan A c5f9a8c9df0f
internet-archive-guide is a skill published in the GitHub repository cyanheads/internet-archive-mcp-server (4 stars, last pushed 2d ago), licensed Apache-2.0. It adds 44 tokens to every session and 959 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-10-28.
Other skills, from other repositories
stackexchange-guide
Find, read, and cite Stack Overflow and other Stack Exchange answers with the stackexchange tools — resolving site and IDs from URLs, search syntax for error messages and tags, choosing which answer to trust, vetting an author, and budgeting the daily API quota. Use when answering from Stack Exchange content, quoting…
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…
add-tool
Scaffold a new MCP tool definition. Use when the user asks to add a tool, create a new tool, or implement a new capability for the server.
design-mcp-server
Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.
api-context
Canonical reference for the unified Context object passed to every tool and resource handler in @cyanheads/mcp-ts-core. Covers the full interface, its RequestContext base, all sub-APIs (ctx.log, ctx.state, ctx.requestInput, ctx.inputs, ctx.clientCapabilities, ctx.enrich, ctx.content), and when to use each.
api-errors
McpError constructor, JsonRpcErrorCode reference, and error handling patterns for @cyanheads/mcp-ts-core. Use when looking up error codes, understanding where errors should be thrown vs. caught, or using ErrorHandler.tryCatch in services.