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 skills add gtapps/hermitd --skill monday-planninggit clone --depth 1 https://github.com/gtapps/hermitdWrote 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/gtapps/hermitd/monday-planning)<a href="https://agentmods.dev/skills/gtapps/hermitd/monday-planning"><img src="https://agentmods.dev/badge/skills/gtapps/hermitd/monday-planning/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.
<a href="https://agentmods.dev/skills/gtapps/hermitd/monday-planning"><img src="https://agentmods.dev/badge/skills/gtapps/hermitd/monday-planning.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00018 | $0.00764 |
| Opus 5.5 | $0.00007 | $0.00306 |
| Sonnet 5.5 | $0.00004 | $0.00153 |
| Haiku 4.5 | $0.00002 | $0.00076 |
Grade A, and why
monday-planning 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 11d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monday Planning
Goal
Read last week's training load from state/strava-weekly-baselines.json (written by weekly-load-review on Sunday). Generate a concrete weekly training plan suggestion and deliver it via the configured channel.
Steps
- Read
state/strava-weekly-baselines.json. If missing or last entry is not from yesterday (Sunday), callmcp__strava__get-recent-activitieswithperPage: 20to compute last week's totals manually. - Read last week's totals: run km, run sessions, elevation, strength sessions, bike sessions.
- Read the 4-week rolling average from the baseline file (or compute from available data).
- Apply planning logic (see below) to generate a 5–7 day training structure.
- Send a message via the configured channel. If no channel is configured, pipe the plan into
.hermit/bin/hermitd-run task note .hermit <id>only inside an open record's turn (otherwise skip the note) instead and skip the notification. Compose in the operator's configured voice, covering the load context, daily structure, and key workout. Example shape:🗓️ Week plan: [Mon date] Based on last week: [X]km running, [load flag] Suggested structure: Mon: [activity] Tue: [activity] Wed: [activity] Thu: [activity] Fri: [activity] Sat: [activity] Sun: [activity] Key session: [highlight the week's main workout] - Write the weekly plan to
.hermit/compiled/weekly-plan-<YYYY-MM-DD>.md(today's date) with frontmatter:
Body: the full 7-day schedule from Step 5, plus the load context and key session highlight.--- title: "Weekly Plan: <Mon date>" type: weekly-plan created: <ISO 8601> task: <T-... for the open record in this turn; omit this field otherwise> tags: [weekly-plan, training] --- - Pipe one line into
.hermit/bin/hermitd-run task note .hermit <id>only inside an open record's turn (otherwise skip the note) and finish this workflow.
Planning Logic
If last week was a load spike (>25% above average):
- Reduce total km by 15–20%
- Keep 1 quality session (tempo or intervals), rest easy
- Include at least 2 rest or active recovery days
- No long run (cap longest run at 10km)
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.
- 11d ago First seen · 71 lines · 18 tokens per session scan A b53745454946
monday-planning is a skill published in the GitHub repository gtapps/hermitd (79 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 764 once invoked, about $0.0001 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-10-02.
Other skills, from other repositories
cco-budget
Configure token budget limits, auto-compact settings, and view current budget status (model-aware — Claude 5 lineup, Opus 5.5 default fallback, full 1M context at standard price).
tg-account
A skill for using Telegram as the account owner through a local Telegram Desktop session. It can read chats and export messages, while writing actions require showing the target and exact text for confirmation.
ccc-resume-session
Load a saved session file from /.claude/sessions/ (latest, by date, or by path), read it fully, and brief project, state, what not to retry, blockers and next step before touching anything. Use when resuming work, continuing where you left off, or after a fresh session.
ccc-spawn
Spin self-contained work off on demand: a background subagent, a separate session (Cowork spawntask chip or CLI /spawn peer), or an independent expert pass; routes fan-outs to $ccc-fleet and chains to $ccc-relay. Use when the user types $ccc-spawn or wants a task done outside this thread.
scout-briefing
Launch a Scout morning briefing session as a background process. Auto-detects mode (morning briefing, consolidation, or weekend briefing) from the current time and day.
scout-consolidation
Launch a Scout consolidation session as a background process. Runs a lighter delta scan — captures what changed since the last run and updates action items and KB.