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 PsychQuant/che-ical-mcp --skill archive-eventgit clone --depth 1 https://github.com/PsychQuant/che-ical-mcpWrote 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/psychquant/che-ical-mcp/archive-event)<a href="https://agentmods.dev/skills/psychquant/che-ical-mcp/archive-event"><img src="https://agentmods.dev/badge/skills/psychquant/che-ical-mcp/archive-event/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/psychquant/che-ical-mcp/archive-event"><img src="https://agentmods.dev/badge/skills/psychquant/che-ical-mcp/archive-event.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 213 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00000 | $0.02943 |
| Opus 5 | $0.00000 | $0.01471 |
| Sonnet 5 | $0.00000 | $0.00589 |
| Haiku 4.5 | $0.00000 | $0.00294 |
Grade A, and why
archive-event 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 8d 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 — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Archive an event from a source
Turning "here is the notice" into a calendar entry requires judgements the 29 EventKit tools will never prompt for. Two of those judgements fail silently — the event is created, the calendar looks normal, and the content is wrong:
- The time was superseded. A notice goes out, then the organizer corrects it. Reading only the first message puts the wrong day in the calendar.
- An estimated value reads as a stated fact. Notices often omit the end time. An estimate that is not labelled is indistinguishable, later, from something the source actually said.
Failures that raise an error can live in a README — the reader will look it up. Silent failures cannot, because nobody knows to look. That is what this skill is for.
What already exists — do not rebuild it
| Mechanism | Covers | Does not cover |
|---|---|---|
quick-event command |
parse → list calendars → conflict check → create | source derivation, correction tracking, evidence |
create_event built-in idempotency |
same-calendar repeat of (title, start ±30s) | the same activity after its start time changed |
find_duplicate_events tool |
duplicates across calendars | within one calendar (it skips same-calendar pairs by design) |
calendar-management skill |
tool catalogue and common workflows | the judgements below |
Conflict checking exists as a tool — this skill still invokes check_conflicts itself before any create (it does not go through quick-event, so it inherits nothing). What it adds are the five judgements that no existing mechanism covers.
Procedure
source ──▶ 1. authoritative time ──▶ 4. which calendar ──▶ 3. compose notes
│
2. update or create ◀───────────┘
（check_conflicts before create）
│
└──▶ 5. same-day deadlines
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.
- 8d ago First seen · 247 lines · 0 tokens per session scan A 41a6266af3dd
archive-event is a skill published in the GitHub repository PsychQuant/che-ical-mcp (36 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,943 tokens. 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
apple-pim
Native macOS personal information management for calendars, reminders, contacts, and local Mail.app. Use when the user wants to schedule meetings, create events, check their calendar, create or complete reminders, look up contacts, find someone's phone number or email, manage tasks and to-do lists, triage local…
apple-calendar-cli
You have access to apple-calendar-cli, a command-line tool for managing Apple Calendar events via EventKit on macOS.
rem-cli
Create, list, update, complete, tag, and search macOS Reminders via the rem CLI. Use when the user wants to manage Apple Reminders from the terminal, automate reminder workflows, reference reminders in shell scripts, or schedule anything on macOS.
confirmation-protocol
Foresay-derived confirmation workflow for email operations. Use this skill BEFORE executing archive-mail with vague filters, composeemail (sending mail), deleteemail/moveemail in bulk, or any operation that touches 5+ emails. Show user a structured preview of "what I understood" before taking action, achieving…
bulk-operation-preview
Show structured preview of bulk email operations (5+ emails) before execute. Group by thread, flag false-positive candidates, count side-effect scope (files written, attachments downloaded, mailboxes touched). Use after email-search-disambiguation finishes Phase 1, as Phase 2 of the confirmation protocol.
email-search-disambiguation
A clarification step for email searches when a person, time period, direction, or scope is unclear. It presents specific possible meanings so the user can choose one.