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 ArcBlock/agent-skills --skill blocklet-url-analyzergit clone --depth 1 https://github.com/ArcBlock/agent-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/arcblock/agent-skills/blocklet-url-analyzer)<a href="https://agentmods.dev/skills/arcblock/agent-skills/blocklet-url-analyzer"><img src="https://agentmods.dev/badge/skills/arcblock/agent-skills/blocklet-url-analyzer.svg" alt="Measured on agentmods" 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.00039 | $0.03778 |
| Opus 5 | $0.00019 | $0.01889 |
| Sonnet 5 | $0.00008 | $0.00756 |
| Haiku 4.5 | $0.00004 | $0.00378 |
Grade A, and why
blocklet-url-analyzer scanned grade A with 1 finding 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 6d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
> **ALWAYS use terminal commands (curl, wget, etc.) to make HTTP requests directly.** How it starts
The opening of the file, as written. The whole thing — 421 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Blocklet URL Analyzer
Analyze URLs in the Blocklet Server ecosystem, identify request types, and locate corresponding development repositories.
Core Philosophy
"Bridge from URL to code."
When issues occur in production, developers only have a URL in hand. This skill serves as the bridge: analyzing URL type (Daemon/Service/Blocklet), locating the specific repository and code path, making the "URL → code" path clear and traceable.
Use Cases
- User provides a Blocklet Server related URL and wants to know which repository to develop in
- During debugging, need to know which component a URL corresponds to
- Reverse lookup development repository from production environment URL
Critical Rule
⚠️ NEVER use Chrome browser or any interactive browser tools to analyze URLs.
ALWAYS use terminal commands (curl, wget, etc.) to make HTTP requests directly.
This is a strict requirement - all URL analysis must be done via command line, not browser automation.
Repository Reference Files
This skill includes local reference files for repository lookup:
references/org-arcblock-repos.md- ArcBlock organization repos (core infrastructure, SDKs, mobile apps)references/org-blocklet-repos.md- Blocklet organization repos (blocklet applications, kits, tools)references/org-aigne-repos.md- AIGNE organization repos (AI agent framework, LLM adapters)
Active Loading Policy (ALP)
Load reference files on-demand based on context. Do not preload all files.
| Trigger Condition | Load File |
|---|---|
| Need ArcBlock core repos (blocklet-server, ux, did-connect, SDKs) | references/org-arcblock-repos.md |
| Need Blocklet app repos (payment-kit, media-kit, discuss-kit, etc.) | references/org-blocklet-repos.md |
| Need AIGNE AI repos (aigne-framework, aigne-hub, LLM adapters) | references/org-aigne-repos.md |
| Uncertain which organization | First read references/README.md for high-density summary |
Loading Strategy:
- First determine which organization the repository likely belongs to based on blocklet name/context
- Load only the relevant reference file
- If uncertain, read
references/README.mdfirst to decide which file to load - Prefer local reference files over
ghcommands for repository lookup
What ships with it
4 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.
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.
- 6d ago First seen · 421 lines · 39 tokens per session scan A 848a3141d82d
blocklet-url-analyzer is a skill published in the GitHub repository ArcBlock/agent-skills (5 stars, last pushed 5d ago), licensed MIT. It adds 39 tokens to every session and 3,778 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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…
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…