01-calendar-pull

01-calendar-pull is an agent for Claude Code from assafkip/kipi-system. It costs 18 tokens per session (491 once invoked), scanned A, original, MIT.

A data-fetching agent that collects Google Calendar events for the next seven days and saves them in a structured file.

In plain words
What is it for?
It collects event titles, dates, times, attendees, and links or locations, separating today’s events from the rest of the week.
Why use it?
It puts upcoming meetings and their key details in one predictable file for later workflow steps.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter.

Good fit It collects event titles, dates, times, attendees, and links or locations, separating today’s events from the rest of the week.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/assafkip/kipi-system/01-calendar-pull
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.

Clone the repo
git clone --depth 1 https://github.com/assafkip/kipi-system

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 01-calendar-pull

README.md
[![agentmods](https://agentmods.dev/badge/agents/assafkip/kipi-system/01-calendar-pull.svg)](https://agentmods.dev/agents/assafkip/kipi-system/01-calendar-pull)
Your own site
<a href="https://agentmods.dev/agents/assafkip/kipi-system/01-calendar-pull"><img src="https://agentmods.dev/badge/agents/assafkip/kipi-system/01-calendar-pull.svg" alt="Measured on agentmods" height="20"></a>
Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 491 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.00018 $0.00491
Opus 5 $0.00009 $0.00246
Sonnet 5 $0.00004 $0.00098
Haiku 4.5 $0.00002 $0.00049

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

Security

Grade A, and why

01-calendar-pull 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.

q-system/.q-system/agent-pipeline/agents/01-calendar-pull.md · 59 lines

What it actually says

Agent: Calendar Pull

You are a data-pull agent. Your ONLY job is to fetch calendar data and write it to disk.

Reads

  • Nothing from disk. This agent fetches live from Google Calendar MCP.

Instructions

  1. Use Google Calendar MCP to fetch events for the next 7 days starting {{DATE}}
  2. For each event, extract: title, date, time, attendees, location/link
  3. Write results to {{BUS_DIR}}/calendar.json:
{
  "bus_version": 1,
  "date": "{{DATE}}",
  "generated_by": "01-calendar-pull",
  "today": [
    {"title": "...", "time": "...", "attendees": ["..."], "link": "..."}
  ],
  "this_week": [
    {"title": "...", "date": "...", "time": "...", "attendees": ["..."], "link": "..."}
  ]
}
  1. Do NOT analyze or interpret. Just pull and structure.

Token budget: <1K tokens output

Collection Gate (Incremental Collection)

If a ## Collection Gate Verdict section appears above with verdict data:

  1. If verdict is "skip":

    • Verify {{BUS_DIR}}/calendar.json exists and is valid JSON
    • If valid: log "Calendar: reusing existing bus file" and EXIT successfully
    • If file is missing or corrupt: proceed with fresh collection (ignore skip)
  2. If verdict is "collect":

    • Proceed with normal collection
    • If since is not null, use it as the start time for the Calendar MCP query to capture events added since last pull. Still include the full 7-day forward window.
  3. After successful write of calendar.json, update collection state:

    • Read {{QROOT}}/memory/collection-state.json
    • Set sources.calendar.last_collected to current UTC ISO timestamp
    • Set sources.calendar.last_bus_date to {{DATE}}
    • Write the file back

If no Collection Gate Verdict section is present, collect normally (backward compatible).

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. 8d ago First seen · 59 lines · 18 tokens per session scan A f7bcd27ca451

Subscribe to this mod's changes

01-calendar-pull is an agent published in the GitHub repository assafkip/kipi-system (109 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 491 once invoked, about $0.0001 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-30.

Related

Other agents, from other repositories

gtd-inbox-processor

Use this agent when you need to process individual entries from inbox.org in a GTD (Getting Things Done) system. This agent should be invoked:\n\n- After capturing new items to inbox.org and wanting to process them into the appropriate action lists\n- When conducting a GTD review and need to clear the inbox…

datacore-one/datacore · 0 tokens

ai-task-executor

Core 24/7 autonomous task execution hub that scans nextactions.org for :AI: tagged tasks, routes them to specialized GTD agents based on task type, handles execution outcomes, logs to journal, and updates org-mode task states. Returns JSON responses with detailed success/failure reporting.

datacore-one/datacore · 0 tokens

ingest-orchestrator

Orchestrator agent that coordinates file/folder ingestion from inbox folders or external sources. Plans first, gets approval, processes with knowledge-extractor subagents, reports results, and cleans up source. Replaces ingest-coordinator per DIP-0021.

datacore-one/datacore · 56 tokens

gtd-inbox-coordinator

Orchestrator agent that coordinates batch inbox processing by spawning gtd-inbox-processor subagents for each entry. Use when the user wants to clear their inbox or during GTD reviews. Reads inbox.org, identifies all entries, spawns parallel processors, and aggregates results.

datacore-one/datacore · 62 tokens

action-item-extractor

Extracts actionable tasks from research outputs and routes them to appropriate GTD focus areas in nextactions.org.

datacore-one/datacore · 25 tokens

gtd-process-inbox

You are the inbox processing orchestrator for a GTD (Getting Things Done) system. Your job is to systematically process ALL entries in inbox.org, transforming raw captures into well-organized, actionable items in nextactions.org.

datacore-one/datacore · 51 tokens