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 ShreyPaharia/octomux --skill plan-weekgit clone --depth 1 https://github.com/ShreyPaharia/octomuxWrote 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/shreypaharia/octomux/plan-week)<a href="https://agentmods.dev/skills/shreypaharia/octomux/plan-week"><img src="https://agentmods.dev/badge/skills/shreypaharia/octomux/plan-week/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/shreypaharia/octomux/plan-week"><img src="https://agentmods.dev/badge/skills/shreypaharia/octomux/plan-week.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.00039 | $0.01544 |
| Opus 5 | $0.00019 | $0.00772 |
| Sonnet 5 | $0.00008 | $0.00309 |
| Haiku 4.5 | $0.00004 | $0.00154 |
Grade A, and why
plan-week 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 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.
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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Weekly Planning
Interview the user about what they want to accomplish, break it into well-scoped Jira tickets, get approval, then create them in Jira.
Checklist
- Fetch context — current sprint, open tickets, recent work
- Interview — understand goals, one question at a time
- Propose ticket list — table with title, type, estimate, epic
- Single approval gate — user approves, drops, or adjusts
- Create tickets in Jira — with description, acceptance criteria, epic, sprint, assignee
- Report — links to all created tickets
Jira Authentication
Before any Jira call, test connectivity by calling getAccessibleAtlassianResources(). If it fails or returns an auth error, stop and prompt the user:
"Jira is not authenticated. Please run
/pluginand authenticate the Atlassian plugin, then try again."
Do not proceed with Jira operations until auth is confirmed.
Phase 1: Fetch Context
Before the interview, silently gather context so you can ask informed questions.
1a. Get Jira cloud ID (also serves as auth check):
getAccessibleAtlassianResources() -> extract cloudId for ostium-defi.atlassian.net
If this fails, follow the Jira Authentication section above.
1b. Get current sprint and open tickets (parallel):
searchJiraIssuesUsingJql(cloudId, "project = "IN" AND assignee = currentUser() AND status != Done ORDER BY priority DESC", fields=["summary","status","priority","issuetype","sprint","parent"])
1c. Get user's Jira account ID:
atlassianUserInfo() -> extract accountId
1d. Check recent git work:
git log --all --oneline --since="1 week ago" --author="Shrey" | head -20
Keep this context in mind but don't dump it on the user. Use it to ask better questions and avoid duplicating existing tickets.
Phase 2: Interview
Start with a single open question:
"What do you want to accomplish this week? List the big things — features, bugs, chores, anything."
Then follow up one question at a time to clarify:
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 · 188 lines · 39 tokens per session scan A 97ac1fbfbede
plan-week is a skill published in the GitHub repository ShreyPaharia/octomux (22 stars, last pushed 10d ago), licensed MIT. It adds 39 tokens to every session and 1,544 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-30.
Other skills, from other repositories
claude-code-expert
Especialista profundo em Claude Code - CLI da Anthropic. Maximiza produtividade com atalhos, hooks, MCPs, configuracoes avancadas, workflows, CLAUDE.md, memoria, sub-agentes, permissoes e integracao com ecossistemas.
cal-com-automation
Automate Cal.com tasks via Rube MCP (Composio): manage bookings, check availability, configure webhooks, and handle teams. Always search tools first for current schemas.
coda-automation
Automate Coda tasks via Rube MCP (Composio): manage docs, pages, tables, rows, formulas, permissions, and publishing. Always search tools first for current schemas.
close-automation
Automate Close CRM tasks via Rube MCP (Composio): create leads, manage calls/SMS, handle tasks, and track notes. Always search tools first for current schemas.
workspace-explorer
Explore and navigate Notion workspaces via MCP. Use when searching for pages, understanding database structure, finding content, creating or updating pages/databases, or managing Notion workspace content. Triggers when user asks about Notion, mentions Notion pages/databases, wants to find something in their wiki…
spell-schedule
Schedule a moflo spell to run on the local machine via the moflo daemon (cron, interval, or one-time). Use when the user wants to schedule, automate, or recurringly run one of THEIR spells locally — e.g. "schedule the oap spell every hour", "run my audit spell every weekday at 9am", "fire X once tomorrow morning".…