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 blockletgit 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)<a href="https://agentmods.dev/skills/arcblock/agent-skills/blocklet"><img src="https://agentmods.dev/badge/skills/arcblock/agent-skills/blocklet/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/arcblock/agent-skills/blocklet"><img src="https://agentmods.dev/badge/skills/arcblock/agent-skills/blocklet.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.00027 | $0.00775 |
| Opus 5.5 | $0.00011 | $0.00310 |
| Sonnet 5.5 | $0.00005 | $0.00155 |
| Haiku 4.5 | $0.00003 | $0.00077 |
Grade A, and why
blocklet 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ARC skill: blocklet
Blocklets are installable AFS apps (manifest + optional AUP pages/agents). This booklet is L0 — verify flags with arc blocklet <cmd> --help.
Discover (always start here)
arc --help
arc blocklet --help
arc blocklet recipe list
arc blocklet recipe explain <name> # e.g. basic | blog | agent | minimal-app
arc blocklet list [dir] # local packages under dir (or cwd)
arc blocklet inspect <path|ref>
arc blocklet check <dir> # validate against recipe/profile
After a daemon is up (arc skill show daemon) — add --instance <name> to
every arc afs call below unless you're on the default instance
(arc skill show afs covers this):
arc afs ls /blocklets --instance <name> # live catalog when mounted
arc afs ls /registry/blocklets --instance <name> # registry entries if present
arc afs explain /blocklets --instance <name>
# WM: open a running blocklet in a surface
# exec $WM/.actions/open-blocklet --args '{"blocklet":"<name>"}' --instance <name>
# Prefer: explain that action first
Scaffold (T5 minimal)
Use an empty isolated directory — never scaffold into the monorepo root.
mkdir -p /tmp/my-blocklet && cd /tmp/my-blocklet
arc blocklet create . --name my-blocklet --recipe basic
# basic → blocklet.yaml only (smallest green path)
# --name becomes the DID identifier: alphanumeric / hyphen / underscore only.
# Omitting it derives one from the directory basename, and `create` REFUSES
# (exit 5) rather than write a DID `blocklet build` would reject (arc#6281).
arc blocklet check .
arc blocklet build .
# → dist/ with .afs/manifest.json + blocklet.dist.json
Richer recipes (need more files; still offline-capable):
| Recipe | What you get |
|---|---|
basic / blank |
manifest only |
blog |
AUP blog pages |
agent |
AI chat + agent |
minimal-app |
web + aup + agent + settings |
agent-workspace |
workspace-shaped app |
support-community |
support-community shell |
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 First seen · 91 lines · 27 tokens per session scan A 8daaed2fd5a4
blocklet is a skill published in the GitHub repository ArcBlock/agent-skills (5 stars, last pushed 9d ago), licensed MIT. It adds 27 tokens to every session and 775 once invoked, about $0.0001 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-09-14.
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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.