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-updategit 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-update)<a href="https://agentmods.dev/skills/aboul3ata/lazyweb-skill/lazyweb-update"><img src="https://agentmods.dev/badge/skills/aboul3ata/lazyweb-skill/lazyweb-update/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-update"><img src="https://agentmods.dev/badge/skills/aboul3ata/lazyweb-skill/lazyweb-update.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 5 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 76 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- high Tool Misuse · line 101 Tool calls are chained to bypass individual safety checks or escalate capabilities beyond what any single tool call would allow.Fix: Limit tool chaining depth and validate the output of each tool before passing it to the next. Require explicit user approval for multi-step chains.
- medium Data Exfiltration · line 44 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Agent Snooping · line 131 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- low Supply Chain · line 44 Remote code is downloaded and executed. This bypasses code review and could introduce malicious code.Fix: Avoid downloading and executing remote scripts. Use trusted packages from PyPI/npm. If remote fetch is required, verify checksums and use HTTPS.
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.00086 | $0.02139 |
| Opus 5 | $0.00043 | $0.01069 |
| Sonnet 5 | $0.00017 | $0.00428 |
| Haiku 4.5 | $0.00009 | $0.00214 |
Grade A, and why
lazyweb-update 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 9d 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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lazyweb Update
Use this skill for maintenance only: update the installed Lazyweb skill pack, reinstall the local skills, and verify the active clients can see the result. Do not run design research from here.
Check what's published first
Before reinstalling, check the latest version through the Lazyweb MCP. This runs against the user's Lazyweb account (so update usage is recorded) and tells them exactly what they'll get:
- Read the installed version:
cat "$HOME/.lazyweb/VERSION" 2>/dev/null || echo 0.0.0 - Call the
lazyweb_check_updateMCP tool withinstalled_versionset to that value,clientset to the coding client you're running in (e.g.claude-code,cursor,codex),skill: "lazyweb-update", andversionset to the installed version. It returns{ installed, latest, update_available, install_hint }— tell the user the installed vs latest version and whether an update is available. - If the Lazyweb MCP is not available — a fresh or broken install is the
usual reason someone runs this skill — skip the tool and compare directly,
then proceed:
curl -fsSL https://raw.githubusercontent.com/aboul3ata/lazyweb-skill/main/VERSION
update_available tells the user what's new, but it does not gate the
reinstall. The updater below reruns setup with --host all, which also repairs
broken, stale, or newly-added client skill roots — a current VERSION does not
mean those are in sync. So:
- If the user asked to update, reinstall, or sync Lazyweb (the normal case):
run the updater below regardless of
update_available. Even when already current, the reinstall brings every client skill root back in sync. - Only if the user asked purely for a status check (e.g. "is there a Lazyweb update?"): report installed vs latest and stop without reinstalling.
Run the update
~/.lazyweb/bin/lazyweb-update is a trusted local binary the user already
installed — it only refreshes the local checkout and reinstalls local skills. Do
not stack up multiple permission gates around it: a single lightweight "Updating
your local Lazyweb skills now." confirmation is enough (any client tool-approval
prompt already covers the rest).
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.
- 9d ago First seen · 186 lines · 86 tokens per session scan E ae94d00136a6
lazyweb-update is a skill published in the GitHub repository aboul3ata/lazyweb-skill (448 stars, last pushed 6d ago), licensed MIT. It adds 86 tokens to every session and 2,139 once invoked, about $0.0004 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-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…