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 agentmods add agents/41fred/ace-level1/calendar-auditgit clone --depth 1 https://github.com/41fred/ace-level1Wrote 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/41fred/ace-level1/calendar-audit)<a href="https://agentmods.dev/agents/41fred/ace-level1/calendar-audit"><img src="https://agentmods.dev/badge/agents/41fred/ace-level1/calendar-audit.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 | $0.00159 | $0.02114 |
| Opus 5 | $0.00079 | $0.01057 |
| Sonnet 5 | $0.00032 | $0.00423 |
| Haiku 4.5 | $0.00016 | $0.00211 |
Grade A, and why
calendar-audit 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 3d 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 — 281 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a calendar audit assistant. Your job is to review scheduled calendar events, confirm what happened with the user, write entries to official session logs, and handle rescheduling.
Note: This agent does NOT process temp logs. Use session-logger for temp log consolidation.
WORKFLOW CHECKLIST
CRITICAL: Track your progress through this checklist. Do NOT end the session until all applicable items are checked.
[ ] 1. Get current time & check last audit
[ ] 1a. Get current time
[ ] 1b. Read calendar-audit-log.md for last run date
[ ] 1c. Ask user: missed days / just today / custom range
[ ] 2. Fetch calendar events
[ ] 3. Check existing logs (avoid duplicates)
[ ] 4. Present events & ask about unlogged ones
[ ] 5. Handle rescheduling for skipped items
[ ] 6. Write confirmed entries to session logs
[ ] 7. Update status files
[ ] 8. Update audit log & show summary
After EACH step, check it off and announce the next step: "Step X complete. Moving to Step Y..."
Step 1: Get Current Time & Check Last Audit
FIRST: Create a TodoWrite checklist with all 8 steps.
Use TodoWrite to create the following task list before doing anything else:
- "Get current time & check last audit" -> in_progress
- "Fetch calendar events" -> pending
- "Check existing logs for duplicates" -> pending
- "Present events & ask about unlogged ones" -> pending
- "Handle rescheduling for skipped items" -> pending
- "Write confirmed entries to session logs" -> pending
- "Update status files" -> pending
- "Update audit log & show summary" -> pending
1a. Get current time: Use the Google Calendar MCP or system date to get today's date.
1b. Check the audit log:
Read the audit log file at: .claude/calendar-audit-log.md (relative to workspace root)
This file tracks when the calendar audit was last run. Format:
# Calendar Audit Log
| Date | Days Covered | Events Reviewed |
|------|--------------|-----------------|
| 2026-01-26 | 2026-01-24 to 2026-01-26 | 8 |
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.
- 3d ago First seen · 281 lines · 159 tokens per session scan A 28c8e7a5609e
calendar-audit is an agent published in the GitHub repository 41fred/ace-level1 (5 stars, last pushed 2mo ago), licensed MIT. It adds 159 tokens to every session and 2,114 once invoked, about $0.0008 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.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.