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/zerodeng01/sublinkpro/cross-layer-syncnpx skills add ZeroDeng01/sublinkPro --skill cross-layer-syncgit clone --depth 1 https://github.com/ZeroDeng01/sublinkProWhat 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.00036 | $0.01749 |
| Opus 5 | $0.00018 | $0.00874 |
| Sonnet 5 | $0.00007 | $0.00350 |
| Haiku 4.5 | $0.00004 | $0.00175 |
Grade A, and why
cross-layer-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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cross-Layer Synchronization Check Skill
Checklist for ensuring all impacted layers are updated together when changes affect multiple parts of the application.
When to use this skill
Use this skill when changes affect:
- API contracts, routes, request/response structures
- Frontend-backend data flow
- Configuration semantics
- Documentation that reflects runtime behavior
- User-facing text or error messages
- Deployment or build processes
Core Principle
Changes must be atomic across layers: When a change affects multiple layers (backend, frontend, docs, skill API reference), all impacted layers must be updated in the same PR/commit.
Prerequisites
Before running this checklist:
- Identify which layers your change touches
- Read AGENTS.md section 9 "Cross-layer synchronization"
- Review CONTRIBUTING.md for cross-layer sync requirements
Backend → Frontend Sync Checklist
When backend changes affect:
API contracts
- Updated route paths in frontend (
webs/src/api/) - Updated request payload structures
- Updated response handling
- Updated error handling
- Updated TypeScript types (if applicable)
Fields
- Updated field names in frontend requests
- Updated field validation
- Updated form components (
webs/src/views/) - Updated display logic
Permissions
- Updated permission checks in frontend
- Updated UI visibility logic
- Updated route guards
Response structures
- Updated response parsing
- Updated state management
- Updated display components
- Updated loading/error states
Task results or notifications
- Updated task result rendering
- Updated notification display
- Added i18n keys if needed (
webs/src/i18n/locales/)
Skill API (if /api/v1/* or /c/* changed)
- Updated
skill-sublinkpro/reference/api.mdendpoint documentation - Updated
skill-sublinkpro/SKILL.mdworkflow descriptions (if affected) - Updated request/response examples
- Updated error handling examples
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.
- 2d ago First seen · 224 lines · 36 tokens per session scan A b185d561b735
cross-layer-sync is a skill published in the GitHub repository ZeroDeng01/sublinkPro (1,605 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 1,749 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…