Octocode Scraping logo

Octocode Scraping

Community
bgauryy
octocode-scraping

Use when extracting or mapping public web content into a local cited corpus: scrape or crawl a URL/docs site, pull tables/pricing/product fields, diagnose blocked or thin pages, or answer from saved pages. Phrases like scrape this URL, crawl the docs, build a corpus, extract pricing. Prefer keyless fetch; ask before hosted spend. Live clicks/HAR/perf → octocode-chrome-devtools.

Overview

Publisherbgauryy
Repositoryoctocode
Skill nameoctocode-scraping
Stars
950
Forks
78
Bundled files
38
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 38 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by bgauryy on GitHub. Read the source before you install it.

Installation

Install the Octocode Scraping AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/bgauryy/octocode/tree/main/skills/octocode-scraping
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/bgauryy/octocode.git /tmp/octocode
mkdir -p .claude/skills
cp -r /tmp/octocode/skills/octocode-scraping .claude/skills/octocode-scraping
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Octocode Scraping in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Octocode Scraping on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Octocode Scraping is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Octocode Scraping

Flow: FRAME → POLICY → ROUTE → FETCH → CORPUS → SEARCH → CITE → RECOVER.

FRAME before the first fetch: fix target URL/domain, goal, depth, and output shape — vague ask → references/user-inputs.md.

Defaults: one public URL, --mode html, omit --provider (keyless cdp→direct), session .octocode/tmp/scrape/{sessionId}, compact stdout. Search corpus before refetch. Live interaction → chrome-devtools on one port, then har-ingest + corpus-run into the same session. Ask before auth, hosted spend, crawl widen, CAPTCHA/MFA, destructive actions. Cite paths + URL metadata — not raw dumps.

Stop when: two same-class failures (report evidence, route tried, sanitized status, next approval); hosted 403 (wrong key or credits gone — status only, no retry); CAPTCHA/MFA, auth wall, or cookie/profile transfer needed; still blocked after one cdp try (ask before --provider scrapingant); personal data, form submits, purchases, sends, deletes, or account changes in scope; the saved corpus already proves the claim (cite it, do not refetch); crawl widen before reports/summary.md is useful. Recovery table: references/failure-recovery.md.

Route (pick one)

NeedDoSkip
Vague scrape--mode html, omit --providermarkdown / auto hosted
See auto pickscripts/provider-check.mjsguessing
Fetch/crawlscripts/fetch.mjsdeprecated scrapingant-fetch
Corpus on diskcorpus-inspect → find helpers → corpus-runblind refetch
Live click/DOM/authchrome-devtools--provider cdp alone for interaction
Page healthchrome measure + measure-queryhosted scrape for scores
CDP → corpusscripts/har-ingest.mjs --from-cdp-dirnew sessionId
Prove fieldscripts/corpus-run.mjs --regex|--scriptreopen browser
Still blockedevidence + ask → --provider scrapingantsilent spend

Scripts (Node, no install; every one takes --help)

WhenRun
fetch / crawl / extract a URL — the owner of every network callscripts/fetch.mjs --url <u> [--mode html] [--crawl --same-domain --max-pages <n>] [--no-raw]
want the fetch plus an immediate corpus brief in one shotscripts/fetch-and-brief.mjs --url <u> (wraps fetch.mjs → corpus-inspect.mjs)
before routing or hosted spend: which provider auto-wins, credits leftscripts/provider-check.mjs [--provider <p>], scripts/provider-usage.mjs — sanitized, never prints the key
read a saved session first, then search itscripts/corpus-inspect.mjs --session-dir <d> [--page <n>], then scripts/corpus-find.mjs --session-dir <d> --query <t>
pull static DOM, assets, or graph paths out of the corpus (live DOM → chrome-devtools)scripts/dom-find.mjs --kind form/button/table, scripts/resource-list.mjs --kind asset/external, scripts/graph-navigate.mjs --from <nodeId> — each with --session-dir <d>
prove one field locally instead of reopening a browserscripts/corpus-run.mjs --session-dir <d> --roots cdp,extracts --regex <re> (or --script <file>, --concat-parts)
bridge chrome-devtools artifacts into this session, or hand a packet backscripts/har-ingest.mjs --session-dir <d> --from-cdp-dir <run>; reverse with --export-packet
need field names before an extractionscripts/schema-helper.mjs --intent "extract pricing and features"
an old transcript uses the legacy namesdeprecated shims scripts/scrapingant-fetch.mjs, scripts/scrapingant-check.mjs, scripts/scrapingant-usage.mjs forward to fetch.mjs / provider-check.mjs / provider-usage.mjs — call the new names
editing or extending a scriptshared modules in scripts/lib/ (providers registry, client fetch, corpus, analyzers, extractors, text, args, bridge); env/key resolution vendored in scripts/octocode-config.mjs; JSON contracts in scripts/schemas/

Full flags, roles, and the library map: read scripts/README.md before adding a flag or a vendor.

References

WhenLoad
frame a vague scopereferences/user-inputs.md
legal/safety/privacy policyreferences/scraping-policy.md
cost / keyless vs hosted routereferences/route-selection.md
provider registry / add a vendorreferences/providers.md
hosted API, after approvalreferences/scrapingant.md
search a saved session corpusreferences/session-corpus.md
site graph / navigation / workflowsreferences/website-analysis.md
stdout and corpus file shapesreferences/data-contract.md
extract quality and citationsreferences/extraction-quality.md
live browser bridge playbookreferences/browser-scraping.md
blocked, thin, or oversized resultsreferences/failure-recovery.md

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Octocode Scraping AI skill do?

Use when extracting or mapping public web content into a local cited corpus: scrape or crawl a URL/docs site, pull tables/pricing/product fields, diagnose blocked or thin pages, or answer from saved pages. Phrases like scrape this URL, crawl the docs, build a corpus, extract pricing. Prefer keyless fetch; ask before hosted spend. Live clicks/HAR/perf → octocode-chrome-devtools.

Why use Octocode Scraping on TypingMind?

Because you install it once and use it with any model. Octocode Scraping is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Octocode Scraping in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/bgauryy/octocode/tree/main/skills/octocode-scraping. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Octocode Scraping?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Octocode Scraping?

As many as you like. As long as a model supports skills, you can use Octocode Scraping with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Octocode Scraping AI skill free?

Yes. It is published on GitHub by bgauryy under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇