Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/DavidROliverBA/ArchitectKBnpx agentmods add skills/davidroliverba/architectkb/scheduleWrote 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/davidroliverba/architectkb/schedule)<a href="https://agentmods.dev/skills/davidroliverba/architectkb/schedule"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/schedule/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/davidroliverba/architectkb/schedule"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/schedule.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00009 | $0.01966 |
| Opus 5 | $0.00005 | $0.00983 |
| Sonnet 5 | $0.00002 | $0.00393 |
| Haiku 4.5 | $0.00001 | $0.00197 |
Grade A, and why
schedule 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 9d 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 — 288 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/schedule
Schedule recurring vault maintenance tasks using macOS launchd (or cron on Linux).
Usage
/schedule list # List scheduled jobs
/schedule add <job> <schedule> # Add a scheduled job
/schedule remove <job> # Remove a scheduled job
/schedule run <job> # Run job immediately
/schedule status # Show job status and last run times
Examples
/schedule list
/schedule add health-check daily
/schedule add graph-rebuild hourly
/schedule add validate weekly
/schedule remove health-check
/schedule status
Available Jobs
| Job | Description | Default Schedule |
|---|---|---|
health-check |
Run vault health check (scripts/health-check.js) | Daily at 6am |
validate |
Run frontmatter/link validation (scripts/validate.js) | Weekly on Monday |
graph-rebuild |
Rebuild knowledge graph index (scripts/generate-graph-enhanced.js) | Hourly |
vault-index |
Rebuild SQLite FTS5 search index (scripts/vault-to-sqlite.js) | Daily at 5am |
backup |
Git commit and push vault changes | Daily at midnight |
weblink-check |
Check for dead weblinks | Weekly on Sunday |
custom |
User-defined command | As specified |
Schedule Formats
| Format | Description | Example |
|---|---|---|
hourly |
Every hour at :00 | hourly |
daily |
Every day at 6:00 AM | daily |
daily@HH:MM |
Every day at specific time | daily@09:30 |
weekly |
Every Monday at 6:00 AM | weekly |
weekly@DAY |
Specific day at 6:00 AM | weekly@friday |
cron EXPR |
Cron expression (5 fields) | cron 0 */4 * * * |
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.
- 9d ago First seen · 288 lines · 9 tokens per session scan A 7bf2c4544e6e
schedule is a skill published in the GitHub repository DavidROliverBA/ArchitectKB (52 stars, last pushed 6mo ago), licensed MIT. It adds 9 tokens to every session and 1,966 once invoked, about $0.0000 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-09-03.
Other skills, from other repositories
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
agentmail
Use your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by your inbox assignment.
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.