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/confignpx skills add runbear-io/aweek --skill configgit 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/config)<a href="https://agentmods.dev/skills/runbear-io/aweek/config"><img src="https://agentmods.dev/badge/skills/runbear-io/aweek/config.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.00035 | $0.03289 |
| Opus 5 | $0.00017 | $0.01644 |
| Sonnet 5 | $0.00007 | $0.00658 |
| Haiku 4.5 | $0.00003 | $0.00329 |
Grade A, and why
config 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 — 361 lines — stays where its author put it; the contents beside it link to each section on GitHub.
aweek:config
CLI counterpart to the dashboard's Settings page. Use this skill any time the
user wants to inspect or change values in .aweek/config.json. The
skill renders the same knobs the Settings page does (time zone, stale task
window, plus the hardcoded heartbeat / lock constants) and provides a
destructive-write gate around any field that's actually editable.
Today the editable fields are timeZone, staleTaskWindowMs,
heartbeatIntervalSec, and runner. Lock directory and max lock age are
intentionally not surfaced — those are implementation details of
src/lock/lock-manager.ts.
runner selects the coding-agent CLI the heartbeat uses to run agent
tasks: claude (Claude Code, the default), gemini (Gemini CLI), or
hermes (Hermes Agent). It is the project-wide default; an individual
agent can override it via its own runner field in
.aweek/agents/<slug>.json. Under the heartbeat both gemini and
hermes run in no-permission (yolo) mode. Switching requires that CLI on
PATH with its own auth configured (gemini: GEMINI_API_KEY / OAuth;
hermes: hermes setup) — aweek does not manage their credentials. Note
that hermes one-shot runs report no token usage, so weekly-budget
accounting is skipped for Hermes agents.
heartbeatIntervalSec is config-backed AND the skill auto-rotates the
live launchd plist (or crontab line) in the same flow as the config
write. The user-facing experience is: pick the new value, see both the
config diff and the plist update reported back. See Step 3a for the
auto-rotation contract — the skill calls installHeartbeat with
confirmed: true without re-prompting because the value-picker in
Step 3 is already the deliberate user input.
Adding a new editable field means extending AweekConfig in
src/storage/config-store.ts, its saveConfig validator, and the
listEditableFields registry in src/skills/config.ts — the SKILL flow
below picks up the new entry without further changes.
Instructions
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 · 361 lines · 35 tokens per session scan A 1f9c3efaf1f9
config is a skill published in the GitHub repository runbear-io/aweek (11 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 35 tokens to every session and 3,289 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
timeline-creator
Create HTML timelines and project roadmaps with Gantt charts, milestones, phase groupings, and progress indicators. Use when users request timelines, roadmaps, Gantt charts, project schedules, or milestone visualizations.
bootstrap-prd
Set up PRD-driven development infrastructure for a new project, including directory structure, templates, and roadmap.
glab-issue
Create, view, update, and manage GitLab issues. Use when working with issue tracking, bug reports, feature requests, or task management. Operations include creating issues, listing with filters, viewing details, adding comments/notes, updating labels/assignees/milestones, closing/reopening, and board management.…
sales-ops
Set up and run Airtable-based sales operations and CRM workflows — pipeline management, account and renewal management, deal desk, RFP / tender pipelines, partner CRMs, sales forecasting, vertical CRMs (real estate, mortgage, brokerage, capital markets, public works, nonprofit), and AI-native lean stacks…
jira
Search and manage Jira issues using JQL queries, create/update tickets, and manage workflows. Use when asked to find Jira tickets, check the backlog, manage sprints, track bugs, or work with Atlassian project management.
github
Use this skill when Enoch needs to coordinate work with GitHub: branches, pull requests, issues, reviews, comments, checks, and merges.