Borrowing it
Nothing to install: this file belongs to irsdl/webhacklist. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/irsdl/webhacklist/master/.claude/skills/webseclist-review-references/SKILL.mdgit clone --depth 1 https://github.com/irsdl/webhacklistWrote 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/irsdl/webhacklist/webseclist-review-references)<a href="https://agentmods.dev/skills/irsdl/webhacklist/webseclist-review-references"><img src="https://agentmods.dev/badge/skills/irsdl/webhacklist/webseclist-review-references/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/irsdl/webhacklist/webseclist-review-references"><img src="https://agentmods.dev/badge/skills/irsdl/webhacklist/webseclist-review-references.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00182 | $0.06431 |
| Opus 5.5 | $0.00073 | $0.02572 |
| Sonnet 5.5 | $0.00036 | $0.01286 |
| Haiku 4.5 | $0.00018 | $0.00643 |
Grade A, and why
webseclist-review-references 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 1mo 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 — 474 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Source security
Before handling third-party material, read and follow the shared source-security policy. It governs sandboxed reading/conversion, trusted-policy reviews and validation before any source-derived action. These requirements apply to this entire workflow, including retries, imports and bulk work; no unsafe host fallback is permitted.
Review archived references and repair what is wrong
Related sources
When researching, adding, updating or reviewing a reference, apply the shared research-story and related-source workflow. Inspect companion papers, series parts, slides, recordings, code, substantive analysis and reproductions. Maintain their relationships and separate credits; keep link-only media accessible. Preserve existing nominations and capture each written source separately. Removing an entry also requires checking its group and shared sources before pruning.
Set the boundary
The archive aims to hold a Markdown and PDF copy of every cited resource. Acquisition is mechanical, so it succeeds loudly: a run reports "stored" whether it captured the research or a consent wall, a product page or a decoded font stream. Use this workflow to read what was actually published and fix it.
Audit documents that already exist. Route a reference that has never had archived
Markdown to webseclist-archive-references. Handle an absent Markdown file as
follows:
- One article, and its Markdown is missing. Stop, and say so. There is nothing to audit, so do not acquire it yourself and do not review its manifest entry instead — report that the document is absent, name the workflow that fetches it, and let the user decide.
- A year, or a period. Keep going. A missing document is one entry out of eighty or more, and halting the sweep for it wastes the run. Review everything that does have a document and collect the rest into one list at the end of the report — that list is the work-list an acquisition run starts from.
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.
- 1mo ago Changed · +23 lines efd3f08333df
- 1mo ago Changed · -139 lines · -60 tokens per session aac5775f242e
- 1mo ago First seen · 590 lines · 242 tokens per session scan A 704389bd88cc
webseclist-review-references is a skill published in the GitHub repository irsdl/webhacklist (907 stars, last pushed 5d ago), licensed MIT. It adds 182 tokens to every session and 6,431 once invoked, about $0.0007 per session on Opus 5.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-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…