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 skills add adamjali/claude-skills --skill site-prospectorgit clone --depth 1 https://github.com/adamjali/claude-skillsWrote 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/adamjali/claude-skills/site-prospector)<a href="https://agentmods.dev/skills/adamjali/claude-skills/site-prospector"><img src="https://agentmods.dev/badge/skills/adamjali/claude-skills/site-prospector/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/adamjali/claude-skills/site-prospector"><img src="https://agentmods.dev/badge/skills/adamjali/claude-skills/site-prospector.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00129 | $0.02501 |
| Opus 5 | $0.00064 | $0.01251 |
| Sonnet 5 | $0.00026 | $0.00500 |
| Haiku 4.5 | $0.00013 | $0.00250 |
Grade A, and why
site-prospector 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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Site Prospector
<execution_context> Autonomous by default — a hands-off finder→builder. Required stops: (1) the user picks which candidates to pursue (Phase 2), and (2) anything that sends or publishes externally.
- 🟢 Auto: search, evaluate, fact-verify, write the brief, invoke site-forge (in
auto), deploy the demo, draft outreach, update the ledger. - 🟡 Ask: which candidates to build (always); every deploy, immediately before it (default is local preview; deploy only for a paying client or a scheduled demo); repointing form leads; custom domains.
- 🔴 Never: send/publish outreach without explicit go (drafts only); publish a
flagged-unverified claim without the demo disclaimer; pay for anything.
Quality note: each demo is built as well as is autonomously reachable, then a
per-site "upgrade to full" flag is surfaced so a winner can be re-run with
site-forge fullfor Gemini/Veo media. </execution_context>
What ships with it
15 files 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.
- .claude-plugin/plugin.json 485 B
- ledger/active/.gitkeep 0 B
- ledger/archive.md 85 B
- ledger/index.md 281 B
- ledger/lessons.md 104 KB
- references/candidate-search.md 5.0 KB
- references/commercial-b2b.md 6.5 KB
- references/docs-ledger.md 2.1 KB
- references/fact-verification.md 3.0 KB
- references/monetization.md 10 KB
- references/operation-context.example.md 1.2 KB
- references/outreach.md 3.5 KB
- references/paid-ads-and-attribution.md 8.2 KB
- references/scouting-doctrine.md 43 KB
- scripts/outreach-page.sh 5.7 KB runs code
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.
- 12d ago First seen · 150 lines · 129 tokens per session scan A fb471d5fde7e
site-prospector is a skill published in the GitHub repository adamjali/claude-skills (1 stars, last pushed 1mo ago), licensed MIT. It adds 129 tokens to every session and 2,501 once invoked, about $0.0006 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
colors
Color systems for web interfaces — OKLCH conversion and palette generation, contrast measurement (APCA/WCAG), gamut and P3 fallbacks, theming, one meaning per color. INVOKE PROACTIVELY when converting color values, building or extending a palette or token set, checking or reporting contrast, or theming light and dark…
branch-recap
Takes stock of what a branch actually changed, before it gets pushed — works out the scope itself, then lays the change out group by group in one pass: files touched, what was done and why, how, and what deserves a second look, quoting code only where a remark needs it rather than reprinting the diffs. Closes on a…
audit-context
Measures where a project's Claude context is going before applying any of clean-context's levers. Reports what Glob discovers with and without ignore files applied, the twenty largest files in the repo and which are generated, the cumulative size of every CLAUDE.md loaded for this working directory, and how many MCP…
accessibility
Accessibility engineering for product interfaces — keyboard support, focus states, ARIA, forms, screen readers, hit areas, motion and zoom. INVOKE PROACTIVELY when building or reviewing any UI component, modal, menu, form, or custom widget, and on any keyboard or screen-reader complaint — even when nobody says "a11y".…
ui-polish
Design-engineering details that make an interface feel polished — border radius, optical alignment, shadows and elevation, animations and micro-interactions, press feedback, icons. INVOKE PROACTIVELY when building or reviewing UI components, adding motion or hover/active states, or when the user says "make it feel…
layout
Layout structure for web interfaces — grouping, alignment, negative space, reading order, progressive disclosure, breakpoints, direction-aware (RTL) structure. INVOKE PROACTIVELY when structuring a page or component, spacing or aligning controls, deciding what collapses at small sizes, or reviewing frontend structure.…