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 agentmods add skills/damimartinez/scrapeagent/skill-creatornpx skills add DamiMartinez/scrapeagent --skill skill-creatorgit clone --depth 1 https://github.com/DamiMartinez/scrapeagentWrote 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/damimartinez/scrapeagent/skill-creator)<a href="https://agentmods.dev/skills/damimartinez/scrapeagent/skill-creator"><img src="https://agentmods.dev/badge/skills/damimartinez/scrapeagent/skill-creator.svg" alt="Measured on agentmods" 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 | $0.00043 | $0.00437 |
| Opus 5 | $0.00022 | $0.00218 |
| Sonnet 5 | $0.00009 | $0.00087 |
| Haiku 4.5 | $0.00004 | $0.00044 |
Grade A, and why
skill-creator 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 3d 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.
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.
What it actually says
Skill Creator
Purpose
Help users create well-structured skills documenting how to scrape specific websites.
New skills are saved to the skills/ directory and become immediately usable after an agent restart.
Workflow
Step 1 — Gather requirements
Ask the user:
- What website do they want to scrape? (get the exact URL)
- What specific data fields do they need?
- Any special requirements? (login, pagination, JS rendering, rate limits)
Step 2 — Investigate the website (if needed)
- Use fetch to retrieve the page HTML
- If the page appears empty, switch to playwright
- Identify exact CSS selectors for each required data field
- Note whether JS is required (use playwright vs fetch)
Step 3 — Generate the skill name
- Kebab-case, all lowercase, e.g.:
amazon-products,reddit-posts,linkedin-jobs - Must clearly represent the website and data type
Step 4 — Write the instructions
Follow the template at assets/SKILL_TEMPLATE.md. Key sections to include:
- Overview with the target URL(s)
- URL construction (if parameterized)
- Step-by-step extraction with exact CSS selectors
- Column/field names for the output
- Notes on edge cases, rate limits, JS requirements
Step 5 — Create the skill
Call the create_skill tool with:
- skill_name: the kebab-case name
- description: 1-2 sentences covering what it scrapes and when to trigger it
- instructions: the full markdown body from Step 4
Step 6 — Confirm
Tell the user the skill was created and that they need to restart the agent (Ctrl+C then adk web) to load it.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 50 lines · 43 tokens per session scan A 3b8ff137d362
skill-creator is a skill published in the GitHub repository DamiMartinez/scrapeagent (10 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 43 tokens to every session and 437 once invoked, about $0.0002 per session on Opus 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…