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/agentproto/ts/ap-cronnpx skills add agentproto/ts --skill ap-crongit clone --depth 1 https://github.com/agentproto/tsWrote 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/agentproto/ts/ap-cron)<a href="https://agentmods.dev/skills/agentproto/ts/ap-cron"><img src="https://agentmods.dev/badge/skills/agentproto/ts/ap-cron.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.00070 | $0.00947 |
| Opus 5 | $0.00035 | $0.00474 |
| Sonnet 5 | $0.00014 | $0.00189 |
| Haiku 4.5 | $0.00007 | $0.00095 |
Grade A, and why
ap-cron scanned grade A with 1 finding 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
"action": { "kind": "command", "command": "curl", "args": ["-fsS", "http://localhost:8080/health"], "cwd": ".", "timeoutMs": 15000 } How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ap-cron
When to use
- Work must run on a schedule with nobody prompting it (nightly audits, periodic sweeps).
- A long-running mission needs periodic check-ins that keep its context alive.
- You want a delayed one-shot action ("in 20 minutes, poke the deploy").
Create a job
cron_create takes a 5-field cron expression in local time and exactly one action. label is the human-readable name; recurring defaults to true.
{
"schedule": "0 9 * * 1-5",
"label": "morning-standup",
"action": {
"kind": "agent",
"adapter": "claude-code",
"prompt": "Summarize overnight commits and draft the day's priority list.",
"cwd": "/repo",
"model": "claude-sonnet-4-5"
}
}
Three action kinds:
- command — run an allowlisted executable.
commandis the basename (git, not/usr/bin/git) and must be listed in<workspace>/.agentproto/allowed-commands.json.
{
"schedule": "*/30 * * * *",
"label": "health-check",
"action": { "kind": "command", "command": "curl", "args": ["-fsS", "http://localhost:8080/health"], "cwd": ".", "timeoutMs": 15000 }
}
- agent — spawn a brand-new session on each firing. Use for self-contained periodic work.
- prompt-session — re-ping an EXISTING living session by id.
{
"schedule": "0 8,14,20 * * *",
"label": "mission-checkin",
"action": { "kind": "prompt-session", "sessionId": "sess_abc123", "prompt": "Check-in: post progress, blockers, and next step." }
}
Inspect, test, delete
cron_list({}) // every job, active + inactive, with schedule, lastResult, nextRunAt
cron_run({ "jobId": "job_01J..." }) // fire NOW, bypassing the schedule — the test path
cron_delete({ "jobId": "job_01J..." }) // permanent removal
After creating a job, call cron_run once and read lastResult from cron_list before trusting the schedule. A fired cron does not notify you — lastResult is the only feedback.
Durable check-ins on a long mission
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.
- yesterday First seen · 84 lines · 70 tokens per session scan A 848843c1341d
ap-cron is a skill published in the GitHub repository agentproto/ts (5 stars, last pushed today), licensed Apache-2.0. It adds 70 tokens to every session and 947 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.
Other skills, from other repositories
markedit-tools
Provides tools for managing MarkEdit, a macOS markdown editor.
differed-task-execution
Delays execution of a task until a specified time or after a duration. Use when the user asks to run something later, in X minutes/hours, at a specific time, schedule a command, or defer work to a future point.
herdr
Control Herdr, a terminal multiplexer for coding agents. Use only when the user explicitly asks to you use or configure Herdr.
strands-review
Local preview of the strands-agents/devtools /strands review agent. Body is the upstream Task Reviewer SOP verbatim — do not paraphrase. Use when the user types /strands-review, asks for a "strands review" of a PR, or wants to anticipate what the remote /strands review GitHub Action will flag. Findings are close but…
docs-reviewer
Review documentation drafts for voice consistency, structure, and terminology before PR submission. Use after completing a draft, when checking if docs are ready to ship, or automatically after docs-writer produces output. Also triggers on "review this draft", "check my docs", "is this ready to ship", "review before…
docs-writer
Draft or rewrite Strands Agents documentation pages. Use when writing new doc pages, rewriting pages that failed audit, drafting sections for existing pages, or writing blog posts and release notes about Strands. Also triggers on "write a doc", "draft a page", "rewrite the quickstart", "add a tutorial for X"…