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/bmbouter/redhat-agents/quarter-planningnpx skills add bmbouter/redhat-agents --skill quarter-planninggit clone --depth 1 https://github.com/bmbouter/redhat-agentsWrote 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/bmbouter/redhat-agents/quarter-planning)<a href="https://agentmods.dev/skills/bmbouter/redhat-agents/quarter-planning"><img src="https://agentmods.dev/badge/skills/bmbouter/redhat-agents/quarter-planning.svg" alt="Measured on agentmods" 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.00026 | $0.00506 |
| Opus 5 | $0.00013 | $0.00253 |
| Sonnet 5 | $0.00005 | $0.00101 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
quarter-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 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.
What it actually says
When to Use
At the start of a planning cycle, typically before a quarter begins.
Instructions
Read local/jira-workflow.md to understand epic conventions, target date fields, and issue hierarchy.
1. Understand goals
Ask the PM:
- What quarter are we planning for? (dates)
- What are the top strategic goals or themes for this quarter?
- Are there any hard commitments or external deadlines?
- What capacity constraints should we consider? (team size, holidays, on-call rotation)
2. Review candidate epics
Query epics that could be planned:
- Existing epics without dates or with future dates
- Epics in New or In Progress status
project = <PROJECT> AND issuetype = Epic AND (status = New OR status = "In Progress") ORDER BY priority ASC
For each candidate, assess:
- Scope: How many sub-issues? Are they well-defined or still vague?
- Dependencies: Does this epic depend on another epic completing first?
- Readiness: Is the epic description complete? Are sub-issues filed?
- Effort estimate: Based on sub-issue count and complexity
3. Draft the quarter plan
## Q[N] Plan — <start date> to <end date>
### Strategic Goals
1. [Goal from PM input]
2. [...]
### Proposed Epics
| Priority | Epic | Scope | Target Start | Target End | Dependencies | Lead |
|----------|------|-------|-------------|-----------|--------------|------|
| 1 | EPIC-123 | 8 issues | <date> | <date> | None | @alice |
| 2 | EPIC-456 | 12 issues | <date> | <date> | After EPIC-123 | @bob |
### Capacity Notes
- [Any capacity constraints or conflicts]
### Risks
- [Dependency risks, scope uncertainty, etc.]
### Not This Quarter
| Epic | Reason |
|------|--------|
| EPIC-789 | Depends on EPIC-456 completing first |
| EPIC-012 | Low priority relative to goals |
Review with the PM. Once approved, offer to set target dates on the epics in Jira.
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 · 68 lines · 26 tokens per session scan A d99f95a56ea4
quarter-planning is a skill published in the GitHub repository bmbouter/redhat-agents (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 26 tokens to every session and 506 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…