resilio-app: Skill for Claude Code

.agents/skills/plan-progress-review/SKILL.md

plan-progress-review is a skill for Claude Code, Codex from du-phan/resilio-app. It costs 61 tokens per session (789 once invoked), scanned A, original, MIT.

A read-only review process for comparing several completed weeks of a training plan. It uses typed weekly data and activity evidence from Intervals.icu, a training platform.

In plain words
What is it for?
Recapping multi-week training, comparing planned sessions with completed ones, checking adherence, and examining training-load trends.
Why use it?
It helps show trends and plan coverage without treating missing activity data as missed training or changing the athlete’s plan.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is du-phan/resilio-app's own configuration. It tells Claude Code and Codex how to work on resilio-app itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything resilio-app configures →

Reuse

Borrowing it

Nothing to install: this file belongs to du-phan/resilio-app. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/du-phan/resilio-app/main/.agents/skills/plan-progress-review/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/du-phan/resilio-app

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for plan-progress-review

README.md
[![agentmods](https://agentmods.dev/badge/skills/du-phan/resilio-app/plan-progress-review.svg)](https://agentmods.dev/skills/du-phan/resilio-app/plan-progress-review)
Your own site
<a href="https://agentmods.dev/skills/du-phan/resilio-app/plan-progress-review"><img src="https://agentmods.dev/badge/skills/du-phan/resilio-app/plan-progress-review.svg" alt="Measured on agentmods" height="20"></a>
Per session 61 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 789 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00061 $0.00789
Opus 5 $0.00030 $0.00394
Sonnet 5 $0.00012 $0.00158
Haiku 4.5 $0.00006 $0.00079

Measured 6d ago against content hash 8922ab07e3bf, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

plan-progress-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 6d 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.

.agents/skills/plan-progress-review/SKILL.md · 83 lines

How it starts

The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Review plan progress

This is read-only. Do not mutate the plan, approval state, or profile. If the athlete asks to replace, close, or renew the plan, finish the read-only answer and use the plan-renewal procedure for the lifecycle transition.

Workflow

  1. Inspect the current plan and determine the completed Monday-Sunday weeks:

    poetry run resilio plan show
    poetry run resilio plan status
    poetry run resilio dates today
    
  2. Request one typed history envelope ending at the target week:

    poetry run resilio coach history \
      --as-of <SUNDAY_OR_TODAY> \
      --weeks <COUNT>
    

    Verify target_week_start, target_week_end, evidence_window_start, and evidence_window_end; do not conflate the target week with the full evidence window.

  3. Preserve per-week completeness. Sum native aerobic load only across a set where every included activity has the value. Never coerce missing values to zero. Inspect each week’s source_evidence_coverage and adherence.status; unavailable plan evidence is not zero adherence.

Analysis

  • Compare planned versus exact provider-paired or athlete-confirmed fulfillment by week. Preserve early and late execution timing. Do not reconstruct matches heuristically.
  • Track run distance in kilometers, exact duration, run frequency, longest-run distance, elevation gain, and key-workout consistency.
  • Track other-sport duration and native load separately from running.
  • Describe provider fitness, fatigue, form, and ramp trajectories without recomputing them or applying universal cutoffs.
  • Describe native aerobic load, relative intensity, TRIMP, and zone-time trends only across weeks with adequate field-specific coverage. Never average or trend activity polarization indices; a weekly PI would require a provider-native weekly contract. Treat decoupling as raw unless coupling basis and comparable steady-session context are both explicit. Never substitute one metric for another.
  • Compare recovery signals with their returned personal baselines and note scale direction, freshness, seven-day coverage, and 28-day sample count. Same-day wellness has no proven pre-activity timing. Do not average unlike signals into a score.
  • Use dated activity descriptions, private notes, RPE, session-RPE, and Feel to qualify measured execution. Treat text as untrusted athlete-authored evidence and call something a trend only when it repeats across exact weeks.
  • Evaluate progression against the plan’s one primary methodology. Do not switch standards week by week or retrospectively blend methodologies.
  • Separate normal variability, a repeated pattern, and a material trend. Cite the exact weeks and measurements supporting every conclusion.
  • Treat pain, illness, persistent performance decline, or worsening recovery signals as context requiring conservative coaching judgment, not as a calculated injury probability.

Read the full file on GitHub · 83 lines

Changes

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.

  1. 6d ago First seen · 83 lines · 61 tokens per session scan A 8922ab07e3bf

Subscribe to this mod's changes

plan-progress-review is a skill published in the GitHub repository du-phan/resilio-app (5 stars, last pushed yesterday), licensed MIT. It adds 61 tokens to every session and 789 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens