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/bindingnpx skills add XyrusCode/ai-sync --skill bindinggit 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.00035 | $0.01065 |
| Opus 5 | $0.00017 | $0.00532 |
| Sonnet 5 | $0.00007 | $0.00213 |
| Haiku 4.5 | $0.00003 | $0.00106 |
Grade A, and why
binding 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Binding
Binding is the durable connection between an Automation and a Widget:
Automation artifact -> Widget.slots.main
Widget.events.submit -> Automation input
Binding.create validates and attaches the connection. It does not run the Automation or display the Widget.
Create
Before creating:
- Automation uses
result.kind: "artifact"with an object schema. - Widget declares
slots.main.kind: "json"with an object schema compatible with the Automation artifact. - If Widget declares
events.submit, its schema is compatible with the Automation input contract. - Widget
index.htmlexists and validates.
{
"action": "create",
"kind": "automation_widget",
"automationId": "automation_generated",
"widgetId": "widget_generated"
}
A Widget has one active main Binding at Widget.bindings.main. Creating another Binding for the same Widget makes the new Binding active. The previous Binding becomes invalid with a superseded validation issue, and its deliveries cannot overwrite Widget.latestData.main.
Status
pending_run: schemas and render checks pass, but no current artifact has been delivered through this Binding.valid: contracts pass and current artifact/render evidence is valid.invalid: one or more validation issues require repair.
Binding artifact validation uses Automation.latestArtifactRunId.
Automatic Revalidation
Automation.update and Widget.update revalidate related Bindings. Inspect revalidatedBindings in the update response before running or enabling automatic work.
Writing index.html or another Widget workspace resource does not call Widget.update, so it does not automatically revalidate the active Binding. After page or resource changes, call Widget.validate, then call Binding.validate for Widget.bindings.main before running the Automation.
Common changes that require attention:
- Automation input schema changes affect
events.submitcompatibility. - Automation result schema changes affect
slots.maincompatibility. - Widget slot or event schema changes affect both directions.
- Widget page changes can affect render validation.
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 · 100 lines · 35 tokens per session scan A fe2e0a56709c
binding is a skill published in the GitHub repository XyrusCode/ai-sync (2 stars, last pushed 2d ago), licensed MIT. It adds 35 tokens to every session and 1,065 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…