What is weekly-plan-generate?

A workflow for designing and checking one week of running workouts from an existing training plan or baseline assessment.

Use it to create a proposal for Week 1, another empty week, or a revised week that still needs athlete approval.

It keeps planned workouts separate from completed evidence and requires relevant dates, athlete information, workout capabilities, and weather before proposing sessions.

How du-phan/resilio-app configures Claude Code and Codex

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/weekly-plan-generate/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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/du-phan/resilio-app/weekly-plan-generate/github.svg)](https://agentmods.dev/skills/du-phan/resilio-app/weekly-plan-generate)

Your own site

<a href="https://agentmods.dev/skills/du-phan/resilio-app/weekly-plan-generate"><img src="https://agentmods.dev/badge/skills/du-phan/resilio-app/weekly-plan-generate/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/du-phan/resilio-app/weekly-plan-generate"><img src="https://agentmods.dev/badge/skills/du-phan/resilio-app/weekly-plan-generate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,371 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00049	$0.02371
Opus 5.5	$0.00020	$0.00948
Sonnet 5.5	$0.00010	$0.00474
Haiku 4.5	$0.00005	$0.00237

Measured 4d ago against content hash 0a1754a2b1ee, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

weekly-plan-generate 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.

.agents/skills/weekly-plan-generate/SKILL.md · 214 lines

How it starts

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

Generate one training week

Operate non-interactively. Write a new proposal file; do not apply it, approve it, or overwrite a previously presented proposal.

Evidence acquisition

Resolve the target week:

poetry run resilio plan status
poetry run resilio plan show
poetry run resilio plan week --week <WEEK_NUMBER>
poetry run resilio profile get
poetry run resilio workout capabilities --sport run

Compute dates through the CLI, never mentally. Fetch the future-target planning context with an evidence date no later than today:
```
poetry run resilio dates week-boundaries --start <WEEK_MONDAY>
poetry run resilio coach create-planning-context \
  --week <WEEK_NUMBER> \
  --evidence-as-of <YYYY-MM-DD> \
  --history-weeks <COUNT>
```
Retain the returned immutable reference for the proposal. Keep target_week separate from recent_history. Never request a future weekly review or treat a future target week as completed evidence.

Weather Context & Adjustments

Fetch local weather before choosing workout days:
```
poetry run resilio weather week --start <WEEK_START>
```
If the weather lookup fails or weather data unavailable is reported, continue with the training-logic decision and state the uncertainty. Do not use web weather. Weather informs only the running sessions prescribed by this workflow.

Coaching decisions

Review the full active plan alongside the target context using the shared macro continuity procedure before authoring exact runs. Confirm they describe the same active plan; reacquire evidence if it changed. For race macros, explain why remaining targets are retained or prepare a same-cycle amendment before generating replacement workouts. Future targets remain strategic intentions, never completed exposure.
When the athlete requests a calendar check or identifies a calendar conflict, use the existing read-only upcoming-activity workflow. Keep planned other-sport facts separate from completed exposure and include their scheduling effects and uncertainty in the proposal.
Branch on target_week.plan_kind:

Read the full file on GitHub · 214 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.

4d ago Changed · +21 lines 0a1754a2b1ee
1mo ago Changed · +26 lines 2d2ac23790a5
1mo ago Changed · +6 lines 85c6ac11ebd6
2mo ago First seen · 161 lines · 49 tokens per session scan A eb2d610baef0

Subscribe to this mod's changes

weekly-plan-generate is a skill published in the GitHub repository du-phan/resilio-app (5 stars, last pushed 5d ago), licensed MIT. It adds 49 tokens to every session and 2,371 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-31.

weekly-plan-generate next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
weekly-plan-generatedu-phan/resilio-app	Skill	5	5d ago	MIT	A	49	Claude Code, Codex
imagegenopenai/codex	Skill	133k	yesterday	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	yesterday	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	313k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	95	Claude Code
next-partial-prefetching-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	103	Claude Code

resilio-app: Skill for Claude Code