Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add idan-yaron/claude-cowork-skills-toolkit/plugin install skills-toolkitWrote 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/idan-yaron/claude-cowork-skills-toolkit/skills-share)<a href="https://agentmods.dev/skills/idan-yaron/claude-cowork-skills-toolkit/skills-share"><img src="https://agentmods.dev/badge/skills/idan-yaron/claude-cowork-skills-toolkit/skills-share/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/idan-yaron/claude-cowork-skills-toolkit/skills-share"><img src="https://agentmods.dev/badge/skills/idan-yaron/claude-cowork-skills-toolkit/skills-share.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.00090 | $0.02344 |
| Opus 5 | $0.00045 | $0.01172 |
| Sonnet 5 | $0.00018 | $0.00469 |
| Haiku 4.5 | $0.00009 | $0.00234 |
Grade B, and why
skills-share scanned grade B 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 12d 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.
Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
- **Bash** runs in the VM — use it to enumerate installed skills AND build How it starts
The opening of the file, as written. The whole thing — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Share Installed Skills
Export one or more already-installed skills as a downloadable .zip file.
The user downloads it via the Cowork preview and saves it wherever they want —
Desktop, Documents, a project folder, Slack, email attachment.
This skill does NOT install the exported plugin back into Cowork. The
skills are already installed. The .zip format deliberately avoids the
"Save plugin"/"Save skill" install prompts that .plugin/.skill extensions
trigger — the user gets a standard file download instead.
This skill is for exporting what you already have. To get new skills from
a GitHub repo, use /skills-load.
VM constraints (why we use the session outputs folder and .zip)
The Cowork VM has a fixed set of mount points. None of them is the user's
Desktop or an arbitrary host path — the Write tool cannot reach
~/Desktop/anything unless the user has explicitly mounted that folder.
What DOES work: /sessions/<session>/mnt/outputs/ is a VM→host bridge mount.
Files written there are surfaced in the Cowork UI by mcp__cowork__present_files.
A .zip file presented this way gives the user a download button — they save
it wherever they want via their OS file picker.
- Bash runs in the VM — use it to enumerate installed skills AND build the ZIP entirely inside the VM.
- Read tool can read from VM-mounted skill directories (not used in the new flow — Bash+Python reads files directly).
- Write tool bridges to the host but only where mounts exist — NOT used in this skill.
mcp__cowork__present_filessurfaces the built ZIP for download.
When to use this vs /skills-load
| Situation | Use |
|---|---|
| "I found a repo with skills I want" | /skills-load <url> |
| "I want to send skills from my session to a colleague" | /skills-share |
| "I want to archive the skills I use" | /skills-share |
| "I want to hand off skills whose GitHub source is gone" | /skills-share |
Step 1: Enumerate installed skills
What ships with it
1 file 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.
- 12d ago First seen · 242 lines · 90 tokens per session scan B 7f0238ed2fe8
skills-share is a skill published in the GitHub repository idan-yaron/claude-cowork-skills-toolkit (5 stars, last pushed 5mo ago), licensed MIT. It adds 90 tokens to every session and 2,344 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it B with 1 finding (enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
session-status
Analyzes current session state without any cleanup. Full mode (default): resolves the active plan file, reads plan checklist + TaskList, gathers unfinished work/issues from conversation history, and emits a /handoff-built next-session prompt. Mid-session mode (/session-status mid): a fast plain-language 'done vs…
wrap-up
End-of-session handler that first checks whether the current session's plan is actually complete. If complete: run a quick retrospective, emit a forward-looking follow-up prompt, and — in a git repository — refresh the repo and clean gone branches. If incomplete: skip cleanup and emit ready-to-paste resume prompts so…
gh-cli-patterns
Canonical reference for all gh CLI command shapes used by skills in this plugin. Defines the placeholder convention, default-branch (trunk vs git-flow) detection, allowed --json fields, GraphQL fallback rules, -f/-F/--raw-field flag semantics, the PR-readiness gate, code-scanning alert query, review-thread…
finalize-pr
Automatically finalize pull requests for merge by resolving CodeQL violations, review threads, merge conflicts, and CI failures. Handles single PR (current branch or by number), all open PRs in the repo, or all open PRs across the org. Includes bot-authored PRs in all modes.
ship
Commit, push, create PR(s), and auto-finalize — full automation pipeline. Handles uncommitted changes and recently created PRs.
dell-idrac-bmc-ops
Bring a Dell PowerEdge BMC (iDRAC) onto the network headlessly, standardize its baseline settings, stage its firmware, and drive an unattended Proxmox/Linux install through it — including generation-specific Redfish/racadm gotchas, the identity-before-power-action rule, and the phantom-drive failure mode caused by…