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 open-octo/octo-agent --skill cron-task-creatorgit clone --depth 1 https://github.com/open-octo/octo-agentWrote 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/open-octo/octo-agent/cron-task-creator)<a href="https://agentmods.dev/skills/open-octo/octo-agent/cron-task-creator"><img src="https://agentmods.dev/badge/skills/open-octo/octo-agent/cron-task-creator/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/open-octo/octo-agent/cron-task-creator"><img src="https://agentmods.dev/badge/skills/open-octo/octo-agent/cron-task-creator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 3 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 6 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 69 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Data Exfiltration · line 94 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00089 | $0.03085 |
| Opus 5.5 | $0.00036 | $0.01234 |
| Sonnet 5.5 | $0.00018 | $0.00617 |
| Haiku 4.5 | $0.00009 | $0.00309 |
Grade A, and why
cron-task-creator 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 11d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -X POST http://127.0.0.1:8088/api/tasks \ How it starts
The opening of the file, as written. The whole thing — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create and manage octo cron tasks
octo runs an agent prompt on a schedule. Each task is a JSON file in
~/.octo/tasks/, loaded by the scheduler inside octo serve. When a task
fires, the scheduler runs one agent turn with the task's prompt in a fresh
session — a run never sees an earlier run's transcript. What's worth keeping
across runs goes in long-term memory: each task has its own project, and with
it its own working directory and memory directory, so a note one run saves is
in the next run's memory block.
Each run is bounded by a 30-minute wall-clock timeout (the only hard cap on
a run).
Task schema
| Field | Required | Meaning |
|---|---|---|
name |
yes | Human-readable task name |
cron |
yes | Schedule expression — see format below |
prompt |
yes | The prompt sent to the agent on each run |
model |
no | Model override; defaults to the server's model |
agent_id |
no | Id of the expert (/api/agents) the run executes as; empty = the Default Agent |
directory |
no | Working directory the run executes in |
notify |
no | IM chats to push each run's final reply (or failure) to — see the notify table |
permission_mode |
yes | auto (tool calls that would need approval are allowed) or strict (they are denied); deny rules apply either way. interactive is rejected — a run has nobody to answer an approval |
enabled |
yes | Whether the schedule is active |
id, created_at, last_run, session_id, session_group_id are
server-managed — never set them by hand except id in the file-write fallback
below.
Every run creates a fresh session (titled by the run's local date and time) and files it under a per-task session group named after the task, so a task's runs cluster together in the sidebar. The group is created with the task and renamed/deleted along with it. Runs never share a session — each starts from a clean transcript.
Cron expression — 6 fields, seconds first
The scheduler uses robfig/cron with a seconds field. A standard 5-field crontab line is invalid — always prepend a seconds field:
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.
- 11d ago Changed · +8 lines b5892dc7c4b7
- 29d ago Changed · +1 lines 7fe78311fee2
- 1mo ago Changed · +56 lines 9e6f638176c8
- 1mo ago First seen · 163 lines · 89 tokens per session scan A bde60e603cb1
cron-task-creator is a skill published in the GitHub repository open-octo/octo-agent (136 stars, last pushed 2d ago), licensed MIT. It adds 89 tokens to every session and 3,085 once invoked, about $0.0004 per session on Opus 5.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-08-30.
Other skills, from other repositories
meeting-notes
Use when the user asks to capture, structure, or summarize meeting notes / call notes / 1:1 discussion / standup notes. Produces a standard template with attendees, agenda, decisions, action items (owner + deadline), and open questions.
ha-settings
Manage Hope Agent application settings through conversation. Use when the user wants to view or change any app configuration: theme, language, enhanced focus indicators, proxy, temperature, notifications, tool timeout, context compaction, automatic session titles, web search, GitHub issue reporting, memory, embedding…
tg-moderator
Telegram chat moderator/companion mode. No tools, conversational only.
telegram-workflow
Rules for using a personal Telegram account through claudegram, a connection that works as the account owner rather than as a bot. It covers reading chats, searching messages, drafting replies, and managing conversations and groups.
apple-reminders
Apple Reminders via remindctl: add, list, complete.
tg-digest
A Telegram unread-message digest that groups missed messages by chat and summarizes them in Russian. Telegram is a messaging service with individual and group chats.