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/jlifyio/wyx/syncnpx skills add jlifyio/wyx --skill syncgit clone --depth 1 https://github.com/jlifyio/wyxWhat 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.00058 | $0.01661 |
| Opus 5 | $0.00029 | $0.00830 |
| Sonnet 5 | $0.00012 | $0.00332 |
| Haiku 4.5 | $0.00006 | $0.00166 |
Grade A, and why
sync 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sync Coordination Mapping
Generate a sync coordination map — a structured description of how independent concepts interact through synchronization handlers. A sync map replaces reading dozens of handler files with a single page showing the coordination topology, timing patterns, and error strategies.
Syncs implement the execution mechanics of concept interactions. Where CONCEPT.md
## interactions declares relationships, SYNCS.md specifies the execution mechanics:
when the sync fires, what data flows, when it skips, and how errors propagate.
How to interpret $ARGUMENTS
Determine the mode from the argument:
- Path to sync directory (e.g.
src/lib/server/syncs/): Retrofit mode — read the existing sync handlers, map the coordination patterns, and propose a SYNCS.md. Flag any patterns that bypass concept boundaries. - Sync description (e.g.
Order fulfillment → Inventory update): Greenfield mode — design a sync spec for the described coordination. Define trigger, flow, qualification, and error strategy. - No arguments: Discovery mode — analyze the project for sync-like patterns (event handlers, cross-concept calls, scheduled jobs, dispatch registrations) and list candidates. Do NOT generate full specs; ask the user which to elaborate. If discovery surfaces data transformation chains without cross-concept coordination, note that
/wyx:pipelinecovers those.
SYNCS.md Format
Write the spec as a SYNCS.md file placed in the sync directory (e.g. src/lib/server/syncs/SYNCS.md).
# syncs: [Module/Area Name]
## coordination graph
[Text diagram showing concept-to-concept flow through syncs]
[Concept] --(action)--> (SyncName) --> [Concept]
[Concept] --(action)--> (SyncName) --> [Concept]
--> [Concept]
## dispatching
- pattern: [event-driven | explicit-call | hybrid]
- error-isolation: [sync failure does NOT propagate to source | propagates]
- depth-limit: [max cascading depth, if applicable]
- context: [how correlation/tracing works across sync boundaries]
## sync: [SyncName]
trigger: [Concept.action | schedule(interval) | manual]
timing: [post-action | pre-validation | scheduled]
flow:
1. [Concept.action] → [what data is read]
2. [transform/filter/validate] → [what happens]
3. [Concept.action] → [what data is written]
qualification: [conditions for execution vs skip]
error: [isolated | propagates | skip-and-log]
file: [relative path to implementation]
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 · 145 lines · 58 tokens per session scan A c2b267427e84
sync is a skill published in the GitHub repository jlifyio/wyx (3 stars, last pushed 23d ago), licensed MIT. It adds 58 tokens to every session and 1,661 once invoked, about $0.0003 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
truecourse-hooks
Install, configure, or remove the TrueCourse pre-commit hook.
truecourse-analyze
Run TrueCourse architecture analysis on this repository.
truecourse-fix
Fix TrueCourse violations that have suggested fixes.
truecourse-list
List TrueCourse violations found in this repository.
code-quality-review
Run a maintainability and structure review focused on abstraction quality, branching complexity, file growth, canonical ownership, duplication, and refactoring opportunities. Use when the user asks for code quality review, maintainability review, 代码质量审查, 可维护性审查, or comments about whether the change stays easy to…
cognitive-interface-audit
Comprehensive cognitive interface audit with two modes and a single tier. Planning mode designs task models, user expertise mapping, and error tolerance strategy. Audit mode evaluates mental model alignment (Norman's Gulfs), consistency (Gestalt), error tolerance (Wood 7-layer defense), cognitive load (NASA-TLX…