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-share-plugingit 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-share-plugin)<a href="https://agentmods.dev/skills/acryldev/acryl/acryl-share-plugin"><img src="https://agentmods.dev/badge/skills/acryldev/acryl/acryl-share-plugin/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-share-plugin"><img src="https://agentmods.dev/badge/skills/acryldev/acryl/acryl-share-plugin.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.00040 | $0.00500 |
| Opus 5.5 | $0.00016 | $0.00200 |
| Sonnet 5.5 | $0.00008 | $0.00100 |
| Haiku 4.5 | $0.00004 | $0.00050 |
Grade A, and why
acryl-share-plugin 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 today.
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
Save, share and pull plugins
A plugin travels as one tarball with a sha512. Where it can go: the plugin store on this machine, the user's own GitHub repository (one per plugin, private unless they list it publicly), an npm registry (the public one, or a private one the user names; a private plugin needs a scope, @owner/name). Catalogs (acryl.dev, cordisplugins.github.io, dshfind) list a public repository by its labels; nobody submits anything.
- Make sure it works first: installed with acryl_install_plugin and verified with acryl_verify_plugin.
- For anything public it needs a "license" in package.json. A fix needs a new version first (acryl_plugins action version, bump patch).
- Your tool is acryl_plugins. Its actions saved, save and version run directly (they stay on this machine); share, and pull from anywhere but store:, ask the user in the app first, because they send the user's work or install code that runs with their permissions; if the user does not allow it, do not retry: tell them the command they can type instead. Never ask for or handle a token (git and gh use the user's own login). Share writes the service contract, the labels and the repository into package.json, runs the secret check over exactly the files it sends, and refuses a version that is already released. To publish to npm instead of GitHub, share with to "npm" (or "npm:"); it uses the user's own npm login.
- The user's own commands, the same operations: in the chat
/plugin save | share <name> [public] [owner/repo] | share <name> npm [public] [registry URL] | pull <source> | version patch <name> | list | saved; on the command lineacryl plugin save | share [--npm] | pull | saved | version. A source isgithub:<owner>/<repo>[@version],npm:<name>,store:<name>, a .tgz file or https URL.
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.
- today First seen · 24 lines · 40 tokens per session scan A d614b8ce8422
acryl-share-plugin is a skill published in the GitHub repository acryldev/acryl (257 stars, last pushed today), licensed MIT. It adds 40 tokens to every session and 500 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-10-17.
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.