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/du-phan/resilio-app/complete-setupnpx skills add du-phan/resilio-app --skill complete-setupgit clone --depth 1 https://github.com/du-phan/resilio-appWrote 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/du-phan/resilio-app/complete-setup)<a href="https://agentmods.dev/skills/du-phan/resilio-app/complete-setup"><img src="https://agentmods.dev/badge/skills/du-phan/resilio-app/complete-setup.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.00042 | $0.01254 |
| Opus 5 | $0.00021 | $0.00627 |
| Sonnet 5 | $0.00008 | $0.00251 |
| Haiku 4.5 | $0.00004 | $0.00125 |
Grade B, and why
complete-setup scanned grade B with 1 finding 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- Use `sudo pip` How it starts
The opening of the file, as written. The whole thing — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Complete Setup (macOS only)
Scope
This skill performs safe environment setup for beginners on macOS only.
If the platform is not macOS, stop and explain that non-macOS setup is deferred in this iteration.
Python support target: >=3.11,<4.0.
Safety Rules (hard)
Never do these during onboarding:
- Replace or delete system Python binaries/symlinks
- Change OS-managed default Python interpreter mapping
- Require global shell aliases for
python3 - Use
sudo pip - Advance to the next phase before validation passes
Always prefer explicit interpreter usage (python3.12 or python3.11) over system mutation.
Workflow Checklist
Copy and update this checklist while running setup:
Setup Progress:
- [ ] Phase 1: Detection gates passed
- [ ] Phase 2: Python available (>=3.11)
- [ ] Phase 3: Package installed and `resilio` runnable
- [ ] Phase 4: Config initialized
- [ ] Phase 5: Final verification + handoff
Phase 1: Detection Gates (must run in order)
Gate 1: Repo root
if [ ! -f pyproject.toml ] || [ ! -d resilio ]; then
echo "Not in repo root. cd into resilio and retry."
exit 1
fi
Gate 2: Platform
uname
Darwin-> continue- anything else -> stop with defer message
Gate 3: Interpreter selection (safe)
PYTHON_CMD=""
if command -v python3 >/dev/null 2>&1 && python3 -c 'import sys; raise SystemExit(0 if sys.version_info >= (3, 11) else 1)'; then
PYTHON_CMD="python3"
elif command -v python3.12 >/dev/null 2>&1; then
PYTHON_CMD="python3.12"
elif command -v python3.11 >/dev/null 2>&1; then
PYTHON_CMD="python3.11"
fi
PYTHON_CMDset -> Python gate passed- empty -> run Phase 2
Gate 4: Install path discovery
poetry --version >/dev/null 2>&1
- success -> Poetry path available
- failure -> venv path
Gate 5: Package runnable check
PACKAGE_READY=false
if command -v resilio >/dev/null 2>&1; then
resilio --help >/dev/null 2>&1 && PACKAGE_READY=true
elif poetry --version >/dev/null 2>&1; then
poetry run resilio --help >/dev/null 2>&1 && PACKAGE_READY=true
fi
What ships with it
9 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.
- evaluations/fresh_macos_m1.json 1.2 KB
- evaluations/macos_pyenv_fallback.json 785 B
- evaluations/partial_setup_recovery.json 841 B
- evaluations/README.md 482 B
- examples/example_macos_homebrew.md 1.5 KB
- references/environment_checks.md 1.8 KB
- references/package_installation.md 963 B
- references/python_setup.md 1.5 KB
- references/troubleshooting.md 1.5 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.
- 3d ago First seen · 213 lines · 42 tokens per session scan B acd51f3d7242
complete-setup is a skill published in the GitHub repository du-phan/resilio-app (5 stars, last pushed 14d ago), licensed MIT. It adds 42 tokens to every session and 1,254 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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…