sublinkPro is a web application for managing proxy subscriptions, including importing providers, testing speed, routing traffic through relays, monitoring usage, and managing services through Telegram. It is built with Go on the backend and React on the frontend for people who manage proxy configurations and network traffic.
Borrowing it
Nothing to install: this file belongs to ZeroDeng01/sublinkPro. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ZeroDeng01/sublinkPro/main/.agents/skills/cross-layer-sync/SKILL.mdgit clone --depth 1 https://github.com/ZeroDeng01/sublinkProWrote 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/skills/zerodeng01/sublinkpro/cross-layer-sync)<a href="https://agentmods.dev/skills/zerodeng01/sublinkpro/cross-layer-sync"><img src="https://agentmods.dev/badge/skills/zerodeng01/sublinkpro/cross-layer-sync/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/skills/zerodeng01/sublinkpro/cross-layer-sync"><img src="https://agentmods.dev/badge/skills/zerodeng01/sublinkpro/cross-layer-sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00036 | $0.01749 |
| Opus 5.5 | $0.00014 | $0.00700 |
| Sonnet 5.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 2mo 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.
- 2mo 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,727 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 1,749 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 skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…