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/managenpx skills add runbear-io/aweek --skill managegit 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/manage)<a href="https://agentmods.dev/skills/runbear-io/aweek/manage"><img src="https://agentmods.dev/badge/skills/runbear-io/aweek/manage.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.00024 | $0.02334 |
| Opus 5 | $0.00012 | $0.01167 |
| Sonnet 5 | $0.00005 | $0.00467 |
| Haiku 4.5 | $0.00002 | $0.00233 |
Grade A, and why
manage 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.
How it starts
The opening of the file, as written. The whole thing — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.
aweek:manage
Manage the lifecycle of an existing aweek agent. This skill is the consolidated replacement for /aweek:resume-agent — it covers every post-hire lifecycle operation through a single interactive entry point:
- Resume a budget-paused agent (clear the
budget.pausedflag) - Top-up a paused agent (reset weekly usage to 0, optionally change the budget limit) — destructive
- Pause / stop an active agent (set
budget.pausedso the heartbeat skips it) - Delete / archive — permanently remove the agent config file — destructive
Identity fields (name, description, system prompt) live in
.claude/agents/<slug>.md and are edited directly on that file — aweek
does not own them.
The skill is a thin UX wrapper on top of src/skills/manage.js, which re-exports the canonical resume pipeline from src/skills/resume-agent.js and adds pause/delete operations. Do not edit agent JSON files directly — always go through the Node modules so schema validation and updatedAt timestamps stay correct.
Destructive operation policy
Per project policy, every destructive lifecycle operation requires explicit user confirmation before the change is written to disk. The confirmation gate lives inside the src/skills/manage.js adapter, but the skill must still present a clear preview and collect an AskUserQuestion confirmation before setting confirmed: true.
| Operation | Destructive | Confirmation required |
|---|---|---|
resume |
No | No |
top-up |
Yes (usage counter reset, optional limit change) | Yes |
pause |
No (reversible) | No |
delete |
Yes (file removed from disk, irreversible) | Yes |
Never pass confirmed: true without collecting explicit confirmation via AskUserQuestion.
Instructions
You MUST follow this exact workflow when this skill is invoked. Use the Node.js modules in src/skills/manage.js for every read and write.
Step 1: Pick a lifecycle action
Ask the user which lifecycle operation they want to perform using AskUserQuestion. Offer the options:
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 · 256 lines · 24 tokens per session scan A 341aa18867ba
manage is a skill published in the GitHub repository runbear-io/aweek (11 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 24 tokens to every session and 2,334 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.
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…