WebReaper: Skill for Claude Code

.agents/skills/write-a-skill/SKILL.md

write-a-skill is a skill for Claude Code, Codex from alex-on-ai/WebReaper. It costs 35 tokens per session (664 once invoked), scanned A, a copy of write-a-skill, MIT.

A guide for creating new agent skills with the expected folder structure, concise instructions, staged detail, and optional reference files or utility scripts.

In plain words
What is it for?
It is for gathering skill requirements, drafting SKILL.md, adding supporting resources, and reviewing the draft with the user.
Why use it?
It helps authors produce skills that are clear, reusable, and organized consistently.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is alex-on-ai/WebReaper's own configuration. It tells Claude Code and Codex how to work on WebReaper itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything WebReaper configures →

Reuse

Borrowing it

Nothing to install: this file belongs to alex-on-ai/WebReaper. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/alex-on-ai/WebReaper/master/.agents/skills/write-a-skill/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/alex-on-ai/WebReaper

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for write-a-skill

README.md
[![agentmods](https://agentmods.dev/badge/skills/alex-on-ai/webreaper/write-a-skill.svg)](https://agentmods.dev/skills/alex-on-ai/webreaper/write-a-skill)
Your own site
<a href="https://agentmods.dev/skills/alex-on-ai/webreaper/write-a-skill"><img src="https://agentmods.dev/badge/skills/alex-on-ai/webreaper/write-a-skill.svg" alt="Measured on agentmods" height="20"></a>
Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 664 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00035 $0.00664
Opus 5 $0.00017 $0.00332
Sonnet 5 $0.00007 $0.00133
Haiku 4.5 $0.00003 $0.00066

Measured 8d ago against content hash be8f20e66309, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

write-a-skill 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 8d 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.

Origin

This is a copy

100% identical to write-a-skill — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agents/skills/write-a-skill/SKILL.md · 118 lines

How it starts

The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Writing Skills

Process

  1. Gather requirements - ask user about:

    • What task/domain does the skill cover?
    • What specific use cases should it handle?
    • Does it need executable scripts or just instructions?
    • Any reference materials to include?
  2. Draft the skill - create:

    • SKILL.md with concise instructions
    • Additional reference files if content exceeds 500 lines
    • Utility scripts if deterministic operations needed
  3. Review with user - present draft and ask:

    • Does this cover your use cases?
    • Anything missing or unclear?
    • Should any section be more/less detailed?

Skill Structure

skill-name/
├── SKILL.md           # Main instructions (required)
├── REFERENCE.md       # Detailed docs (if needed)
├── EXAMPLES.md        # Usage examples (if needed)
└── scripts/           # Utility scripts (if needed)
    └── helper.js

SKILL.md Template

---
name: skill-name
description: Brief description of capability. Use when [specific triggers].
---

# Skill Name

## Quick start

[Minimal working example]

## Workflows

[Step-by-step processes with checklists for complex tasks]

## Advanced features

[Link to separate files: See [REFERENCE.md](REFERENCE.md)]

Description Requirements

The description is the only thing your agent sees when deciding which skill to load. It's surfaced in the system prompt alongside all other installed skills. Your agent reads these descriptions and picks the relevant skill based on the user's request.

Goal: Give your agent just enough info to know:

  1. What capability this skill provides
  2. When/why to trigger it (specific keywords, contexts, file types)

Format:

  • Max 1024 chars
  • Write in third person
  • First sentence: what it does
  • Second sentence: "Use when [specific triggers]"

Good example:

Extract text and tables from PDF files, fill forms, merge documents. Use when working with PDF files or when user mentions PDFs, forms, or document extraction.

Read the full file on GitHub · 118 lines

Changes

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.

  1. 8d ago First seen · 118 lines · 35 tokens per session scan A be8f20e66309

Subscribe to this mod's changes

write-a-skill is a skill published in the GitHub repository alex-on-ai/WebReaper (146 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 664 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to write-a-skill, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

firecrawl-build

Integrate Firecrawl into application code whenever a product, agent, or workflow needs web data inside the app — web search, live search results, page scraping, structured extraction, or browser interaction. Use when building any feature that needs data from the web in code, even if the user does not mention Firecrawl…

firecrawl/firecrawl · 149 tokens

firecrawl-build-onboarding

Get Firecrawl credentials and SDK setup into a project. Use when an application needs FIRECRAWLAPIKEY, when an agent should add Firecrawl to .env, when the user wants to authenticate Firecrawl for app code, or when choosing the first SDK and docs for a new Firecrawl integration. This skill includes its own browser…

firecrawl/firecrawl · 89 tokens

firecrawl-build-scrape

Integrate Firecrawl /scrape into product code for single-page extraction. Use when an app already has a URL and needs markdown, HTML, links, screenshots, metadata, or structured page output. Prefer this skill over broader crawl patterns when the feature is page-level.

firecrawl/firecrawl · 62 tokens

firecrawl-build-search

Integrate Firecrawl /search into product code and agent workflows. Use when an app needs discovery before extraction, when the feature starts with a query instead of a URL, or when the system should search the web and optionally hydrate result content.

firecrawl/firecrawl · 54 tokens

firecrawl-build-interact

Integrate Firecrawl /interact into product code for dynamic pages and browser actions after scraping. Use when a feature needs clicks, form fills, pagination, authentication-aware flows, or other multi-step interactions that plain /scrape cannot complete.

firecrawl/firecrawl · 56 tokens

crawl4ai-skill

A web crawler and scraper that searches with DuckDuckGo, fetches individual pages or whole sites, and returns clean Markdown intended for language models. It can also scrape pages that need JavaScript to display their content.

lancelin111/crawl4ai-skill · 63 tokens