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/doc-sync-check/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/doc-sync-check)<a href="https://agentmods.dev/skills/zerodeng01/sublinkpro/doc-sync-check"><img src="https://agentmods.dev/badge/skills/zerodeng01/sublinkpro/doc-sync-check/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/doc-sync-check"><img src="https://agentmods.dev/badge/skills/zerodeng01/sublinkpro/doc-sync-check.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.00034 | $0.02424 |
| Opus 5.5 | $0.00014 | $0.00970 |
| Sonnet 5.5 | $0.00007 | $0.00485 |
| Haiku 4.5 | $0.00003 | $0.00242 |
Grade A, and why
doc-sync-check 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 — 320 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Sync Check Skill
Checklist for ensuring documentation stays synchronized with code changes.
When to use this skill
Use this skill when changes affect:
- User-visible behavior or features
- API contracts or endpoints
- Configuration options or environment variables
- Deployment or installation procedures
- Developer workflows or contribution processes
- Build or validation processes
Core Principle
Documentation must be updated in the same PR as the code change. Outdated docs are a maintenance burden and user pain point.
Prerequisites
Before running this checklist:
- Identify which documentation files might be affected
- Read AGENTS.md section "Documentation expectations"
- Review CONTRIBUTING.md for documentation standards
Quick Reference: Which Docs to Update
| Change Type | Docs to Check |
|---|---|
| User-facing feature | README.md + .zh-CN.md, docs/features/*.md + .zh-CN.md |
| Configuration option | docs/configuration.md + .zh-CN.md, example configs |
| Installation/deployment | docs/installation.md + .zh-CN.md, skill-sublinkpro/reference/deploy.md |
| API endpoint | skill-sublinkpro/reference/api.md |
| Developer workflow | docs/development.md + .zh-CN.md, CONTRIBUTING.md + .zh-CN.md |
| Architecture/guidelines | AGENTS.md |
| New documentation | skill-sublinkpro/reference/docs.md (documentation map) |
Feature Documentation Checklist
When user-facing features change:
README updates
- Updated
README.mdif feature overview affected - Updated
README.zh-CN.md(Chinese version) - Updated feature list if new feature added
- Updated screenshots/GIFs if UI changed significantly
Feature docs
- Updated relevant
docs/features/*.mdfile - Updated corresponding
.zh-CN.mdfile - Added new feature doc if new feature (both languages)
- Updated examples and usage instructions
- Verified code samples are accurate
Cross-references
- Updated links from README to feature docs
- Updated internal cross-references in docs
- Added new doc to
docs/index/TOC (if applicable)
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 · 320 lines · 34 tokens per session scan A 0829c774b0ec
doc-sync-check is a skill published in the GitHub repository ZeroDeng01/sublinkPro (1,727 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 2,424 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…