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 KonghaYao/peri --skill crongit clone --depth 1 https://github.com/KonghaYao/periWrote 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/konghayao/peri/cron)<a href="https://agentmods.dev/skills/konghayao/peri/cron"><img src="https://agentmods.dev/badge/skills/konghayao/peri/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/konghayao/peri/cron"><img src="https://agentmods.dev/badge/skills/konghayao/peri/cron.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
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 →
- high Tool Misuse · line 53 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00078 | $0.00918 |
| Opus 5.5 | $0.00031 | $0.00367 |
| Sonnet 5.5 | $0.00016 | $0.00184 |
| Haiku 4.5 | $0.00008 | $0.00092 |
Grade A, and why
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 12d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scheduled Tasks (Cron)
You have access to scheduled task tools (mcp__cron__cron_register, mcp__cron__cron_list, mcp__cron__cron_remove) for registering recurring automated tasks using standard 5-field cron expressions (minute hour day_of_month month day_of_week).
These three tools are deferred: they are not in your direct tool list. Discover them with SearchExtraTools (e.g. search for cron), then invoke them by their full name with ExecuteExtraTool.
When to Use
- The user asks for a recurring/periodic task: reminders, periodic reports, status checks, polling.
- The user asks to manage existing scheduled tasks (list, remove).
- The user's phrasing implies "every X", "每天/每周/每月", "at 9am daily", etc.
Do NOT register a cron task just because the user mentions a time — only when they explicitly want it to repeat automatically.
Tools
| Tool | Purpose |
|---|---|
mcp__cron__cron_register(expression, prompt) |
Register a new scheduled task. prompt is the user message submitted when the task fires. |
mcp__cron__cron_list() |
List all registered tasks with status, next fire time, and prompt. |
mcp__cron__cron_remove(id) |
Remove a task by its ID (shown by mcp__cron__cron_list). |
If SearchExtraTools returns no mcp__cron__* tool, the built-in cron instance is disabled for this session (MetaHarness CronMiddleware: false, the {"cron": {"disabled": true}} config entry, or PERI_MCP_BUILTIN=off); tell the user instead of trying to work around it.
Cron Expression Format
Standard 5-field cron expression:
minute hour day_of_month month day_of_week
Examples:
*/5 * * * *— every 5 minutes0 9 * * *— every day at 09:000 9 * * 1-5— weekdays at 09:0030 8 1 * *— the 1st of each month at 08:30
Use mcp__cron__cron_list to verify the registered task and its next fire time after registering.
Safety
mcp__cron__cron_register schedules future agent turns that fire without further user confirmation — treat it like delegating execution authority. Before registering:
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.
- 12d ago Changed · +7 lines · +10 tokens per session 52aefaf9432f
- 1mo ago First seen · 64 lines · 68 tokens per session scan A aebdb75d76f9
cron is a skill published in the GitHub repository KonghaYao/peri (244 stars, last pushed today), licensed Apache-2.0. It adds 78 tokens to every session and 918 once invoked, about $0.0003 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-30.
Other skills, from other repositories
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
plugin-creator
Create and scaffold plugin directories for Codex with a required .codex-plugin/plugin.json, optional plugin folders/files, valid manifest defaults, and personal-marketplace entries by default. Use when Codex needs to create a new personal plugin, add optional plugin structure, generate or update marketplace entries…
codex-pr-body
Update the title and body of one or more pull requests.
remote-tests
Testing against remote executors in integration tests.
update-v8-version
Update Codex's pinned v8 / rustyv8 versions, validate the release-candidate path, and investigate failed V8 canary or artifact builds. Use when asked to bump V8, update rustyv8 artifacts, prepare or validate a V8 release candidate, check v8-canary, or diagnose why a V8 version update no longer builds.
qa-testing
Verify your work by actually operating the app or website you changed, instead of assuming it works. Strongly recommended whenever you build, modify, or debug a web app, website, or desktop GUI app. Drive real browsers with the agent-browser CLI and native desktop apps with the cua-driver CLI. These are installed on…