calendar-conflicts

calendar-conflicts is a skill for Claude Code from aashari/ai-agent-skills. It costs 31 tokens per session (1,036 once invoked), scanned A, original, MIT.

A calendar tool that finds timed events which overlap. It ignores all-day events because they do not occupy a specific time slot.

In plain words
What is it for?
Use it to check for overlapping events today, this week, over a chosen number of days, or on a specific date.
Why use it?
It helps reveal double-booked meetings and other scheduling conflicts that are easy to miss when looking through a calendar manually.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: built for openclaw.

Good fit Use it to check for overlapping events today, this week, over a chosen number of days, or on a specific date.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/aashari/ai-agent-skills/calendar-conflicts
Install

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.

Any agent
npx skills add aashari/ai-agent-skills --skill calendar-conflicts
Clone the repo
git clone --depth 1 https://github.com/aashari/ai-agent-skills

Made for: Claude Code.

Wrote 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.

agentmods badge for calendar-conflicts

README.md
[![agentmods](https://agentmods.dev/badge/skills/aashari/ai-agent-skills/calendar-conflicts/github.svg)](https://agentmods.dev/skills/aashari/ai-agent-skills/calendar-conflicts)
Your own site
<a href="https://agentmods.dev/skills/aashari/ai-agent-skills/calendar-conflicts"><img src="https://agentmods.dev/badge/skills/aashari/ai-agent-skills/calendar-conflicts/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.

agentmods 80×15 button for calendar-conflicts

Your own site · 80×15
<a href="https://agentmods.dev/skills/aashari/ai-agent-skills/calendar-conflicts"><img src="https://agentmods.dev/badge/skills/aashari/ai-agent-skills/calendar-conflicts.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,036 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00031 $0.01036
Opus 5 $0.00015 $0.00518
Sonnet 5 $0.00006 $0.00207
Haiku 4.5 $0.00003 $0.00104

Measured 10d ago against content hash 51bb9fc198b9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

calendar-conflicts 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 10d 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.

skills/apple-calendar/calendar-conflicts/SKILL.md · 104 lines

How it starts

The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Calendar Conflicts — Find Overlapping Events

Detect time-overlapping events (double-bookings). All-day events are excluded since they don't block time slots.

Arguments

$ARGUMENTS — time range (default: next 7 days):

  • "today", "this week", "next 14 days"
  • "2026-03-01" → specific date
  • Empty → next 7 days

Steps

DB="$HOME/Library/Group Containers/group.com.apple.calendar/Calendar.sqlitedb"
ARGS="$ARGUMENTS"

DAYS=7
if echo "$ARGS" | grep -qiE '[0-9]+ day'; then DAYS=$(echo "$ARGS" | grep -oiE '[0-9]+'); fi
if echo "$ARGS" | grep -qi 'week'; then DAYS=7; fi
if echo "$ARGS" | grep -qi 'today'; then DAYS=1; fi

NOW_CD=$(( $(date +%s) - 978307200 ))
FUTURE_CD=$(( $(date +%s) + DAYS * 86400 - 978307200 ))

# Fetch all timed events in window, detect overlaps in Python
sqlite3 -separator '|' "$DB" "
SELECT
  ci.ROWID,
  ci.summary,
  date(COALESCE(oc.occurrence_start_date, oc.occurrence_date) + 978307200, 'unixepoch', 'localtime') as day,
  COALESCE(oc.occurrence_start_date, oc.occurrence_date) as start_cd,
  COALESCE(oc.occurrence_end_date, oc.occurrence_date + 3600) as end_cd,
  strftime('%H:%M', COALESCE(oc.occurrence_start_date, oc.occurrence_date) + 978307200, 'unixepoch', 'localtime') as start_time,
  strftime('%H:%M', COALESCE(oc.occurrence_end_date, oc.occurrence_date + 3600) + 978307200, 'unixepoch', 'localtime') as end_time,
  c.title as calendar
FROM OccurrenceCache oc
JOIN CalendarItem ci ON oc.event_id = ci.ROWID
LEFT JOIN Calendar c ON ci.calendar_id = c.ROWID
LEFT JOIN Store s ON c.store_id = s.ROWID
WHERE oc.occurrence_date >= $NOW_CD
  AND oc.occurrence_date <= $FUTURE_CD
  AND ci.hidden = 0
  AND ci.status != 2
  AND ci.all_day = 0
  AND s.type != 5
  AND s.disabled = 0
GROUP BY ci.ROWID, day
ORDER BY day, start_cd;
" | python3 -c "
import sys

events = []
for line in sys.stdin:
    parts = line.strip().split('|')
    if len(parts) >= 8:
        rowid, title, day, start_cd, end_cd, start_time, end_time, calendar = parts[:8]
        events.append({'id': rowid, 'title': title, 'day': day,
                       'start': int(start_cd), 'end': int(end_cd),
                       'start_time': start_time, 'end_time': end_time, 'cal': calendar})

conflicts = []
for i in range(len(events)):
    for j in range(i+1, len(events)):
        a, b = events[i], events[j]
        if a['day'] != b['day']:
            break
        # Overlap: a.start < b.end AND a.end > b.start
        if a['start'] < b['end'] and a['end'] > b['start']:
            conflicts.append((a, b))

if not conflicts:
    print('No conflicts found.')
else:
    print(f'{len(conflicts)} conflict(s) found:')
    for a, b in conflicts:
        print(f\"  {a['day']}: [{a['start_time']}-{a['end_time']}] {a['title']} ({a['cal']})\")
        print(f\"         overlaps [{b['start_time']}-{b['end_time']}] {b['title']} ({b['cal']})\")
        print()
"

Read the full file on GitHub · 104 lines

Changes

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.

  1. 10d ago First seen · 104 lines · 31 tokens per session scan A 51bb9fc198b9

Subscribe to this mod's changes

calendar-conflicts is a skill published in the GitHub repository aashari/ai-agent-skills (5 stars, last pushed 6mo ago), licensed MIT. It adds 31 tokens to every session and 1,036 once invoked, about $0.0002 per session on Opus 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-31.