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 divinevideo/divine-mobile --skill wayback-machine-raw-content-id-modifiergit clone --depth 1 https://github.com/divinevideo/divine-mobileWrote 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/divinevideo/divine-mobile/wayback-machine-raw-content-id-modifier)<a href="https://agentmods.dev/skills/divinevideo/divine-mobile/wayback-machine-raw-content-id-modifier"><img src="https://agentmods.dev/badge/skills/divinevideo/divine-mobile/wayback-machine-raw-content-id-modifier/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/divinevideo/divine-mobile/wayback-machine-raw-content-id-modifier"><img src="https://agentmods.dev/badge/skills/divinevideo/divine-mobile/wayback-machine-raw-content-id-modifier.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00102 | $0.00966 |
| Opus 5.5 | $0.00041 | $0.00386 |
| Sonnet 5.5 | $0.00020 | $0.00193 |
| Haiku 4.5 | $0.00010 | $0.00097 |
Grade A, and why
wayback-machine-raw-content-id-modifier 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 1mo 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.
1. Test the URL with curl to see actual response: 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.
Wayback Machine Raw Content with id_ Modifier
Problem
When fetching archived JSON API endpoints from the Wayback Machine, you get HTML-wrapped
content with the Wayback toolbar instead of the raw JSON response. This causes JSON parse
errors like "Expecting value: line 1 column 1 (char 0)" because the response starts with
<!DOCTYPE html> instead of valid JSON.
Context / Trigger Conditions
- Fetching archived API endpoints from
web.archive.org/web/{timestamp}/{url} - JSON parsing fails with "Expecting value: line 1 column 1 (char 0)"
- Response content starts with HTML instead of expected JSON
- Crawling archived REST APIs, JSON feeds, or any non-HTML content from Wayback
- Using Python
json.loads(),response.json(), or similar JSON parsing
Solution
Add id_ after the timestamp in the Wayback URL to get raw content:
Default (HTML-wrapped):
https://web.archive.org/web/20170112012313/https://vine.co/api/users/profiles/123
Raw content (add id_):
https://web.archive.org/web/20170112012313id_/https://vine.co/api/users/profiles/123
Code Fix Pattern
# BEFORE (broken - returns HTML)
url = f"https://web.archive.org/web/{timestamp}/https://example.com/api/data"
# AFTER (works - returns raw JSON)
url = f"https://web.archive.org/web/{timestamp}id_/https://example.com/api/data"
Other Wayback Modifiers
id_- Raw/identity (no modifications, returns original content)if_- Iframe embed modejs_- JavaScript rewriting modecs_- CSS rewriting modeim_- Image mode
Verification
-
Test the URL with curl to see actual response:
# Without id_ - shows HTML with Wayback toolbar curl -s "https://web.archive.org/web/20170112012313/https://example.com/api/data" | head -5 # With id_ - shows raw JSON curl -s "https://web.archive.org/web/20170112012313id_/https://example.com/api/data" | head -5 -
Verify JSON parsing works:
import json import urllib.request url = f"https://web.archive.org/web/{timestamp}id_/{api_url}" with urllib.request.urlopen(url) as resp: data = json.loads(resp.read()) # Should work now
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.
- 1mo ago First seen · 103 lines · 102 tokens per session scan A 3931d1c52da1
wayback-machine-raw-content-id-modifier is a skill published in the GitHub repository divinevideo/divine-mobile (264 stars, last pushed today), licensed MPL-2.0. It adds 102 tokens to every session and 966 once invoked, about $0.0004 per session on Opus 5.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-09-03.
Other skills, from other repositories
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…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.