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 commands/sanisideup/claude-code-granola-sync/sync-granolagit clone --depth 1 https://github.com/sanisideup/claude-code-granola-syncWrote 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/commands/sanisideup/claude-code-granola-sync/sync-granola)<a href="https://agentmods.dev/commands/sanisideup/claude-code-granola-sync/sync-granola"><img src="https://agentmods.dev/badge/commands/sanisideup/claude-code-granola-sync/sync-granola.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.00000 | $0.00714 |
| Opus 5 | $0.00000 | $0.00357 |
| Sonnet 5 | $0.00000 | $0.00143 |
| Haiku 4.5 | $0.00000 | $0.00071 |
Grade A, and why
sync-granola 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 5d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sync Granola meetings from local cache into the project folder with metadata preservation.
Arguments
The command accepts optional arguments from the user: $ARGUMENTS
Argument formats:
- No arguments: sync last 7 days (default)
- Number like
30or30d: sync last N days --allorall: sync all meetingsfolder:FolderName: sync only meetings from specific folder (e.g.,folder:Innovation)--no-transcripts: optional legacy flag (transcripts may not exist in cache v4)
Instructions
Run the Granola sync script with the appropriate arguments:
-
Parse the
$ARGUMENTSto determine sync options -
Build the command with proper flags:
- If
$ARGUMENTSis empty: use default (last 7 days) - If
$ARGUMENTScontains a number: use--days N - If
$ARGUMENTScontains--allorall: use--days 0 - If
$ARGUMENTScontainsfolder:X: extract folder name and use--folder X - If
$ARGUMENTScontains--no-transcripts: add the flag
- If
-
Execute the sync script:
python3 scripts/sync-granola.py [flags] -
After sync completes, provide a summary:
- Number of meetings synced
- Location of saved files
- Any errors encountered
Examples
User input: /sync-granola
Command: python3 scripts/sync-granola.py --days 7
User input: /sync-granola 30
Command: python3 scripts/sync-granola.py --days 30
User input: /sync-granola all
Command: python3 scripts/sync-granola.py --days 0
User input: /sync-granola folder:Innovation
Command: python3 scripts/sync-granola.py --days 7 --folder Innovation
User input: /sync-granola 14 --no-transcripts
Command: python3 scripts/sync-granola.py --days 14 --no-transcripts
Expected Output
After syncing, show the user:
- ✅ Success message with count of synced meetings
- 📁 File locations:
- Meeting notes:
main/sources/granola/meetings/ - Transcripts:
main/sources/granola/transcripts/(legacy/pre-migration only)
- Meeting notes:
- 📊 Brief summary of what was synced (date range, folders if filtered)
- ⚠️ Any warnings (especially metadata-only cache detection)
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.
- 5d ago First seen · 69 lines · 0 tokens per session scan A d34f83ac7e6f
sync-granola is a command published in the GitHub repository sanisideup/claude-code-granola-sync (11 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 714 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-30.
Other commands, from other repositories
organize-files
Organize and rename files based on content analysis.
search
Search across all project artifacts by keyword, document type, or requirement ID.
tree
Show file tree with sync status indicators showing which files are indexed, modified, new, or deleted.
notebook-status
Check the progress of a /agy:notebook sweep (for long document sets run with --background). Reports % complete, done/pending/failed counts, elapsed time and a rough ETA, and which documents are still pending — so you can resume. Read-only, no agy.
meeting_to_protocol
Transform doctor visit transcript into PHG updates, calendar events, and follow-ups.
assess
Run an AI literacy assessment — scan the repo for evidence, ask clarifying questions, produce a timestamped assessment document, apply immediate habitat fixes, recommend workflow changes, capture a reflection, and add a literacy level badge to the README.