[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77VT6B27WJHQ6X0AP70QHXA":3,"skill-same:01M77VT6B27WJHQ6X0AP70QHXA":56},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M77VT6B27WJHQ6X0AP70QHXA","read-deleted-pages",null,"Recover deleted, edited or historical web content using the Wayback Machine and its CDX API, archive.today, Common Crawl and Memento\u002FTimetravel. Use when a page is deleted, changed or 404s, checking what a site used to say, finding old team or staff pages, prior pricing, removed posts, pre-redaction wording or old contact details, enumerating every archived URL for a domain, or preserving evidence before it disappears. Applies to litigation and evidence preservation, regulatory and disclosure review, due diligence on a company's history, and journalism. Reference at useosint.com\u002Fskills\u002Fread-deleted-pages.","Reihantt6\u002Fsns-myagent","Reihantt6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F219822095?v=4","01M77KK94PV8B7C2D9XWXNS8DJ","Mohamad Reihan tegar prasetya","01M77KK958QFMTHYXGXFV7KZ79",2,"MIT","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fread-deleted-pages\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"Recover deleted, edited or historical web content using the Wayback Machine and its CDX API, archive.today, Common Crawl and Memento\u002FTimetravel. Use when a page is deleted, changed or 404s, checking what a site used to say, finding old team or staff pages, prior pricing, removed posts, pre-redaction wording or old contact details, enumerating every archived URL for a domain, or preserving evidence before it disappears. Applies to litigation and evidence preservation, regulatory and disclosure review, due diligence on a company's history, and journalism. Reference at useosint.com\u002Fskills\u002Fread-deleted-pages.\"\n---\n# Read deleted pages\n\nArchives work because removal is a decision made after publication. The\nbeginner's mistake is treating the Wayback Machine as a website you browse: the\ncalendar UI shows one page at a time, while the CDX API enumerates every URL the\narchive ever saw under a host, including paths nobody remembers.\n\n## Which archive first\n\n| Situation | Go to | Why |\n|---|---|---|\n| A URL that 404s now | Wayback, then archive.today | Different corpora, different removal pressure |\n| \"What did this site say before X\" | Wayback CDX with `collapse=digest` | Gives the dates content changed, not every capture |\n| A JS-heavy page or a social post | archive.today | Captures the rendered DOM; Wayback often replays an empty shell |\n| Wayback says the URL is excluded | archive.today, then Common Crawl | Neither answers to Wayback's exclusion process |\n| Paths and subdomains you don't know about | CDX with `matchType=domain` | It is an enumeration tool, not a lookup tool |\n| A URL Wayback never captured | Common Crawl | Independent crawler, different seeds |\n| Regional or national-TLD content | A Memento aggregator, then the national archive | Some national archives offer full-text search |\n| Evidence you cannot lose | Capture it yourself, then submit to two archives | Nobody else is preserving it for you |\n\nCoverage and removal policy per source:\n[reference\u002Farchive-comparison.md](reference\u002Farchive-comparison.md).\n\n## The CDX API is the actual tool\n\nThe CDX server indexes capture records — one row per capture — and lets you\nfilter, collapse and enumerate them. Every URL a crawler ever saw under a host,\ndeduplicated:\n\n```bash\ncurl -s 'http:\u002F\u002Fweb.archive.org\u002Fcdx\u002Fsearch\u002Fcdx?url=example.com\u002F*&output=json&fl=original&collapse=urlkey' \\\n  | jq -r '.[1:][] | .[0]' | sort -u\n```\n\nUse `output=json` rather than the default text: it survives URLs containing\nspaces and quotes, which the text format mangles. The first JSON row is a header\nnaming the columns, not a capture — hence the `.[1:]`.\n\nFour parameters do nearly all the work:\n\n- **`matchType`** — `exact`, `prefix`, `host`, or `domain`. `matchType=domain`\n  returns the host *and all subdomains*, routinely surfacing staging, legacy and\n  internal hosts long gone from DNS. Take them to `find-hidden-subdomains`.\n- **`filter=\u003Cfield>:\u003Cregex>`**, invertible with `!` and combinable. Filter to\n  `statuscode:200` for captures that returned content, or `!mimetype:text\u002Fhtml`\n  to isolate documents, archives and config files.\n- **`from`\u002F`to`** take a timestamp prefix at any precision — `from=2019`,\n  `from=201903` — so you can bracket the window around a known event.\n- **`collapse`** suppresses adjacent rows sharing a field. `collapse=urlkey` is\n  the enumeration idiom; `collapse=digest` matters most.\n\n`digest` hashes the captured payload, so `collapse=digest` reduces a page's\nhistory to the captures where content actually *changed*. Four hundred captures\nbecome six rows, and those six dates are the story.\n\n```bash\ncurl -s 'http:\u002F\u002Fweb.archive.org\u002Fcdx\u002Fsearch\u002Fcdx?url=example.com\u002Fabout\u002Fteam&output=json&collapse=digest&fl=timestamp,digest,statuscode'\n```\n\nFull parameters, paging, and a ready enumeration pass: [reference\u002Fcdx-cookbook.md](reference\u002Fcdx-cookbook.md).\n\n## Replay is not the capture\n\nThe page at `web.archive.org\u002Fweb\u002F\u003Ctimestamp>\u002F\u003Curl>` is reconstructed. The\narchive injects a toolbar, rewrites links and resource references back into the\narchive, and — the part that misleads people — pulls each resource from *its own\nnearest capture*, which may be months away from the HTML you asked for. The\nrendered page you screenshot may never have existed.\n\nAppend `id_` to the timestamp to get the raw archived response with no injection\nand no rewriting:\n\n```bash\ncurl -s 'https:\u002F\u002Fweb.archive.org\u002Fweb\u002F20190412093000id_\u002Fhttp:\u002F\u002Fexample.com\u002Fpricing' > pricing-2019.html\n```\n\nUse `id_` for anything you will parse, hash, diff, or cite. A page that replays\nas blank may have been captured fine, so fetch the raw response before\nconcluding the archive has nothing — but archived JavaScript that called an API\nat view time has no data behind it, because the API response was never captured.\nThose pages are shells by nature, not by failure.\n\n## What this actually recovers\n\nPull the raw captures at two dates from the `collapse=digest` list and compare\nthem as text. The removals are the evidence: a person deleted from a team page\nbetween two dates is a departure with a date range attached, and a `find-anyone`\nlead with no remaining reason to be loyal. What surfaces, in practice:\n\n- **Staff and team pages.** The current site lists who is there now; the archive\n  lists everyone who ever was, with titles, bios, and often direct email\n  addresses from before the org moved to a contact form.\n- **Prior pricing and terms** — what was charged, what was promised, and what\n  the refund policy said on the date a dispute began. Also removed posts and\n  press releases: partnerships, funding or clients both sides stopped mentioning.\n- **Old contact details.** Phone numbers, street addresses and named individual\n  contacts later replaced by a form. Straight into `whose-number-is-this`.\n- **Pre-redaction copy.** Diffing a page published in full against its edited\n  successor shows exactly which words somebody paid a lawyer to remove — a very\n  strong signal about what matters.\n- **Forgotten files** — document paths, backup filenames and admin surfaces\n  indexed once and never cleaned up. See `secrets-in-git-history`.\n- **The prior owner of a domain.** A domain that changed hands shows a different\n  business in its archive history — the fastest way to spot a\n  reputation-laundering purchase.\n\n## Preserve it before you look further\n\nAnything you find can be removed, and investigating sometimes causes the\nremoval. Capture first, analyse second.\n\nSubmit the live URL to the Internet Archive's Save Page Now at\n`https:\u002F\u002Fweb.archive.org\u002Fsave\u002F` and to archive.today, so two independent\norganisations hold a timestamped copy you did not create. Then take your own\nrecord: a WARC preserves the full HTTP exchange including headers, which a\nscreenshot does not.\n\n```bash\nwget --warc-file=evidence-001 --page-requisites --no-parent https:\u002F\u002Fexample.com\u002Fpricing\nsha256sum evidence-001.warc.gz | tee evidence-001.sha256\n```\n\nRecord the capture time in UTC, the URL exactly as requested, and the hash. A\nscreenshot alone is weak — trivially forged, no headers. A third-party archive\nURL plus your own hashed WARC is strong, because they corroborate each other and\none is outside your control. That is what `write-the-intel-brief` expects.\n\n## Verifying a capture is genuine\n\nAnyone can put content into an archive: both Save Page Now and archive.today\naccept arbitrary URLs from anonymous submitters. A capture proves *that URL\nserved that content to that crawler at that time*, and nothing about who\ncontrolled the URL. The realistic spoofing routes:\n\n- **A forged screenshot of an archive page.** Trivial. Never accept a screenshot\n  of an archive; work from the archive URL itself and re-fetch it.\n- **Content injected via the URL.** A reflected query parameter, a\n  user-generated content path or an open redirect lets someone archive\n  attacker-chosen text on a legitimate-looking domain. Read the `original` field\n  character by character: anything after `?` or `#`, any unfamiliar path\n  segment, any lookalike host.\n- **Capture after a domain changed hands.** The domain was the buyer's, not the\n  original business's. Check transfer dates against the capture timestamp with\n  `who-owns-this-domain`.\n- **Selective capture** — a real page up for eleven minutes, archived by the\n  person who put it up.\n\nCorroboration, in order of strength: confirm the record exists independently in\nthe CDX index with `statuscode` 200 and a `digest`; look for adjacent captures\nmade by the archive's own crawler rather than by on-demand submission, since\ncrawler captures are much harder to stage; check a second independent archive\nnear the same date; check consistency with the site's other history. A lone\non-demand capture with no neighbours is an assertion by its submitter.\n\n## Where this goes wrong\n\n- **Absence is not evidence.** No capture means unlinked, robots-blocked, behind\n  a login, too obscure to crawl, or removed — not that the page never existed.\n  Check two archives before writing \"no record\".\n- **Exclusion looks like absence.** An explicit exclusion notice means somebody\n  acted; a plain 404 means nothing. Different facts — note which you got.\n- **Retroactive removal.** Wayback has historically applied a site's *current*\n  robots.txt to its whole archive history, so a new `Disallow` could pull years\n  of captures at once — making an expired-domain purchase plus a restrictive\n  robots.txt a cheap way to launder a site's past. The practice has narrowed,\n  but go to archive.today and Common Crawl when a history looks too clean.\n- **Composite renders.** Mixed-date resources mean the rendered page is a\n  reconstruction. Cite the HTML capture timestamp, not \"how it looked\".\n- **Capture time is not publication time.** A page first captured in March may\n  have been published in January. The capture bounds the date from above only.\n- **Dynamic and personalised content.** The crawler saw one variant — one\n  geography, one A\u002FB bucket, logged out. Prices and availability especially.\n- **Sparse sampling hides everything.** A page captured twice a year can change\n  and revert with no trace; `collapse=digest` shows observed changes, not all\n  changes. Timestamps are UTC, and forgetting that breaks a timeline by a day.\n\n## Confidence grading\n\n- **Confirmed** — a crawler-initiated capture with `statuscode:200`, retrieved\n  raw with `id_`, on a URL verified as the subject's, corroborated by a second\n  archive or by adjacent captures in the same crawl series.\n- **Probable** — a single well-formed Wayback capture with no second source, or\n  an archive.today capture consistent with the site's other history.\n- **Unconfirmed** — an on-demand capture with no neighbours; a URL carrying\n  query parameters or user-generated content paths; a screenshot; content read\n  from a composite replay rather than the raw response.\n- **Rejected** — a capture whose URL was not under the subject's control at that\n  date, or one taken after a domain transfer and presented as the prior owner's.\n\nCite the full archive URL with timestamp, the original URL, the capture time in\nUTC, and how you retrieved it. An archive citation without a timestamp is not a\ncitation.\n\n## Worked example\n\nA supplier's site claims an industry certification. The client wants it verified\nbefore signing.\n\n`collapse=digest` on the certifications page returns nine content changes over\nsix years. The raw captures either side of the most recent one show the\ncertification body's name changed — from a recognised accreditor to a similarly\nnamed entity — with no announcement.\n\nThe dead end: the accreditor's own register has no live entry either way, and\nits archived member lists replay as empty shells. Fetching them with `id_` shows\nwhy — the list was rendered client-side from an API call, so the crawler\ncaptured a page with no data in it. Nothing recoverable there.\n\nCDX enumeration on `matchType=domain` then turns up a staging host holding an\narchived PDF of the original certificate. Its metadata carries an expiry date\ntwo years before the current site claims coverage, and\n`secrets-in-file-metadata` gets an author name from the same file.\n\nGrade: the wording change **confirmed** — two crawler captures, raw, both read.\nThe lapse **probable** — one document, no confirmation from the accreditor.\n\n## Pivots\n\n| New selector | Goes to |\n|---|---|\n| Former staff names, titles, bios | `find-anyone`, `pattern-of-life-from-socials` |\n| Email addresses from pre-form contact pages | `what-an-email-reveals` |\n| Phone numbers and street addresses | `whose-number-is-this` |\n| Subdomains and hosts from CDX enumeration | `find-hidden-subdomains`, `who-owns-this-domain` |\n| Archived documents and PDFs | `secrets-in-file-metadata` |\n| Archived images | `find-the-original-image`, `geolocate-from-pixels` |\n| Forgotten paths and exposed file names | `google-like-a-spy`, `secrets-in-git-history` |\n| Prior corporate identity of a domain | `x-ray-a-company`, `who-really-owns-it` |\n| A timeline of edits and removals | `write-the-intel-brief`, `graph-the-network` |\n\n## Legal and handling notes\n\nReading an archive is passive; it touches the archive's servers, not the\ntarget's. Fetching a recovered path against the live site is not passive and\nlands in the target's logs — decide deliberately which you are doing.\n\nArchived personal data is still personal data. Content removed under a\nright-to-erasure request may persist in archives, and republishing it can create\nthe liability the removal was meant to extinguish. Weigh the investigative need\nagainst the reason for removal, and minimise per\n[..\u002F..\u002FETHICS.md](..\u002F..\u002FETHICS.md). Reproducing substantial archived content in\na published report is a separate copyright question from using it as evidence.\n\nBulk retrieval strains a nonprofit's infrastructure: rate-limit enumeration and\nraw fetches, and pull the index once rather than repeatedly.\n","# Read deleted pages\n\nArchives work because removal is a decision made after publication. The\nbeginner's mistake is treating the Wayback Machine as a website you browse: the\ncalendar UI shows one page at a time, while the CDX API enumerates every URL the\narchive ever saw under a host, including paths nobody remembers.\n\n## Which archive first\n\n| Situation | Go to | Why |\n|---|---|---|\n| A URL that 404s now | Wayback, then archive.today | Different corpora, different removal pressure |\n| \"What did this site say before X\" | Wayback CDX with `collapse=digest` | Gives the dates content changed, not every capture |\n| A JS-heavy page or a social post | archive.today | Captures the rendered DOM; Wayback often replays an empty shell |\n| Wayback says the URL is excluded | archive.today, then Common Crawl | Neither answers to Wayback's exclusion process |\n| Paths and subdomains you don't know about | CDX with `matchType=domain` | It is an enumeration tool, not a lookup tool |\n| A URL Wayback never captured | Common Crawl | Independent crawler, different seeds |\n| Regional or national-TLD content | A Memento aggregator, then the national archive | Some national archives offer full-text search |\n| Evidence you cannot lose | Capture it yourself, then submit to two archives | Nobody else is preserving it for you |\n\nCoverage and removal policy per source:\n[reference\u002Farchive-comparison.md](reference\u002Farchive-comparison.md).\n\n## The CDX API is the actual tool\n\nThe CDX server indexes capture records — one row per capture — and lets you\nfilter, collapse and enumerate them. Every URL a crawler ever saw under a host,\ndeduplicated:\n\n```bash\ncurl -s 'http:\u002F\u002Fweb.archive.org\u002Fcdx\u002Fsearch\u002Fcdx?url=example.com\u002F*&output=json&fl=original&collapse=urlkey' \\\n  | jq -r '.[1:][] | .[0]' | sort -u\n```\n\nUse `output=json` rather than the default text: it survives URLs containing\nspaces and quotes, which the text format mangles. The first JSON row is a header\nnaming the columns, not a capture — hence the `.[1:]`.\n\nFour parameters do nearly all the work:\n\n- **`matchType`** — `exact`, `prefix`, `host`, or `domain`. `matchType=domain`\n  returns the host *and all subdomains*, routinely surfacing staging, legacy and\n  internal hosts long gone from DNS. Take them to `find-hidden-subdomains`.\n- **`filter=\u003Cfield>:\u003Cregex>`**, invertible with `!` and combinable. Filter to\n  `statuscode:200` for captures that returned content, or `!mimetype:text\u002Fhtml`\n  to isolate documents, archives and config files.\n- **`from`\u002F`to`** take a timestamp prefix at any precision — `from=2019`,\n  `from=201903` — so you can bracket the window around a known event.\n- **`collapse`** suppresses adjacent rows sharing a field. `collapse=urlkey` is\n  the enumeration idiom; `collapse=digest` matters most.\n\n`digest` hashes the captured payload, so `collapse=digest` reduces a page's\nhistory to the captures where content actually *changed*. Four hundred captures\nbecome six rows, and those six dates are the story.\n\n```bash\ncurl -s 'http:\u002F\u002Fweb.archive.org\u002Fcdx\u002Fsearch\u002Fcdx?url=example.com\u002Fabout\u002Fteam&output=json&collapse=digest&fl=timestamp,digest,statuscode'\n```\n\nFull parameters, paging, and a ready enumeration pass: [reference\u002Fcdx-cookbook.md](reference\u002Fcdx-cookbook.md).\n\n## Replay is not the capture\n\nThe page at `web.archive.org\u002Fweb\u002F\u003Ctimestamp>\u002F\u003Curl>` is reconstructed. The\narchive injects a toolbar, rewrites links and resource references back into the\narchive, and — the part that misleads people — pulls each resource from *its own\nnearest capture*, which may be months away from the HTML you asked for. The\nrendered page you screenshot may never have existed.\n\nAppend `id_` to the timestamp to get the raw archived response with no injection\nand no rewriting:\n\n```bash\ncurl -s 'https:\u002F\u002Fweb.archive.org\u002Fweb\u002F20190412093000id_\u002Fhttp:\u002F\u002Fexample.com\u002Fpricing' > pricing-2019.html\n```\n\nUse `id_` for anything you will parse, hash, diff, or cite. A page that replays\nas blank may have been captured fine, so fetch the raw response before\nconcluding the archive has nothing — but archived JavaScript that called an API\nat view time has no data behind it, because the API response was never captured.\nThose pages are shells by nature, not by failure.\n\n## What this actually recovers\n\nPull the raw captures at two dates from the `collapse=digest` list and compare\nthem as text. The removals are the evidence: a person deleted from a team page\nbetween two dates is a departure with a date range attached, and a `find-anyone`\nlead with no remaining reason to be loyal. What surfaces, in practice:\n\n- **Staff and team pages.** The current site lists who is there now; the archive\n  lists everyone who ever was, with titles, bios, and often direct email\n  addresses from before the org moved to a contact form.\n- **Prior pricing and terms** — what was charged, what was promised, and what\n  the refund policy said on the date a dispute began. Also removed posts and\n  press releases: partnerships, funding or clients both sides stopped mentioning.\n- **Old contact details.** Phone numbers, street addresses and named individual\n  contacts later replaced by a form. Straight into `whose-number-is-this`.\n- **Pre-redaction copy.** Diffing a page published in full against its edited\n  successor shows exactly which words somebody paid a lawyer to remove — a very\n  strong signal about what matters.\n- **Forgotten files** — document paths, backup filenames and admin surfaces\n  indexed once and never cleaned up. See `secrets-in-git-history`.\n- **The prior owner of a domain.** A domain that changed hands shows a different\n  business in its archive history — the fastest way to spot a\n  reputation-laundering purchase.\n\n## Preserve it before you look further\n\nAnything you find can be removed, and investigating sometimes causes the\nremoval. Capture first, analyse second.\n\nSubmit the live URL to the Internet Archive's Save Page Now at\n`https:\u002F\u002Fweb.archive.org\u002Fsave\u002F` and to archive.today, so two independent\norganisations hold a timestamped copy you did not create. Then take your own\nrecord: a WARC preserves the full HTTP exchange including headers, which a\nscreenshot does not.\n\n```bash\nwget --warc-file=evidence-001 --page-requisites --no-parent https:\u002F\u002Fexample.com\u002Fpricing\nsha256sum evidence-001.warc.gz | tee evidence-001.sha256\n```\n\nRecord the capture time in UTC, the URL exactly as requested, and the hash. A\nscreenshot alone is weak — trivially forged, no headers. A third-party archive\nURL plus your own hashed WARC is strong, because they corroborate each other and\none is outside your control. That is what `write-the-intel-brief` expects.\n\n## Verifying a capture is genuine\n\nAnyone can put content into an archive: both Save Page Now and archive.today\naccept arbitrary URLs from anonymous submitters. A capture proves *that URL\nserved that content to that crawler at that time*, and nothing about who\ncontrolled the URL. The realistic spoofing routes:\n\n- **A forged screenshot of an archive page.** Trivial. Never accept a screenshot\n  of an archive; work from the archive URL itself and re-fetch it.\n- **Content injected via the URL.** A reflected query parameter, a\n  user-generated content path or an open redirect lets someone archive\n  attacker-chosen text on a legitimate-looking domain. Read the `original` field\n  character by character: anything after `?` or `#`, any unfamiliar path\n  segment, any lookalike host.\n- **Capture after a domain changed hands.** The domain was the buyer's, not the\n  original business's. Check transfer dates against the capture timestamp with\n  `who-owns-this-domain`.\n- **Selective capture** — a real page up for eleven minutes, archived by the\n  person who put it up.\n\nCorroboration, in order of strength: confirm the record exists independently in\nthe CDX index with `statuscode` 200 and a `digest`; look for adjacent captures\nmade by the archive's own crawler rather than by on-demand submission, since\ncrawler captures are much harder to stage; check a second independent archive\nnear the same date; check consistency with the site's other history. A lone\non-demand capture with no neighbours is an assertion by its submitter.\n\n## Where this goes wrong\n\n- **Absence is not evidence.** No capture means unlinked, robots-blocked, behind\n  a login, too obscure to crawl, or removed — not that the page never existed.\n  Check two archives before writing \"no record\".\n- **Exclusion looks like absence.** An explicit exclusion notice means somebody\n  acted; a plain 404 means nothing. Different facts — note which you got.\n- **Retroactive removal.** Wayback has historically applied a site's *current*\n  robots.txt to its whole archive history, so a new `Disallow` could pull years\n  of captures at once — making an expired-domain purchase plus a restrictive\n  robots.txt a cheap way to launder a site's past. The practice has narrowed,\n  but go to archive.today and Common Crawl when a history looks too clean.\n- **Composite renders.** Mixed-date resources mean the rendered page is a\n  reconstruction. Cite the HTML capture timestamp, not \"how it looked\".\n- **Capture time is not publication time.** A page first captured in March may\n  have been published in January. The capture bounds the date from above only.\n- **Dynamic and personalised content.** The crawler saw one variant — one\n  geography, one A\u002FB bucket, logged out. Prices and availability especially.\n- **Sparse sampling hides everything.** A page captured twice a year can change\n  and revert with no trace; `collapse=digest` shows observed changes, not all\n  changes. Timestamps are UTC, and forgetting that breaks a timeline by a day.\n\n## Confidence grading\n\n- **Confirmed** — a crawler-initiated capture with `statuscode:200`, retrieved\n  raw with `id_`, on a URL verified as the subject's, corroborated by a second\n  archive or by adjacent captures in the same crawl series.\n- **Probable** — a single well-formed Wayback capture with no second source, or\n  an archive.today capture consistent with the site's other history.\n- **Unconfirmed** — an on-demand capture with no neighbours; a URL carrying\n  query parameters or user-generated content paths; a screenshot; content read\n  from a composite replay rather than the raw response.\n- **Rejected** — a capture whose URL was not under the subject's control at that\n  date, or one taken after a domain transfer and presented as the prior owner's.\n\nCite the full archive URL with timestamp, the original URL, the capture time in\nUTC, and how you retrieved it. An archive citation without a timestamp is not a\ncitation.\n\n## Worked example\n\nA supplier's site claims an industry certification. The client wants it verified\nbefore signing.\n\n`collapse=digest` on the certifications page returns nine content changes over\nsix years. The raw captures either side of the most recent one show the\ncertification body's name changed — from a recognised accreditor to a similarly\nnamed entity — with no announcement.\n\nThe dead end: the accreditor's own register has no live entry either way, and\nits archived member lists replay as empty shells. Fetching them with `id_` shows\nwhy — the list was rendered client-side from an API call, so the crawler\ncaptured a page with no data in it. Nothing recoverable there.\n\nCDX enumeration on `matchType=domain` then turns up a staging host holding an\narchived PDF of the original certificate. Its metadata carries an expiry date\ntwo years before the current site claims coverage, and\n`secrets-in-file-metadata` gets an author name from the same file.\n\nGrade: the wording change **confirmed** — two crawler captures, raw, both read.\nThe lapse **probable** — one document, no confirmation from the accreditor.\n\n## Pivots\n\n| New selector | Goes to |\n|---|---|\n| Former staff names, titles, bios | `find-anyone`, `pattern-of-life-from-socials` |\n| Email addresses from pre-form contact pages | `what-an-email-reveals` |\n| Phone numbers and street addresses | `whose-number-is-this` |\n| Subdomains and hosts from CDX enumeration | `find-hidden-subdomains`, `who-owns-this-domain` |\n| Archived documents and PDFs | `secrets-in-file-metadata` |\n| Archived images | `find-the-original-image`, `geolocate-from-pixels` |\n| Forgotten paths and exposed file names | `google-like-a-spy`, `secrets-in-git-history` |\n| Prior corporate identity of a domain | `x-ray-a-company`, `who-really-owns-it` |\n| A timeline of edits and removals | `write-the-intel-brief`, `graph-the-network` |\n\n## Legal and handling notes\n\nReading an archive is passive; it touches the archive's servers, not the\ntarget's. Fetching a recovered path against the live site is not passive and\nlands in the target's logs — decide deliberately which you are doing.\n\nArchived personal data is still personal data. Content removed under a\nright-to-erasure request may persist in archives, and republishing it can create\nthe liability the removal was meant to extinguish. Weigh the investigative need\nagainst the reason for removal, and minimise per\n[..\u002F..\u002FETHICS.md](..\u002F..\u002FETHICS.md). Reproducing substantial archived content in\na published report is a separate copyright question from using it as evidence.\n\nBulk retrieval strains a nonprofit's infrastructure: rate-limit enumeration and\nraw fetches, and pull the index once rather than repeatedly.\n",{"description":7},"main","58843b159d7a4050d6b785a98b908cce505c0b92","agent\u002Fskills\u002Fread-deleted-pages",0,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent","https:\u002F\u002Fgithub.com\u002FReihantt6","reihsns.web.id","2026-08-19 20:08:18",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Reihantt6\u002Fsns-myagent --skill read-deleted-pages",{"tool":38,"command":39},"bunx","bunx skills add Reihantt6\u002Fsns-myagent --skill read-deleted-pages",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Reihantt6\u002Fsns-myagent --skill read-deleted-pages","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fread-deleted-pages\u002FSKILL.md",true,[46,52],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"reference\u002Farchive-comparison.md","REFERENCE","参考文档",8823,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fread-deleted-pages\u002Freference\u002Farchive-comparison.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"reference\u002Fcdx-cookbook.md",8767,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fread-deleted-pages\u002Freference\u002Fcdx-cookbook.md",[57,64,71,78,85,92],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M77XDCYZ407XYMF2T4P6F7VT","youtube-transcript","Extract transcripts from YouTube videos. Use when the user asks for a transcript, subtitles, or captions of a YouTube video and provides a YouTube URL (youtube.com\u002Fwatch?v=, youtu.be\u002F, or similar). Supports output with or without timestamps.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-transcript\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M77XD7PBC98J6MXGJJ2TJ8DX","youtube-thumbnail-design","YouTube thumbnail design with specific dimensions, contrast rules, and mobile preview optimization. Covers safe zones, text placement, face expression psychology, and A\u002FB testing. Use for: YouTube thumbnails, video cover images, click-through optimization. Triggers: youtube thumbnail, thumbnail design, video thumbnail, click through rate, ctr optimization, youtube cover, video cover image, thumbnail maker, thumbnail tips, youtube design, video preview image","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-thumbnail-design\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M77XD2541C8HXJ6RHYZP4NGJ","youtube-short-maker","Make YouTube Shorts that hold attention with Pexo — vertical 9:16, fast-paced, hook in the first 3 seconds. Describe your topic and Pexo writes the script, generates the shots, picks the models, and assembles a finished Short with music and captions. Use for YouTube Shorts: \"youtube short\", \"make a youtube short\", \"shorts video\", \"short-form video\". NOT for long-form or landscape video.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-short-maker\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M77XCXKVSYK7KTZ3PQBVVGFD","xcode-project-setup","Safely modifies Xcode projects (.pbxproj) to add Swift Packages and link files. Use this skill whenever an iOS project needs dependencies installed (e.g. Firebase, Alamofire).","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fxcode-project-setup\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M77XCR1DV8ZQK2NHWKVY4EWX","x402","Set up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key. Two setups it works out up front — \"just use it\" (set up a wallet so you or Claude Code can run cloud browser tasks paid from the wallet — Claude writes and runs throwaway scripts, nothing touches your codebase) or \"build it in\" (install the SDK and write the key + code into your project). Walks through wallet setup, funding, .env, and a ~$1 test run. Use when the user asks about x402, pay-per-use, USDC payments, or wants Browser Use Cloud without an API key. For the free-tier signup (reverse-CAPTCHA → API key), use `browser-use cloud signup` or the `cloud` skill instead.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fx402\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M77XCMD3R3ZBZQQSW6E0793B","x-twitter-scraper","Build GitHub Copilot workflows with Xquik X API SDKs, REST endpoints, hosted Apify Actor runs, MCP tools, TweetClaw OpenClaw plugin installs, signed webhooks, tweet search, user lookup, follower exports, media actions, and agent automation.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fx-twitter-scraper\u002FSKILL.md",[],[]]