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 diillson/chatcli --skill remindersgit clone --depth 1 https://github.com/diillson/chatcliWrote 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/diillson/chatcli/reminders)<a href="https://agentmods.dev/skills/diillson/chatcli/reminders"><img src="https://agentmods.dev/badge/skills/diillson/chatcli/reminders/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/diillson/chatcli/reminders"><img src="https://agentmods.dev/badge/skills/diillson/chatcli/reminders.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 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.
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.00070 | $0.00920 |
| Opus 5.5 | $0.00028 | $0.00368 |
| Sonnet 5.5 | $0.00014 | $0.00184 |
| Haiku 4.5 | $0.00007 | $0.00092 |
Grade A, and why
reminders 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 2mo 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.
Reminders
Two distinct things hide behind "remind me" — pick the right one:
- A reminder/to-do in the user's reminders app (persists in their ecosystem, syncs to phone). Use native tooling.
- A timed nudge from ChatCLI itself — "ping me in 2h", "message me tomorrow at 9 to do X".
Use ChatCLI's built-in
@scheduler(+@sendto deliver), no external app needed. This is the self-contained path and works on every OS.
If the user is talking to ChatCLI over a gateway (Telegram/WhatsApp) and wants to be messaged, prefer path 2. If they want it in Apple/Google Reminders, use path 1.
Path 1 — Native reminders app (OS-specific)
ChatCLI is multi-OS — pick by platform:
- macOS → AppleScript
Reminders.app(no install):
List open items:osascript -e 'tell application "Reminders" to make new reminder with properties {name:"Call the dentist", due date:(date "2026-06-04 09:00")}'osascript -e 'tell application "Reminders" to get name of (reminders whose completed is false)' - Windows → a scheduled Toast reminder via PowerShell
ScheduledTasks, or simply use Path 2 (the ChatCLI scheduler) which is cleaner and OS-agnostic. Detect withGet-Command remind -ErrorAction SilentlyContinue. - Linux with
remind(1)installed (command -v remind) → append to~/.remindersand query withremind ~/.reminders. If nothing suitable is installed, fall back to Path 2.
When unsure what's installed, prefer Path 2 — it needs no external app and works identically on Windows, macOS, and Linux.
Path 2 — ChatCLI scheduler (timed nudge, any OS)
Schedule a job that fires later and delivers a message. Resolve "now" first if the delay is
relative — macOS / Linux: date '+%Y-%m-%d %H:%M %Z'; Windows:
Get-Date -Format "yyyy-MM-dd HH:mm zzz". Then use @scheduler to register the job, pairing it with @send so the reminder reaches the
user on their channel. Consult the @scheduler tool schema for the exact when/every/payload
fields (one-shot vs recurring), and confirm the resolved absolute time back to the user.
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.
- 2mo ago First seen · 71 lines · 70 tokens per session scan A 8093c00fd46c
reminders is a skill published in the GitHub repository diillson/chatcli (94 stars, last pushed yesterday), licensed Apache-2.0. It adds 70 tokens to every session and 920 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-09-03.
Other skills, from other repositories
12-cook
Manages project recipes and practical guides. Use when the user wants to find a recipe, document a technique, research improvements, follow an existing guide, or check that its steps are usable.
05-improve
Reads complete conversation evidence, measures visible cost, and recommends minimal improvements. Use when the user wants to improve a conversation, reduce wasted time or tokens, or choose files to revise. Not for delivery review or automatic edits.
09-for-sure
Run an iterative agent loop that retries until a runnable success condition passes. Use when the user says "for sure", "keep trying until", or wants guaranteed completion against a success command. Not for one-shot tasks or uncheckable goals.
claudeshrink
Automatically compress large natural text or log files before processing. Trigger when the user pastes massive text blobs, or asks to analyze a large file (logs, docs, transcripts), or provides a prompt that is too large for the context window. DO NOT trigger on source code files or structural data (JSON, XML).
agent-state-bar
A design guide for an agent status bar: a short, automatically updated summary of progress, remaining tasks, tool counts, errors, and system state placed near the latest model input.
reward-design
A guide to defining the scores that an AI agent receives during trial-and-error training. It covers checks based on rules, human preferences, or another model, and distinguishes rewarding the final result from rewarding the steps taken.