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 acryldev/acryl --skill acryl-build-extensiongit clone --depth 1 https://github.com/acryldev/acrylWrote 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/acryldev/acryl/acryl-build-extension)<a href="https://agentmods.dev/skills/acryldev/acryl/acryl-build-extension"><img src="https://agentmods.dev/badge/skills/acryldev/acryl/acryl-build-extension/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/acryldev/acryl/acryl-build-extension"><img src="https://agentmods.dev/badge/skills/acryldev/acryl/acryl-build-extension.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.00050 | $0.00520 |
| Opus 5.5 | $0.00020 | $0.00208 |
| Sonnet 5.5 | $0.00010 | $0.00104 |
| Haiku 4.5 | $0.00005 | $0.00052 |
Grade A, and why
acryl-build-extension 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 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.
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.
What it actually says
Build an ACRYL extension
- Read {{pack}}/docs/start-here/this-runtime.md completely (contracts, delivery).
- Decide WHERE it mounts and on which surfaces: read {{pack}}/docs/maps/mount-points.md (CLI has terminal overlays; Web and Desktop have client slots; tools, commands, prompts and skills work everywhere). Ask or check which surface the user is on if it matters (the router and acryl_workspace_status help). For an unfamiliar kind of plugin see {{pack}}/docs/maps/taxonomy.md.
- Pick the plugin type(s) the feature needs and open the matching doc from {{pack}}/docs/README.md (tool, service, event hook, config, prompt, client UI, host route, tui command). Read it completely and follow its cross-references.
- Open the closest working example in {{pack}}/example-plugins/README.md and read every file of it. Copy it into a NEW directory /.acryl-extensions// (outside the pack) and change it. Never guess a plugin's shape from memory.
- Write the package (package.json, cordis.patch.yml, index.js, and client.js for UI). Declare honestly in package.json:
"acryl": { "apiVersion": 1, "permissions": [...] }(fs.read, fs.write, net, shell, secrets, ui); the human sees the permissions before a new extension is installed. Write it under<workspace>/.acryl-extensions/<name>/(this project) or<ACRYL home>/extensions/<name>/(all projects and surfaces on this home). - Call the acryl_install_plugin tool with the ABSOLUTE path of that directory. Read its result. Fix the named cause and call it again if it fails; it undoes failed installs.
- Tell the user what you built, whether it is live, and (for UI) that it is already visible in their open conversation, with no reload needed. Do not claim it works before the tool result says so. You cannot publish to the marketplace; say what remains if the user wants that.
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 Changed 604701654c2f
- 24d ago Changed ac750ac7b179
- 25d ago First seen · 22 lines · 50 tokens per session scan A 9a5541d2e643
acryl-build-extension is a skill published in the GitHub repository acryldev/acryl (256 stars, last pushed today), licensed MIT. It adds 50 tokens to every session and 520 once invoked, about $0.0002 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-21.
Other skills, from other repositories
modsearch
Plug-in web search, X (Twitter) search, and page fetch for models without native web access. Use whenever the task needs current information, external facts, source links, posts from X, or the content of a specific URL, and the active model/harness has no native search or fetch tool. Runs the modsearch CLI to return…
manage-taskboard
Manage work in the native DeepSeek Harness Taskboard with exact task ids and optimistic versions. Use when an Agent must inspect project work, claim an eligible todo, record progress or blockers, verify an implementation, submit it for human review, or release its own claim; also use when a human asks how to accept…
industry-research-method
A Chinese-language method for researching an industry by mapping its supply chain, tracking policies and news, and writing sourced reports. It separates the chain into upstream inputs, midstream production, and downstream distribution or use.
company-research-method
A documented process for researching a company using supplied files and selected public sources. It produces a company overview with business details, sourced financial figures, and stated risks.
workdsh-expert-manager
A workflow for creating and delivering reusable expert roles or teams from a user's goals and source material. It saves their instructions, documents, resources, and team structure as a draft that can be checked and published.
workdsh-ppt-design
A workflow guide for creating and editing PowerPoint presentations in the WorkDSH editor. It covers slide-by-slide storytelling, visual design, supported content tools, importing existing PPTX files, and exporting presentations.