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-status)<a href="https://agentmods.dev/commands/athola/skrills/sync-status"><img src="https://agentmods.dev/badge/commands/athola/skrills/sync-status/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-status"><img src="https://agentmods.dev/badge/commands/athola/skrills/sync-status.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.00013 | $0.00280 |
| Opus 5.5 | $0.00005 | $0.00112 |
| Sonnet 5.5 | $0.00003 | $0.00056 |
| Haiku 4.5 | $0.00001 | $0.00028 |
Grade A, and why
sync-status 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 Status
Show sync status and preview changes using the skrills MCP server.
Use the mcp__plugin_skrills_skrills__sync-status tool with:
from: Source agent (claude, codex, copilot, or cursor)to: Target agentdry_run: Always true for status checks
Parse $ARGUMENTS for:
--from <agent>or-f <agent>: Source agent (default: claude)--to <agent>or-t <agent>: Target agent (default: codex)
Report:
- Skills that would be synced (new, updated, unchanged)
- Commands that would be synced
- MCP server configs that would be synced
- Any potential conflicts
Handle errors:
- If MCP server unavailable: Report connection error
- If source/target invalid: List valid options (claude, codex, copilot, cursor)
- If no skills found in source: Report empty state
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 · 30 lines · 13 tokens per session scan A 1e75ee147eb0
sync-status is a command published in the GitHub repository athola/skrills (69 stars, last pushed 3d ago), licensed MIT. It adds 13 tokens to every session and 280 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.
spawn
Spawn a worker or orchestrator agent session in a registered project, or a standalone worker session that is not tied to a project. Standalone sessions run in an AO-managed directory. Register a project first with ao project add for project-scoped sessions.
pull-requests
Workers do not push with personal credentials. The sandbox provides two socket helpers (their exact invocations are in the $AOPULLREQUESTHELP and $AOREVIEWHELP environment variables) plus one ao command.
red-team
Stress-test a plan, strategy, PRD, or launch with a room of hostile expert personas before you commit.
review-open-prs
Command "review-open-prs" from The-Artificer-of-Ciphers-LLC/skills-from-the-artificer, covering batch pr review directive — all open prs i did not author, phase a — enumerate target prs & build the queue, phase b — per-pr directive (runs once per queued $pr), 0. context anchoring and 1. preconditions.
co-change
List files that historically co-change with a target (git log heuristic; COCHANGE-style).