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 uthumany/uthy-legacy-os --skill quarterly-planninggit clone --depth 1 https://github.com/uthumany/uthy-legacy-osWrote 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/uthumany/uthy-legacy-os/quarterly-planning)<a href="https://agentmods.dev/skills/uthumany/uthy-legacy-os/quarterly-planning"><img src="https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/quarterly-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/uthumany/uthy-legacy-os/quarterly-planning"><img src="https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/quarterly-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.00032 | $0.00876 |
| Opus 5 | $0.00016 | $0.00438 |
| Sonnet 5 | $0.00006 | $0.00175 |
| Haiku 4.5 | $0.00003 | $0.00088 |
Grade A, and why
quarterly-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 12d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quarterly Planning (1 Week)
Overview
Quarterly planning connects company objectives to product initiatives. It's about deciding what to focus on for the next 90 days, what to deprioritize, and how to measure success. This workflow runs at the end of each quarter.
When to Use
- At the end of each quarter to plan the next quarter's product work
- When company strategy or objectives have changed
- You need to align the product team around shared priorities
- Before budget or headcount planning sessions
- Don't use for: weekly or monthly planning (too heavy), firefighting or crisis management
Instructions
This workflow runs over 5 days at the end of the quarter. Each day has a specific focus. Do not skip days — the sequence builds from reflection to commitment.
- Start by reviewing the previous quarter's results (Day 1)
- Define objectives before identifying opportunities (Day 2 before Day 3)
- Only plan resources AFTER defining what you're doing (Day 4 after Day 3)
- Get buy-in before announcing (Day 5)
Day 1: Review & Reflect
- Review last quarter — Did we hit our objectives? What worked? What didn't? Load retrospective skill
- Review metrics — Load metrics-framework and north-star-metrics skills. Where are we vs. targets?
- Review competitive landscape — Load competitive-analysis skill. What changed in the market?
Output: Quarter review document with key learnings
Day 2: Define Objectives
- Company goals alignment — What are the company's priorities for next quarter?
- Product objectives — How does product support those goals? 1-3 objectives max
- Problem framing — Load problem-statement skill. What problems need solving?
Output: 1-3 product objectives for the quarter
Day 3: Identify Opportunities
- Opportunity mapping — Load opportunity-solution-tree skill. What opportunities serve our objectives?
- Prioritize opportunities — Rank by impact, confidence, and strategic fit
- Preliminary solutions — For top 2-3 opportunities, brainstorm solution directions
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.
- 12d ago First seen · 93 lines · 32 tokens per session scan A 2c62a57dd719
quarterly-planning is a skill published in the GitHub repository uthumany/uthy-legacy-os (5 stars, last pushed 3mo ago), licensed MIT. It adds 32 tokens to every session and 876 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.
remove
Remove a deployed framework or addon from the current workspace.