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.
git clone --depth 1 https://github.com/athola/skrillsWrote 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/commands/athola/skrills/sync-from-claude)<a href="https://agentmods.dev/commands/athola/skrills/sync-from-claude"><img src="https://agentmods.dev/badge/commands/athola/skrills/sync-from-claude/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/commands/athola/skrills/sync-from-claude"><img src="https://agentmods.dev/badge/commands/athola/skrills/sync-from-claude.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.00020 | $0.00345 |
| Opus 5 | $0.00010 | $0.00172 |
| Sonnet 5 | $0.00004 | $0.00069 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
sync-from-claude 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 9d 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
Sync from Claude
Sync from Claude Code using the skrills MCP server.
Use the mcp__plugin_skrills_skrills__sync-from-claude tool with:
to: Target agent (codex,cursor, orcopilot). Default:codexinclude_marketplace: Include marketplace skills (default: false)dry_run: Preview changes without writing
Parse $ARGUMENTS for:
--to <agent>or-t <agent>: Target agent (default: codex)--include-marketplace: Include marketplace skills--dry-runor-n: Preview mode
This reads from ~/.claude/:
- Skills from SKILL.md files
And syncs to the target directory:
- Codex:
~/.codex/skills/(Codex discovery root) - Cursor:
.cursor/directory (agents, rules, skills) - Copilot:
~/.config/github-copilot/instructions/
Report:
- Number of skills copied
- Number of skills skipped
- Names of synced skills
Handle errors:
- If Claude directory doesn't exist: Report and exit cleanly
- If target directory doesn't exist: Offer to create it
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.
- 9d ago First seen · 37 lines · 20 tokens per session scan A 26f673300d8a
sync-from-claude is a command published in the GitHub repository athola/skrills (69 stars, last pushed 4d ago), licensed MIT. It adds 20 tokens to every session and 345 once invoked, about $0.0001 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 commands, from other repositories
send
Send a message to a running agent session. Use this to correct or direct a live agent mid-stream without killing and respawning it.
ship-an-mcp-server
Workflow recipe — make your product agent-usable by chaining 4 skills, spec to pricing.
rescue-an-account
Workflow recipe — diagnose an at-risk customer and build the full save play through to renewal by chaining 4 skills.
prompt-optimizer
Analyze and rewrite a prompt to maximize clarity, specificity, and output quality.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.