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-all)<a href="https://agentmods.dev/commands/athola/skrills/sync-all"><img src="https://agentmods.dev/badge/commands/athola/skrills/sync-all/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-all"><img src="https://agentmods.dev/badge/commands/athola/skrills/sync-all.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.00025 | $0.00368 |
| Opus 5.5 | $0.00010 | $0.00147 |
| Sonnet 5.5 | $0.00005 | $0.00074 |
| Haiku 4.5 | $0.00003 | $0.00037 |
Grade A, and why
sync-all 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 1mo 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 All
Sync all configurations between AI coding assistants using the skrills MCP server.
Use the mcp__plugin_skrills_skrills__sync-all tool with these parameters:
from: Source agent (claude, codex, copilot, or cursor). Default: claudeto: Target agent. Default: codex (for claude source) or claude (for others)dry_run: Set to true to preview changes without writingforce: Set to true to skip confirmation prompts
Parse $ARGUMENTS for:
--from <agent>or-f <agent>: Source agent--to <agent>or-t <agent>: Target agent--dry-runor-n: Preview mode--force: Skip confirmations
If no arguments provided, sync from Claude to Codex with a preview first.
Report sync results including:
- Number of skills synced
- Number of commands synced
- Number of MCP servers synced
- Any conflicts or errors encountered
Handle errors:
- If MCP server unavailable: Report connection error with troubleshooting steps
- If source/target invalid: List valid options (claude, codex, copilot, cursor)
- If conflicts detected: Show conflicts and prompt for resolution strategy
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.
- 1mo ago First seen · 35 lines · 25 tokens per session scan A 7620b78a5a65
sync-all is a command published in the GitHub repository athola/skrills (69 stars, last pushed 3d ago), licensed MIT. It adds 25 tokens to every session and 368 once invoked, about $0.0001 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-08-30.
Other commands, from other repositories
project
Manage projects: register repos, inspect, configure per-project settings, and remove.
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.
promote
The promote loop — scan your transcripts for what you keep asking, pick a pattern, draft the skill, test its triggers, publish the release package.
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.