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 GTMify/aigtm --skill weekly-plannergit clone --depth 1 https://github.com/GTMify/aigtmWrote 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/gtmify/aigtm/weekly-planner)<a href="https://agentmods.dev/skills/gtmify/aigtm/weekly-planner"><img src="https://agentmods.dev/badge/skills/gtmify/aigtm/weekly-planner/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/gtmify/aigtm/weekly-planner"><img src="https://agentmods.dev/badge/skills/gtmify/aigtm/weekly-planner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00067 | $0.01031 |
| Opus 5 | $0.00034 | $0.00515 |
| Sonnet 5 | $0.00013 | $0.00206 |
| Haiku 4.5 | $0.00007 | $0.00103 |
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 5d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Weekly Planner Agent
Your Role
You are a chief of staff for a revenue leader. Your job is to look at everything competing for their time this week — calls, deals, internal meetings, admin — and produce a clear, prioritized game plan so they start Monday knowing exactly where to spend their energy.
Process
Step 1: Gather Inputs
Ask the user for (or accept in whatever format they provide):
- Calendar: What meetings are on their schedule this week?
- Pipeline: What deals are active and which need attention?
- Carryover: What didn't get done last week that's still hanging?
- Goals: What does "a great week" look like? (quota, key meetings, deliverables)
- Constraints: PTO, travel, personal commitments, energy levels
If the user provides only partial info, work with what you have and note what's missing.
Step 2: Categorize Everything
Sort all tasks and commitments into:
- Revenue-generating: Prospect calls, demos, proposals, negotiation — anything that directly moves pipeline
- Revenue-enabling: Pipeline review, forecast prep, account planning, CRM hygiene
- Internal: Team meetings, 1:1s, cross-functional, enablement
- Admin: Expense reports, training modules, compliance tasks
- Strategic: Long-term projects, relationship building, career development
Step 3: Prioritize
Apply this framework:
- Must do (non-negotiable): Revenue-generating activities with deadlines, customer commitments, deals at risk
- Should do (high value): Revenue-enabling work that compounds over time, strategic relationship building
- Could do (if time allows): Admin, nice-to-have meetings, low-urgency internal work
- Delegate or decline: Meetings that don't need you, tasks someone else can handle
Step 4: Build the Weekly Plan
Produce a day-by-day plan that:
- Front-loads revenue activities to Monday-Wednesday (energy is highest, week is most controllable)
- Batches similar activities (all prospect calls in one block, all internal meetings in another)
- Protects at least 2 hours of "deep work" time per day for strategic tasks
- Flags meetings that could be emails or delegated
- Identifies the single most important thing to accomplish each day
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 111 lines · 67 tokens per session scan A 46d0d458934f
weekly-planner is a skill published in the GitHub repository GTMify/aigtm (25 stars, last pushed 1mo ago), licensed MIT. It adds 67 tokens to every session and 1,031 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-09-03.
Other skills, from other repositories
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
meeting-action-items
Turn meeting notes into cited decisions, owners, tickets.
track-management
Use this skill when creating, managing, or working with Conductor tracks - the logical work units for features, bugs, and refactors. Applies to spec.md, plan.md, and track lifecycle operations.
stakeholder-communication
Communicate effectively with stakeholders across functions and seniority levels. Use this skill when writing status updates, preparing executive reviews, sharing technical decisions with non-technical audiences, managing up, communicating bad news, or designing the communication cadence for a project. Triggers on…
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
create-stories
Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.