A setup guide for recurring Claude Code tasks, such as weekly digests or periodic checks. Scheduled tasks run at set times without being started manually.

It is for creating schedules for pattern digests, question digests, stale-guidance checks, lead updates, and maturity checks.

It turns repeated reminders and reviews into scheduled work instead of relying on someone to start them each time.

routines — Skill for Claude Code by thevibeworks/claude-code-docs

Install

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.

Any agent

npx skills add thevibeworks/claude-code-docs --skill routines

Clone the repo

git clone --depth 1 https://github.com/thevibeworks/claude-code-docs

Made for: Claude Code.

Or install champion-kit, the plugin that ships this one along with the rest of its 7 skills, 1 agent.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/thevibeworks/claude-code-docs/routines/github.svg)](https://agentmods.dev/skills/thevibeworks/claude-code-docs/routines)

Your own site

<a href="https://agentmods.dev/skills/thevibeworks/claude-code-docs/routines"><img src="https://agentmods.dev/badge/skills/thevibeworks/claude-code-docs/routines/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/thevibeworks/claude-code-docs/routines"><img src="https://agentmods.dev/badge/skills/thevibeworks/claude-code-docs/routines.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,937 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 100% copy Near-identical to another mod in the catalogue.

Token cost

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.00045	$0.01937
Opus 5.5	$0.00018	$0.00775
Sonnet 5.5	$0.00009	$0.00387
Haiku 4.5	$0.00005	$0.00194

Measured today against content hash 98de31ba1a08, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

routines 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 today.

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.

Origin

This is a copy

100% identical to routines — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

content/github/claude-plugins-official/plugins/champion-kit/skills/routines/SKILL.md · 57 lines

How it starts

The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Start here

Say in one line what you'll make: a ready-to-paste /schedule line for each routine you pick, adapted to this repo.

What the champion typed after the command, if anything: $ARGUMENTS

If that's blank, run the guided flow below. If it has text, or they already told you some of this, use what it answers and ask only for what's still missing.

Before asking, say that /schedule needs a claude.ai login, isn't available with an API key or through a cloud provider, and can be turned off by an org. Note this folder's name so the lines can name the repo.

Then ask:

Which routines? Use AskUserQuestion with two questions in one call, each letting them pick more than one. Weekly: "Weekly patterns digest" (recommended) and "Weekly question digest". Monthly or quarterly: "Stale guidance check" (recommended), "Monthly lead update", and "Quarterly maturity check".
What's your timezone, and do you want a time of day? A plain question. The default is no set time.
Only if they picked the question digest: which issue tracker should it read? A plain question.

How to ask: one question at a time, or a small batch of related choices, and wait for the answer before you go on. When the answer is one of a few options, use the AskUserQuestion tool with up to four options, the recommended or most common one first. If AskUserQuestion isn't available, give the same options as a short numbered list and wait for the answer. Ask a plain question only when the answer is open, such as a goal or team names, and suggest a default. When a question asks how someone works or what score fits, mark no option as recommended. A consent question, about reading through git, gh, chat, or a connector, or about writing a file, puts the safe choice, such as "Not yet", first as the recommended one. A pick counts as a yes only for the exact read or write it names. If the champion says "go", list the defaults you'll take for the remaining questions, then take them, but still stop at every consent question. A default never counts as a yes.

Read the full file on GitHub · 57 lines

Changes

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.

today First seen · 57 lines · 45 tokens per session scan A 98de31ba1a08

Subscribe to this mod's changes

routines is a skill published in the GitHub repository thevibeworks/claude-code-docs (170 stars, last pushed today), licensed MIT. It adds 45 tokens to every session and 1,937 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to routines, differing in 0 lines, and is treated as a copy.

Project management agent-sdk ai-agents anthropic claude documentation

routines next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
routinesthevibeworks/claude-code-docs	Skill	170	today	MIT	A	45	Claude Code
synccortex-tms/cortex-tms	Skill	180	5d ago	MIT	A	40	Claude Code
validatecortex-tms/cortex-tms	Skill	180	5d ago	MIT	A	22	Claude Code
atlas-reporttonone-ai/tonone	Skill	77	24d ago	MIT	A	44	Claude Code
vibing-orchestrateshabaraba/vibing.nvim	Skill	13	yesterday	MIT	A	76	Claude Code
adding-config-fieldsdork-labs/dorkos	Skill	11	today	MIT	A	61	Claude Code
visual-companiondork-labs/dorkos	Skill	11	today	MIT	A	36	Claude Code