القائمة
Submit a URL to the Wayback Machine for archiving. Use when the user wants to archive a webpage, save a page to the Internet Archive, preserve a URL, or create a snapshot.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | wayback-submit |
| description | Submit a URL to the Wayback Machine for archiving. Use when the user wants to archive a webpage, save a page to the Internet Archive, preserve a URL, or create a snapshot. |
Submit a URL to the Internet Archive's Wayback Machine using the Save Page Now 2 (SPN2) API.
npx tsx scripts/submit.ts <url> [options]
| Argument | Required | Description |
|---|---|---|
url | Yes | URL to archive |
| Option | Description |
|---|---|
--no-raw | Include Wayback toolbar in archived URL |
--key=ACCESS:SECRET | Use API authentication (get keys at https://archive.org/account/s3.php) |
When submission succeeds:
✓ Archive submitted successfully
Job ID: spn2-abc123...
Check status: https://web.archive.org/save/status/spn2-abc123...
Waiting for capture...
✓ Capture complete
URL: https://web.archive.org/web/20240115123456id_/https://example.com
npx tsx scripts/submit.ts <url> [options]
Options:
--no-raw - Include Wayback toolbar in archived URL--key=ACCESS:SECRET - Use API authenticationRun from the wayback plugin directory: ~/.claude/plugins/cache/wayback/
Get API keys at https://archive.org/account/s3.php (requires free account).
Header format:
Authorization: LOW {access_key}:{secret_key}
| Limit | Authenticated | Anonymous |
|---|---|---|
| Concurrent captures | 12 | 6 |
| Daily captures | 100,000 | 4,000 |
| Per-URL daily | 10 | 10 |
| Capture timeout | 50s page load, 2min total |
Endpoint: POST https://web.archive.org/save
curl -X POST https://web.archive.org/save \
-H "Accept: application/json" \
-H "Authorization: LOW myaccesskey:mysecret" \
-d "url=https://example.com"
| Parameter | Description |
|---|---|
url | URL to archive (required) |
capture_all=1 | Capture even 4xx/5xx error pages |
capture_outlinks=1 | Also archive linked pages (first 100) |
capture_screenshot=1 | Generate PNG screenshot |
delay_wb_availability=1 | Delay indexing ~12 hours (reduces load) |
skip_first_archive=1 | Skip check if URL was already archived |
if_not_archived_within=30d | Skip if archived within timeframe (e.g., 30d, 1h) |
js_behavior_timeout=10 | Run JavaScript for N seconds (max 30) |
force_get=1 | Use simple HTTP GET instead of browser |
capture_cookie=name=value | Include custom cookie in request |
target_username / target_password | Login credentials for protected pages |
Success:
{
"url": "https://example.com",
"job_id": "spn2-abc123..."
}
curl "https://web.archive.org/save/status/{job_id}" \
-H "Authorization: LOW myaccesskey:mysecret"
Pending:
{"status": "pending", "resources": []}
Success:
{
"status": "success",
"timestamp": "20240115123456",
"original_url": "https://example.com",
"resources": ["https://example.com/style.css"],
"outlinks": {},
"screenshot": "https://web.archive.org/web/.../screenshot.png"
}
Error codes: error:blocked-url, error:too-many-daily-captures, error:soft-time-limit-exceeded, error:invalid-host-resolution
curl "https://web.archive.org/save/status/user" \
-H "Authorization: LOW myaccesskey:mysecret"
Returns: {"available": 99950, "processing": 2}
For quick one-off saves without authentication:
https://web.archive.org/save/{URL}
Lower rate limits apply (6 concurrent, 4k daily).
delay_wb_availability=1 for batch jobs (reduces server load)capture_screenshot=1 for visual verificationUse when the user needs help with path queries, JSON transformations, schema validation, or safe JSON editing workflows. Triggered by questions about JSON operations, data extraction, file merging, or validation strategies.
Scan project dependencies for known vulnerabilities. Automatically detect and parse package files (package.json, requirements.txt, Gemfile, go.mod, pom.xml) and check all dependencies against the CVE database. Use when you want to audit a project for security vulnerabilities, check if dependencies have known CVEs, or generate a vulnerability report for compliance.
Search for Common Vulnerabilities and Exposures (CVEs) by ID (e.g., CVE-2024-1086) or by product name (e.g., OpenSSL, Apache Tomcat). Get detailed vulnerability information including severity scores, affected software versions, and references. Use when the user wants to look up CVE information, check if a product has known vulnerabilities, or research security issues.
Validate a JSON file against the schema referenced in its $schema property. Use when the user asks to check JSON against its own schema, validate self-describing JSON, auto-validate JSON files, or verify JSON with embedded schema reference.
Validate JSON data against a JSON Schema. Use when the user asks to validate JSON against a schema, check if JSON conforms to a schema, test JSON data validity, or verify JSON structure matches a schema definition.
Validate that a JSON Schema is well-formed and conforms to the JSON Schema specification. Use when the user asks to check if a schema is valid, verify schema syntax, validate schema structure, or check a JSON Schema file for errors.