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/xyruscode/ai-sync/automationnpx skills add XyrusCode/ai-sync --skill automationgit clone --depth 1 https://github.com/XyrusCode/ai-syncWhat 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.00034 | $0.03366 |
| Opus 5 | $0.00017 | $0.01683 |
| Sonnet 5 | $0.00007 | $0.00673 |
| Haiku 4.5 | $0.00003 | $0.00337 |
Grade A, and why
automation 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 yesterday.
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 — 367 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Automation
Automation owns executable work: trigger, input contract, execution, result contract, files, delivery, runs, assets, and workspace.
Commercial Limits
- Only enabled regular Automations count. Cron jobs and widget tasks use separate limits.
- Disabled tasks are kept and use no slot. Disable one before enabling another when a limit is full.
- On downgrade, the newest tasks by
createdAtstay enabled. Older tasks are disabled, not deleted. - A running task finishes after downgrade; disabling blocks future automatic runs.
- If a quota reminder says not to retry, report the limit and ask the user which task to disable.
Create Contract
Automation.create requires sibling top-level fields:
titledescription: a concise, non-empty statement of purposetriggerinputexecutionresult
delivery is optional. Use it only for local notification delivery; omit it or pass [] when no notification is needed.
input is only the input contract:
{ kind: "none" }{ kind: "text", defaultInput? }{ kind: "json", schema, defaultInput? }
Use result.kind: "artifact" for structured output and Widget delivery. The artifact must be a JSON object that matches result.schema.
Minimum Python artifact Automation:
{
"action": "create",
"title": "Daily metric producer",
"description": "Produces a daily metric artifact for downstream display.",
"trigger": { "kind": "manual" },
"input": {
"kind": "json",
"schema": { "type": "object", "properties": {}, "additionalProperties": false },
"defaultInput": {}
},
"execution": {
"kind": "code",
"runtime": "python",
"entryRef": { "kind": "path", "base": "automation", "path": "automation.py" }
},
"result": {
"kind": "artifact",
"schema": {
"type": "object",
"properties": { "summary": { "type": "string" } },
"required": ["summary"],
"additionalProperties": true
}
},
"delivery": []
}
After create, write the Python program to data.metadata.codeEntry.path. The Automation assets root is data.metadata.roots.assetsRoot; its run workspace is data.metadata.roots.workspaceRoot.
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.
- yesterday First seen · 367 lines · 34 tokens per session scan A 6b15310cb5e2
automation is a skill published in the GitHub repository XyrusCode/ai-sync (2 stars, last pushed 2d ago), licensed MIT. It adds 34 tokens to every session and 3,366 once invoked, about $0.0002 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…