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 skills add PinkPig97/codex-thread-cron --skill thread-crongit clone --depth 1 https://github.com/PinkPig97/codex-thread-cronWrote 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/pinkpig97/codex-thread-cron/thread-cron)<a href="https://agentmods.dev/skills/pinkpig97/codex-thread-cron/thread-cron"><img src="https://agentmods.dev/badge/skills/pinkpig97/codex-thread-cron/thread-cron/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/pinkpig97/codex-thread-cron/thread-cron"><img src="https://agentmods.dev/badge/skills/pinkpig97/codex-thread-cron/thread-cron.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.00021 | $0.00326 |
| Opus 5.5 | $0.00008 | $0.00130 |
| Sonnet 5.5 | $0.00004 | $0.00065 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
thread-cron 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 1mo 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.
What it actually says
Use this skill when the user wants recurring work inside the current Codex thread and the local Codex build already supports native cron_create, cron_list, and cron_delete.
Guardrails
- Prefer native thread cron over automation for recurring work in the current thread.
- Do not fall back to automation unless the user explicitly asks for automation.
- If native cron tools are unavailable, say so plainly and stop instead of inventing a workaround.
Workflow
- Normalize the task into three fields:
name,schedule, andprompt. - Prefer simple 5-field cron expressions that the current native parser supports.
- Keep prompts bounded, idempotent, and thread-local.
- After create, list, or delete, restate the exact schedule, prompt, or job id that was acted on.
Prompt Design Rules
- Start with a verb:
Review,Check,Summarize,Remind. - Keep scope narrow to one thread or one repository.
- Avoid prompts that assume hidden context from a different session.
- Prefer outputs that can be repeated safely without compounding side effects.
Schedule Rules
- Supported syntax is numeric 5-field cron with
*, lists, ranges, and steps. - Do not use aliases like
@daily. - Do not use month or weekday names like
JANorMON.
Read references/recipes.md when the user needs example schedules or prompt templates.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 35 lines · 21 tokens per session scan A 22f9f82d87c6
thread-cron is a skill published in the GitHub repository PinkPig97/codex-thread-cron (1 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 21 tokens to every session and 326 once invoked, about $0.0001 per session on Opus 5.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-31.
Other skills, from other repositories
subscription-manager
Create and manage scheduled subscription tasks. Use when the user wants to set up recurring reminders, periodic reports, scheduled checks, or any automated tasks that run on a schedule. Supports cron expressions, fixed intervals, and one-time executions.
agent-self-scheduling
Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers.
computer-use
Read and drive native desktop apps through the accessibility layer — list apps, snapshot a window as a numbered element tree, then click/type/scroll/drag by element index or screen coordinates. Use for a desktop app, not a web page. macOS + Windows; off unless enabled in Settings.
meetings
Context for the Meetings app's data — where a meeting's notes, diagram, transcript-derived tasks and calendar cache live, what the lifecycle states mean, how the app's agents are driven. Load when asked about a meeting's notes or action items, or when touching the meetings app data dir.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.
subscription-setup
A setup workflow for creating recurring medical-learning subscriptions after a doctor’s profile has been registered.