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.
git clone --depth 1 https://github.com/assafkip/kipi-systemWrote 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/agents/assafkip/kipi-system/01-calendar-pull)<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>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.00018 | $0.00491 |
| Opus 5 | $0.00009 | $0.00246 |
| Sonnet 5 | $0.00004 | $0.00098 |
| Haiku 4.5 | $0.00002 | $0.00049 |
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.
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
- Use Google Calendar MCP to fetch events for the next 7 days starting {{DATE}}
- For each event, extract: title, date, time, attendees, location/link
- 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": "..."}
]
}
- 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:
-
If
verdictis"skip":- Verify
{{BUS_DIR}}/calendar.jsonexists 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)
- Verify
-
If
verdictis"collect":- Proceed with normal collection
- If
sinceis 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.
-
After successful write of calendar.json, update collection state:
- Read
{{QROOT}}/memory/collection-state.json - Set
sources.calendar.last_collectedto current UTC ISO timestamp - Set
sources.calendar.last_bus_dateto{{DATE}} - Write the file back
- Read
If no Collection Gate Verdict section is present, collect normally (backward compatible).
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 · 59 lines · 18 tokens per session scan A f7bcd27ca451
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.
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…
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.
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.
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.
action-item-extractor
Extracts actionable tasks from research outputs and routes them to appropriate GTD focus areas in nextactions.org.
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.