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 Peiiii/nextclaw --skill crongit clone --depth 1 https://github.com/Peiiii/nextclawWrote 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/peiiii/nextclaw/cron)<a href="https://agentmods.dev/skills/peiiii/nextclaw/cron"><img src="https://agentmods.dev/badge/skills/peiiii/nextclaw/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/peiiii/nextclaw/cron"><img src="https://agentmods.dev/badge/skills/peiiii/nextclaw/cron.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 Excessive Agency · line 16 Skill allows unbounded resource consumption (API calls, storage, compute). Without rate limits or quotas, a compromised or misbehaving agent can cause denial-of-service or cost overruns.Fix: Set explicit rate limits, timeouts, and resource quotas for API calls, file operations, and compute. Implement circuit breakers for runaway loops.
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.00008 | $0.00942 |
| Opus 5.5 | $0.00003 | $0.00377 |
| Sonnet 5.5 | $0.00002 | $0.00188 |
| Haiku 4.5 | $0.00001 | $0.00094 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cron
Use the cron tool to schedule reminders or recurring tasks.
cron is the only built-in automation scheduler. Do not refer users to Heartbeat or HEARTBEAT.md.
Before creating a job, decide whether the user wants a one-time action or a recurring action:
- Use
atfor one-time tasks such as "in 5 minutes", "at 6pm today", "tomorrow morning", or "only once". - Use
everyonly for true intervals that should repeat forever. - Use
crononly for repeating calendar schedules such as "every weekday at 9am".
When the user gives a relative time such as "in 1 minute", "5 minutes later", or "1分钟后", do not guess the base time.
- First check the current local time using an available tool, such as
execwithdate. - If the prompt already includes a current local time hint, you may use that hint instead of calling another tool.
- Then convert the relative time into an exact ISO datetime with timezone and pass that absolute value to
at.
When filling message, write the runtime instruction for the agent, not just the final outbound text fragment.
- Good:
At the scheduled time, send a WeChat message to the current chat saying: "会议还有 5 分钟开始。" - Bad:
会议还有 5 分钟开始。
If the user wants an exact message sent through WeChat or another channel, the instruction should explicitly say to send that exact text.
If the user wants the scheduled task to continue an existing conversation or explicitly provides a session id, pass it as sessionId. Omit sessionId when the task should use its own job-owned cron:<jobId> session.
If the user asks for a periodic follow-up, recurring check, or “continue this later” workflow, prefer binding the cron job to the existing sessionId instead of inventing a second automation mechanism.
If the user wants a periodic review of a file, workflow, inbox, or project board, express that directly in message.
- Good:
Read docs/TODO.md, check what changed since the last run, and summarize only actionable updates. - Good:
Continue the current release investigation, inspect the latest logs, and report only new blockers. - Bad:
heartbeat
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 · 91 lines · 8 tokens per session scan A 81e0314577e4
cron is a skill published in the GitHub repository Peiiii/nextclaw (262 stars, last pushed yesterday), licensed MIT. It adds 8 tokens to every session and 942 once invoked, about $0.0000 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
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…
session-done
Prepare a concise session handoff when the user asks to wrap up, capture continuation context, or use /done. Retain a Markdown file only when requested.
chief-of-staff
Act as the user's chief of staff, not a task-taker. Use for planning a day or week, triaging priorities, prepping for meetings or calls, drafting messages on the user's behalf, tracking commitments and follow-ups, reviewing what's in-flight, or any moment the user wants a trusted operator who knows their context.…
schedule
A skill for creating and managing scheduled tasks, including tasks that run automatically at regular times.
aetox-teach
สอนคนใช้ Aetox — ทำอะไรได้บ้างในคำที่คนเข้าใจ ห้องไหนไว้ทำอะไร ห้าอย่างที่คนใหม่ต้องรู้ และวิธีสอนด้วยการลงมือทำงานจริงของเขาแทนการบรรยาย · อ่านเมื่อผู้ใช้ถามว่าแอปนี้ทำอะไรได้ ถามวิธีใช้ หรือเพิ่งเปิดครั้งแรก.