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 skills add PsychQuant/che-ical-mcp --skill troubleshoot-tccgit clone --depth 1 https://github.com/PsychQuant/che-ical-mcpWrote 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/skills/psychquant/che-ical-mcp/troubleshoot-tcc)<a href="https://agentmods.dev/skills/psychquant/che-ical-mcp/troubleshoot-tcc"><img src="https://agentmods.dev/badge/skills/psychquant/che-ical-mcp/troubleshoot-tcc/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.
<a href="https://agentmods.dev/skills/psychquant/che-ical-mcp/troubleshoot-tcc"><img src="https://agentmods.dev/badge/skills/psychquant/che-ical-mcp/troubleshoot-tcc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00119 | $0.03633 |
| Opus 5 | $0.00060 | $0.01817 |
| Sonnet 5 | $0.00024 | $0.00727 |
| Haiku 4.5 | $0.00012 | $0.00363 |
Grade A, and why
troubleshoot-tcc 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 12d 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Troubleshoot TCC permissions for che-ical-mcp
This skill is the first thing to try when calendar / reminder tools fail. Most "calendar tools don't work" reports are TCC (Transparency, Consent & Control) state issues rather than code bugs.
The two-layer authorization model (read this first, #168)
macOS TCC may attribute a Calendar/Reminders access check to the responsible process — the host app that (transitively) spawned the binary — not only to the binary itself. Two independent layers can therefore appear in System Settings → Privacy & Security → Calendar / Reminders:
| Layer | Entry looks like | When it exists |
|---|---|---|
| Binary layer — CheICalMCP's own grant | CheICalMCP with a green exec icon |
Created by --setup dialogs or Claude Desktop's first prompt |
| Host layer — the responsible process | Depends on host, see table below | Created when a TCC check is attributed to the host context |
Host-layer entry names:
| Host | Host-layer entry in System Settings | Notes |
|---|---|---|
| Claude Code (CLI) | A bare version-number string, e.g. 2.1.202, with a question-mark document icon |
That IS the Claude Code native binary — the real executable lives at ~/.local/share/claude/versions/<version> (~/.local/bin/claude is a symlink to it), and TCC displays a path-keyed client by its filename. ⚠️ The path rotates on every Claude Code update, so this grant can silently go stale (#170) |
| Terminal.app / iTerm2 / VS Code | The app's own name | Applies when you run the binary (or claude) from that app's shell |
| Claude Desktop | (no host entry needed) | Desktop spawns .mcpb servers via /Applications/Claude.app/Contents/Helpers/disclaimer, which makes the child its own responsible process — the .mcpb CheICalMCP entry is self-contained. (The disclaimer shim exec-replaces itself, so it usually won't show up in a live ps ancestry trace — identify Desktop context by the absence of a claude/versions/… ancestor, not by finding the disclaimer.) |
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.
- 12d ago First seen · 213 lines · 119 tokens per session scan A f306fd3a9051
troubleshoot-tcc is a skill published in the GitHub repository PsychQuant/che-ical-mcp (35 stars, last pushed 3d ago), licensed MIT. It adds 119 tokens to every session and 3,633 once invoked, about $0.0006 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 skills, from other repositories
apple-pim
Native macOS personal information management for calendars, reminders, contacts, and local Mail.app. Use when the user wants to schedule meetings, create events, check their calendar, create or complete reminders, look up contacts, find someone's phone number or email, manage tasks and to-do lists, triage local…
use-peek
Use the peek CLI to inspect, debug, and interact with native macOS app windows. Use when the user asks to debug a macOS app, inspect UI elements, take screenshots, click buttons, or automate interactions with native apps.
apple-calendar-cli
You have access to apple-calendar-cli, a command-line tool for managing Apple Calendar events via EventKit on macOS.
api-errors
McpError constructor, JsonRpcErrorCode reference, and error handling patterns for @cyanheads/mcp-ts-core. Use when looking up error codes, understanding where errors should be thrown vs. caught, or using ErrorHandler.tryCatch in services.
browser-edge-cases
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.
ios-simulator
Verify and debug native, React Native, Expo, or Flutter apps on an iOS Simulator with agent-device. Use when an agent needs to launch an app, inspect its live UI, tap, type, scroll, validate a code change, collect failure evidence, or reproduce a workflow on an iPhone or iPad Simulator.