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/macakdev/gc-mcp/weekly-plannernpx skills add macakdev/GC-MCP --skill weekly-plannergit clone --depth 1 https://github.com/macakdev/GC-MCPWhat 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.00047 | $0.00370 |
| Opus 5 | $0.00023 | $0.00185 |
| Sonnet 5 | $0.00009 | $0.00074 |
| Haiku 4.5 | $0.00005 | $0.00037 |
Grade A, and why
weekly-planner 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 2d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 2d ago First seen · 33 lines · 47 tokens per session scan A fdd336e3a21c
weekly-planner is a skill published in the GitHub repository macakdev/GC-MCP (4 stars, last pushed 23d ago), with no licence file. It adds 47 tokens to every session and 370 once invoked, about $0.0002 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
garmin-connect
Garmin Connect CLI for activities, health, body composition, workouts, devices, gear, goals, and more.
garmin-trainer
Adaptive 12-week training plan generator using Garmin Connect data. Creates structured workouts and schedules them on your Garmin calendar. Use this skill whenever the user asks about training plans, workout scheduling, race preparation, building fitness for upcoming events, or wants to generate/update their training…
garmin-health
Fetches and reports the user's Garmin Connect health and workout data (sleep, HRV, stress, Body Battery, resting HR, steps, calories, HR zones, per-km splits, strength-training exercise sets with reps/weight) via the local garminpipeline CLI, writing markdown/CSV files into data/library/. Use when the user asks to…
release-garmin-pipeline
Cut a new GitHub release of the Garmin Health Pipeline (Windows .exe + macOS .app via GitHub Actions), with bilingual RU/EN release notes. Use when the user asks to release, ship, publish a new version, or says "коммит, пуш, релиз" / "новый релиз" for this project.
garmin-connect
Query Garmin Connect fitness and health data including activities, athlete stats, sleep, heart rate, stress, and body battery. Use when the user asks about Garmin data, workouts, training, or health metrics.
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.