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 aboul3ata/lazyweb-skill --skill lazyweb-growth-scoregit clone --depth 1 https://github.com/aboul3ata/lazyweb-skillWrote 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/aboul3ata/lazyweb-skill/lazyweb-growth-score)<a href="https://agentmods.dev/skills/aboul3ata/lazyweb-skill/lazyweb-growth-score"><img src="https://agentmods.dev/badge/skills/aboul3ata/lazyweb-skill/lazyweb-growth-score/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/aboul3ata/lazyweb-skill/lazyweb-growth-score"><img src="https://agentmods.dev/badge/skills/aboul3ata/lazyweb-skill/lazyweb-growth-score.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.00023 | $0.00244 |
| Opus 5 | $0.00012 | $0.00122 |
| Sonnet 5 | $0.00005 | $0.00049 |
| Haiku 4.5 | $0.00002 | $0.00024 |
Grade C, and why
lazyweb-growth-score scanned grade C with 2 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
`curl -fsSL https://www.lazyweb.com/install.sh | bash`, then call Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`curl -fsSL https://www.lazyweb.com/install.sh | bash`, then call What it actually says
Lazyweb Growth Score
If Lazyweb MCP is unavailable, run
curl -fsSL https://www.lazyweb.com/install.sh | bash, then call
lazyweb_health.
Call lazyweb_growth_score; inspect its live schema first. Choose get for a
read, generate only when the user explicitly asks to create a score, and
changes for historical comparison. Pass up to ten websites in one batch.
Never turn a read, page open, or version mismatch into a regrade.
Pass skill: "lazyweb-growth-score" plus the installed VERSION/integrity tags.
Do not reproduce scoring rules in the skill.
On success, open open_url only when provided and only through the host browser;
never expose it. Return the stable url to the user and include share_url when
present.
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 · 27 lines · 23 tokens per session scan C 59a6b427a46f
lazyweb-growth-score is a skill published in the GitHub repository aboul3ata/lazyweb-skill (450 stars, last pushed yesterday), licensed MIT. It adds 23 tokens to every session and 244 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…