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/skill-sublinkpronpx skills add ZeroDeng01/sublinkPro --skill skill-sublinkprogit 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/skill-sublinkpro)<a href="https://agentmods.dev/skills/zerodeng01/sublinkpro/skill-sublinkpro"><img src="https://agentmods.dev/badge/skills/zerodeng01/sublinkpro/skill-sublinkpro.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00056 | $0.07150 |
| Opus 5 | $0.00028 | $0.03575 |
| Sonnet 5 | $0.00011 | $0.01430 |
| Haiku 4.5 | $0.00006 | $0.00715 |
Grade C, and why
sublinkpro scanned grade C with 3 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 4d 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
6. `POST /api/v1/template/ai/edit-sessions/{sessionId}/accept` (`--json` with optional `currentText` set to the editor's current text). Send `currentText` whenever you have the current editor text, especially after a pri Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
| **JSON** (POST/PUT) | `curl -s -H "X-API-Key: $SUBLINK_API_KEY" -H "Content-Type: application/json" -d '{"k":"v"}' "$SUBLINK_BASE_URL<path>"` | Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Under the hood the assistant calls the SublinkPro REST API with curl (or the optional Python helper). Authentication and API quirks are handled for you. How it starts
The opening of the file, as written. The whole thing — 315 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SublinkPro AI Skill
Control your SublinkPro instance through natural language. This skill lets an AI assistant call the SublinkPro API directly, so you can manage nodes, subscriptions, shares, airports, and templates without opening the web UI.
Installation
-
Copy this directory into your AI agent's skills directory. The exact path depends on your tool — for Claude Code it is
~/.claude/skills/sublinkpro:cp -r skill-sublinkpro ~/.claude/skills/sublinkpro # or symlink if you cloned the repo: ln -s /path/to/sublinkE/skill-sublinkpro ~/.claude/skills/sublinkproFor other agents, place the directory wherever that tool loads skills from.
-
Set environment variables:
export SUBLINK_BASE_URL=http://localhost:8000 # your SublinkPro server address export SUBLINK_API_KEY=prefix_xxx_yyy # your API key -
Get an API key:
- Open SublinkPro web UI
- Go to Settings → Access Keys
- Click Create (or Add)
- Copy the key (shown only once) and set
SUBLINK_API_KEY
How to Use
You don't need to know the API, the parameter names, or what data already exists. Just say what you want in plain language and the assistant guides you the rest of the way. If you're not sure what's possible, simply ask "what can I do?" and you'll get a menu.
Example openers:
- "I want to add a node" → the assistant walks you through it step by step
- "Add this node:
vless://..." - "Help me build a new subscription"
- "Show me all my subscriptions"
- "Create a share link"
- "Import an airport"
- "Edit the 'ACL4SSR' template to block ads"
- "Show dashboard stats"
- "How does the smart tag system work?" → the assistant fetches and explains the relevant documentation
- "I don't have SublinkPro yet — help me set it up" → the assistant guides you through deploying it (see Deploy below)
Under the hood the assistant calls the SublinkPro REST API with curl (or the optional Python helper). Authentication and API quirks are handled for you.
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 315 lines · 56 tokens per session scan C 93937771ff32
sublinkpro is a skill published in the GitHub repository ZeroDeng01/sublinkPro (1,611 stars, last pushed 3d ago), licensed MIT. It adds 56 tokens to every session and 7,150 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 3 findings (strips warnings and disclaimers, sends data to an external url, makes network calls). 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…