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 agentmods add skills/jonesphillip/sharehtml/sharehtml-collaborationnpx skills add jonesphillip/sharehtml --skill sharehtml-collaborationgit clone --depth 1 https://github.com/jonesphillip/sharehtmlWrote 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/jonesphillip/sharehtml/sharehtml-collaboration)<a href="https://agentmods.dev/skills/jonesphillip/sharehtml/sharehtml-collaboration"><img src="https://agentmods.dev/badge/skills/jonesphillip/sharehtml/sharehtml-collaboration.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 | $0.00081 | $0.00828 |
| Opus 5 | $0.00041 | $0.00414 |
| Sonnet 5 | $0.00016 | $0.00166 |
| Haiku 4.5 | $0.00008 | $0.00083 |
Grade A, and why
sharehtml-collaboration 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 4d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to use
Use this skill whenever the task involves a document managed with sharehtml, including:
- deploying or updating a local document
- sharing or unsharing a document
- pulling a remote document locally
- comparing local changes against the deployed document
- reviewing unresolved comments and addressing feedback
sharehtml can deploy supported source files directly, including .html, .md, .markdown, .json, and common code files such as .js, .ts, .jsx, .tsx, .py, .rb, .go, .rs, .java, .c, .cpp, .css, and .sh.
Do not wrap code or Markdown in HTML unless the user explicitly asks for that. If the file is binary or not a supported text/source format, do not try to deploy it directly.
Default behavior
- Keep documents private by default.
- Never run
sharehtml share ...unless the user explicitly asks to make a document shareable. - If a deploy would overwrite an existing document, do not blindly confirm it.
- Before overwriting, run
sharehtml diff <file>, summarize the changes in plain language, and ask the user to confirm. - When a command needs a document id and the user only knows the document name, use
sharehtml listto find candidates. If multiple matches are plausible, ask the user to choose.
Workflows
Deploy or update a document
- Verify the file is a supported format.
- Run
sharehtml deploy <file>. - If the CLI indicates the document already exists and would be updated:
- run
sharehtml diff <file> - summarize the proposed changes in human language
- ask the user whether to proceed with the overwrite
- run
- Only make the document shareable if the user explicitly asks.
Review and address feedback
- Resolve the document id or URL.
- If only a name is given, use
sharehtml list.
- If only a name is given, use
- Run
sharehtml comments <id> --json. - Pull the document locally if needed with
sharehtml pull <id>. - Make the requested local changes.
- Run
sharehtml diff <file>. - Summarize the changes in human language and ask for approval before deploying.
- Run
sharehtml deploy <file>once approved.
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.
- 4d ago First seen · 79 lines · 81 tokens per session scan A c81fda87adcf
sharehtml-collaboration is a skill published in the GitHub repository jonesphillip/sharehtml (127 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 81 tokens to every session and 828 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
hono-cloudflare
Hono on Cloudflare Workers - bindings, KV, D1, R2, Durable Objects, and edge deployment patterns.
github-issue-workflow
How to start work on a GitHub issue in the munkel repo — check for an existing draft PR and the issue's assignee first to avoid duplicating work someone already owns, claim the issue by assigning it, then open a draft PR linked with "Closes.
munkel
Send ephemeral end-to-end-encrypted messages that appear in friends' MacBook notches, via the munkel CLI (macOS). Use when the user wants to message, ping, or notify someone in a Munkel channel, broadcast to a channel, or list Munkel channels and members.
stoop-api
Publish a stoop site over HTTP with an API key, from a server-side app, agent, or CI job that has no folder and no terminal. Use when code you are writing needs to publish or revise a web page at runtime — a bot posting a report, a job publishing a dashboard. If you have the files on disk and a terminal, use stoop…
stoop-platform
The stoop platform SDK reference: platform.db, identity, ai, files, channel, and the served house-style theme. Load before writing any platform. call in a stoop site, whichever way the site is published.
stoop
Deploy a static site to stoop from a folder using the stoop CLI. Use when you have the site's files on disk and a terminal: creating, changing, deploying, or debugging a stoop site, or shipping a quick prototype or demo. If you are a server-side app or agent publishing at runtime with no folder and no terminal, use…