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 matteotitta/genesys-skills --skill weekly-plangit clone --depth 1 https://github.com/matteotitta/genesys-skillsWrote 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/matteotitta/genesys-skills/weekly-plan)<a href="https://agentmods.dev/skills/matteotitta/genesys-skills/weekly-plan"><img src="https://agentmods.dev/badge/skills/matteotitta/genesys-skills/weekly-plan/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/matteotitta/genesys-skills/weekly-plan"><img src="https://agentmods.dev/badge/skills/matteotitta/genesys-skills/weekly-plan.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.00118 | $0.01393 |
| Opus 5 | $0.00059 | $0.00696 |
| Sonnet 5 | $0.00024 | $0.00279 |
| Haiku 4.5 | $0.00012 | $0.00139 |
Grade A, and why
weekly-plan scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
For full per-phase commands and curl payloads → the premium reference. How it starts
The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/weekly-plan — Weekly planning orchestrator
Plan the week's work across all active clients. Scan communications, check engagement state, suggest tasks with the right skills and agents, then create them in Paperclip and Linear for automated execution.
For full 6-phase process (gather / state-check / suggest / approve / create / summary) → the premium reference. For agent IDs, project IDs, status IDs, and other Linear lookups → the premium reference.
Triggers
Invoke when user says:
- "/weekly-plan"
- "Let's plan the week"
- "What should we work on this week?"
- "Weekly planning"
Do NOT invoke when:
- User wants to create a single task (just create it directly)
- User asks for a daily briefing (use
/today) - User wants to run a specific skill (invoke that skill directly)
Prerequisites
- Paperclip server running at
http://127.0.0.1:3100 - Linear API key available (Paperclip secrets as
LINEAR_API_KEY) - Gmail and Calendar MCPs connected
Process at a glance
| Phase | Purpose | Output |
|---|---|---|
| 1. Gather | Pull from Gmail, Slack, Granola, Calendar (parallel) | notes/MMYY-weekly-context.md per client |
| 2. State check | Linear issues + client folders + ontology dependency check | Current-state map |
| 3. Suggest | Group tasks by client; assign skill + agent + dependencies | Structured task list |
| 4. Approve | Wait for user to approve / edit / reject | Approved task set |
| 5. Create | Linear issue + Paperclip task per approved item | Created task IDs |
| 6. Summary | Present what was created with agent routing | Summary report |
For full per-phase commands and curl payloads → the premium reference.
Agent routing (quick reference)
| Agent | Skills it runs |
|---|---|
| Researcher | company-context, competitor-research, ICP, TOV, transcripts, win-loss, brand-kit |
| Product Marketer | positioning, product-messaging, content-strategy, pricing |
| Growth Marketer | landing pages, case-study, lifecycle, email-nurture, webinar-brief |
| Content Creator | LinkedIn (all variants), youtube-scripts, aeo-content, thought-leadership, hype-man, newsletter |
| Sales | battlecards, demo-script, sales-deck, outreach-emails, abm-campaign, clay-search |
| Paid Marketer | ad-creative-brief, google-ads, linkedin-ads, paid-ads-audit, paid-campaign-strategy |
| Operator | skill-catalog, reviewers, brand-context, runbook, dashboard, experiment, workflow-design, recall |
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 · 137 lines · 118 tokens per session scan A 31632e40a8e1
weekly-plan is a skill published in the GitHub repository matteotitta/genesys-skills (36 stars, last pushed 1mo ago), licensed MIT. It adds 118 tokens to every session and 1,393 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
gingiris-b2b-growth
🇺🇸 B2B SaaS Growth — PLG vs SLG Playbook — Diagnose whether your problem is distribution, pricing, or PMF. PLG/SLG selection by ACV and sales cycle, the 5-stage path from $0 to $10M ARR, NRR discipline, affiliate & channel motion, enterprise tiering. Built from HeyGen, Deel, Vercel, Supabase, Snowflake patterns.…
gr-b2b-growth
A guide to growing a business-to-business software product from early user research to large-scale sales. B2B software is sold to companies rather than individual consumers.
go-to-market-playbook
A reusable Go-to-Market strategy template for both B2B and B2C launches. Covers positioning, messaging, ICP definition, channel selection, and competitive analysis frameworks. By @WeiYipei.
support-tool-stack
Customer support platform selection, setup, and optimization — Intercom, Zendesk, Front, Help Scout, HubSpot Service Hub, Linear, and AI-native tools. Use when choosing a support platform, migrating tools, setting up help desk workflows, designing ticket routing, building macros and saved replies, or integrating…
co-founder-dynamics
Complete co-founder playbook for technical founders — finding co-founders, equity splits (dynamic and static), co-founder agreements, vesting schedules, working relationships, conflict resolution, co-founder breakups, and the "dating before marrying" framework. Use when looking for a co-founder, structuring a founding…
engineer-to-founder
Translate engineering strengths into founder-led GTM: customer discovery, positioning, demos, technical proof, founder sales habits, and first repeatable motion. Use when a technical founder needs to sell, do customer interviews, explain value without feature dumping, or build GTM confidence.