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/runbear-io/aweek/plannpx skills add runbear-io/aweek --skill plangit clone --depth 1 https://github.com/runbear-io/aweekWrote 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/runbear-io/aweek/plan)<a href="https://agentmods.dev/skills/runbear-io/aweek/plan"><img src="https://agentmods.dev/badge/skills/runbear-io/aweek/plan.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 | $0.00019 | $0.04276 |
| Opus 5 | $0.00010 | $0.02138 |
| Sonnet 5 | $0.00004 | $0.00855 |
| Haiku 4.5 | $0.00002 | $0.00428 |
Grade A, and why
plan 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 4d 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 — 306 lines — stays where its author put it; the contents beside it link to each section on GitHub.
aweek:plan
Single entry point for every planning operation on an aweek agent:
- Edit the agent's free-form planning markdown (long-term goals, monthly plans, strategies, notes) at
.aweek/agents/<slug>/plan.md. - Adjust weekly tasks (create / add / update) on the in-flight week.
The planning markdown is the source of truth for long-term intent. It is intentionally free-form — the weekly generator reads it as context rather than enforcing a schema. If you find yourself wanting a structured field that plan.md can't express, add it as prose; the model will pick it up.
Plans are always active. There is no approval gate — every weekly plan is immediately eligible for the heartbeat the moment it lands on disk. Adjustments take effect on the next tick.
Weekly plan logic lives in src/skills/plan.ts, composed over the services in src/services/plan-adjustments.ts. Markdown logic lives in src/storage/plan-markdown-store.ts. Never write agent JSON or the plan file directly — always go through the skill module or the plan-markdown dispatcher.
Instructions
Follow this exact workflow when invoked. Use AskUserQuestion for every interactive prompt.
Step 1: Select an Agent
List all agents:
echo '{"dataDir":".aweek/agents"}' \
| aweek exec agent-helpers listAllAgents --input-json -
Response is an array of { config } records. Render a numbered list using agent name and role, then ask the user to pick one via AskUserQuestion.
If the list is empty, tell the user "No agents found. Use /aweek:hire to create one first." and stop.
Step 2: Choose an Operation
Ask via AskUserQuestion:
- Edit planning markdown — open / show / replace the agent's
plan.md. - Adjust weekly plan — create a weekly plan, add tasks, update task status, etc.
- Done
Route to the matching branch. After each branch finishes, loop back to Step 2 until the user picks Done.
Branch A: Edit planning markdown
The markdown file is a free-form authoring surface. Its H2 conventions (Long-term goals / Monthly plans / Strategies / Notes) are a template, not a schema — the user can restructure freely.
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.
- 4d ago First seen · 306 lines · 19 tokens per session scan A 8d60f50fb836
plan is a skill published in the GitHub repository runbear-io/aweek (11 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 4,276 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…