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/first-sessionnpx skills add du-phan/resilio-app --skill first-sessiongit 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/first-session)<a href="https://agentmods.dev/skills/du-phan/resilio-app/first-session"><img src="https://agentmods.dev/badge/skills/du-phan/resilio-app/first-session.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.00054 | $0.01306 |
| Opus 5 | $0.00027 | $0.00653 |
| Sonnet 5 | $0.00011 | $0.00261 |
| Haiku 4.5 | $0.00005 | $0.00131 |
Grade A, and why
first-session 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 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.
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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
First session
Keep the conversation in athlete language. Do not expose commands, tools, skill names, or local paths. Use one Poetry environment throughout.
Authority and safety
- Treat synchronized completed activities, wellness, and sport settings as the factual provider record.
- Treat profile fields, constraints, goals, and approved VDOT as athlete-confirmed facts.
- Present provider thresholds, heart rates, power, pace, and VO2 max only as candidates. Never copy them into the profile without explicit confirmation.
- Never derive a missing value, convert provider VO2 max into VDOT, or present a composite readiness or injury-risk score.
- Ask about pain, illness, pregnancy, medication, or medical restrictions when relevant. Do not diagnose; recommend appropriate professional care for medical red flags.
Workflow
-
Verify the CLI and account with:
poetry run resilio auth statusIf the credential is absent, ask the athlete to obtain their personal Intervals.icu API key. Store only
INTERVALS_ICU_API_KEY=<key>in.env.localwith mode0600. Never print or inspect the secret. -
Run the coordinated import:
poetry run resilio sync poetry run resilio sync --statusReport the returned window, counts, partial state, quarantines, and workout fulfillments exactly. Do not claim that quarantined or ambiguous rows were imported.
-
Establish dates and inspect factual state:
poetry run resilio dates today poetry run resilio status poetry run resilio profile get poetry run resilio profile candidates poetry run resilio memory list --type INJURY_HISTORY -
Create or update the profile from confirmed facts. Collect:
- athlete name, age, and running experience;
- minimum and maximum run days, unavailable days, and maximum session duration in minutes;
- athlete-managed sports, each as either a flexible weekly expectation or a recurring weekday pattern, with typical session duration and intensity;
- whether running, balanced training, or one active athlete-managed sport has priority when recovery constraints require a tradeoff;
- the IANA timezone used for training schedules;
- usual training location for local weather planning.
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 · 143 lines · 54 tokens per session scan A c70e8db6f6f7
first-session is a skill published in the GitHub repository du-phan/resilio-app (5 stars, last pushed 2d ago), licensed MIT. It adds 54 tokens to every session and 1,306 once invoked, about $0.0003 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-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…