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/kissrosecicd-hub/agents-evolution/v2raya-linux-basicnpx skills add kissrosecicd-hub/agents-evolution --skill v2raya-linux-basicgit clone --depth 1 https://github.com/kissrosecicd-hub/agents-evolutionWhat 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.00037 | $0.00414 |
| Opus 5 | $0.00018 | $0.00207 |
| Sonnet 5 | $0.00007 | $0.00083 |
| Haiku 4.5 | $0.00004 | $0.00041 |
Grade A, and why
v2raya-linux-basic 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 3d 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.
What it actually says
v2raya-linux-basic
Назначение:
- дать рабочий runbook по установке
v2rayAна Arch Linux, Ubuntu и Fedora; - зафиксировать UI-настройки для системного прокси, TUN и
RoutingA; - явно показать, как использовать ключи Outline (
ss://) вv2rayA.
Что покрывает:
- Установка
v2rayA+ core (xray/v2ray) по дистрибутивам. - Запуск и автозапуск через
systemd. - Вход в UI:
http://127.0.0.1:2017. - Готовый
RoutingAшаблон с local bypass + dev/media правилами. - Анти-DNS-подмена через DoH в UI.
- Импорт ключей Outline в
v2rayA.
Основной инструмент:
scripts/v2raya-install.sh
Быстрый старт:
# preview авто-детекта (без установки)
bash scripts/v2raya-install.sh
# выполнить установку
bash scripts/v2raya-install.sh --apply
# проверить install helper
bash scripts/v2raya-install.sh
# открыть reference
sed -n '1,260p' references/V2RAYA_LINUX_GUIDELINES.md
Ограничения:
- skill справочный, не запускает
sudoшаги автоматически; - не хранить ключи (
ss://...) в репозитории и логах; - для TUN/transparent proxy применять только через UI и проверять доступ после каждого изменения.
Reference:
references/V2RAYA_LINUX_GUIDELINES.md
What ships with it
2 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.
- 3d ago First seen · 47 lines · 37 tokens per session scan A aee9aeb0b936
v2raya-linux-basic is a skill published in the GitHub repository kissrosecicd-hub/agents-evolution (31 stars, last pushed 4mo ago), licensed MIT. It adds 37 tokens to every session and 414 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…