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/security-review/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/security-review)<a href="https://agentmods.dev/skills/zerodeng01/sublinkpro/security-review"><img src="https://agentmods.dev/badge/skills/zerodeng01/sublinkpro/security-review/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/security-review"><img src="https://agentmods.dev/badge/skills/zerodeng01/sublinkpro/security-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high YARA Match · line 61 YARA rule matched a hack tool or exploit indicator (offensive tools, reconnaissance, privilege escalation, or exploit frameworks).Fix: Remove offensive tool references and exploit code. Legitimate agent skills should not contain penetration testing tools, exploit frameworks, or reconnaissance utilities.
- high Prompt Injection · line 191 This pattern attempts to override system instructions or ignore safety constraints. Without LLM analysis, manual review is recommended.Fix: Remove or rewrite any text that instructs the agent to ignore prompts, override safety rules, or trust unverified content. Ensure skill content cannot be injected to alter agent behavior.
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.00039 | $0.02144 |
| Opus 5.5 | $0.00016 | $0.00858 |
| Sonnet 5.5 | $0.00008 | $0.00429 |
| Haiku 4.5 | $0.00004 | $0.00214 |
Grade A, and why
security-review 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 — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Review Skill
This skill provides a comprehensive security review checklist for code changes that involve authentication, authorization, sensitive data handling, or security-critical features.
When to use: When making changes to:
- Authentication/authorization logic
- MFA (Multi-Factor Authentication) functionality
- Sensitive data handling (passwords, tokens, API keys, secrets)
- API endpoints with permission requirements
- Input validation and sanitization
- Database queries
- Cryptographic operations
- CORS/CSP configurations
- Session management
- File upload/download functionality
Security Review Checklist
🔐 1. Authentication & Authorization
Check for:
- Authentication bypass: Can the endpoint/feature be accessed without proper authentication?
- Authorization checks: Are user permissions verified before allowing access?
- Role-based access control: Are roles (admin, user, guest) properly enforced?
- Token validation: Are JWT/API tokens properly validated (signature, expiration, issuer)?
- Session security: Are sessions properly managed (timeout, secure flags, HttpOnly)?
Detailed guide: references/authentication-guide.md (includes code examples)
Relevant files:
api/auth.goapi/auth_mfa.gomiddlewares/auth.gomiddlewares/mfa.go
🔑 2. MFA (Multi-Factor Authentication)
Check for:
- MFA enforcement: Is MFA required for sensitive operations?
- MFA bypass prevention: Can MFA be circumvented through alternate flows?
- Backup codes security: Are backup codes securely generated and stored?
- TOTP secret protection: Are TOTP secrets encrypted at rest?
- Rate limiting: Is there rate limiting on MFA verification attempts?
Detailed guide: references/mfa-guide.md
Relevant files:
api/auth_mfa.gomodels/mfa.gomiddlewares/mfa.go
🛡️ 3. Sensitive Data Handling
Check for:
- Password storage: Are passwords hashed with bcrypt/argon2 (never plain text)?
- Secrets in logs: Are secrets/tokens masked in logs and error messages?
- Secrets in responses: Are sensitive fields (passwords, tokens) excluded from API responses?
- Secrets in transit: Are sensitive data transmitted over HTTPS only?
- Secrets in database: Are secrets encrypted at rest (API keys, tokens)?
What ships with it
10 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.
- references/api-security-guide.md 4.7 KB
- references/authentication-guide.md 2.3 KB
- references/cryptography-guide.md 4.6 KB
- references/database-security-guide.md 3.2 KB
- references/dependency-security-guide.md 3.7 KB
- references/file-security-guide.md 5.0 KB
- references/input-validation-guide.md 4.6 KB
- references/mfa-guide.md 1.9 KB
- references/sensitive-data-guide.md 3.3 KB
- references/session-management-guide.md 4.7 KB
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 · 243 lines · 39 tokens per session scan A 94479a73f9d0
security-review is a skill published in the GitHub repository ZeroDeng01/sublinkPro (1,727 stars, last pushed yesterday), licensed MIT. It adds 39 tokens to every session and 2,144 once invoked, about $0.0002 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…