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 skills/ondrasek/cc-plugins/searchnpx skills add ondrasek/cc-plugins --skill searchgit clone --depth 1 https://github.com/ondrasek/cc-pluginsWhat 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.00055 | $0.00627 |
| Opus 5 | $0.00028 | $0.00313 |
| Sonnet 5 | $0.00011 | $0.00125 |
| Haiku 4.5 | $0.00006 | $0.00063 |
Grade A, and why
search scanned grade A with 1 finding 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -H "Authorization: Bearer $TOKEN" \ How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Search Calendar
Critical Rules
- Read cross-cutting behaviors first:
skills/shared/references/cross-cutting.md - Read-only — never create, modify, or delete events
- Search broadly, then filter — cast a wide net with the search query, then filter results for relevance
Context Files
Read these files before starting:
skills/shared/references/cross-cutting.md— provider detection, output format, error handlingskills/shared/references/providers.md— CLI commands and search syntax
Workflow
1. Extract Search Parameters
From the user's request, determine:
- Keyword(s): the subject/title to search for
- Attendee: if searching for meetings with a specific person
- Calendar: if searching a specific calendar
- Date range: if the user specifies a time window (default: next 30 days)
2. Detect Providers
Follow provider detection from cross-cutting.md. Stop if no provider is available.
3. Search Events
Google Calendar:
# Keyword search (searches upcoming events by default)
gcalcli search "KEYWORD" --tsv --details location --nocolor
# With date range
gcalcli search "KEYWORD" "START_DATE" "END_DATE" --tsv --details location --nocolor
Microsoft 365:
TOKEN=$(az account get-access-token --resource https://graph.microsoft.com --query accessToken -o tsv)
# Keyword search
curl -s -H "Authorization: Bearer $TOKEN" \
"https://graph.microsoft.com/v1.0/me/events?\$search=\"KEYWORD\"&\$select=subject,start,end,location,isAllDay,attendees,organizer&\$top=20&\$orderby=start/dateTime"
For attendee searches on Microsoft, examine the attendees and organizer fields in the results.
4. Format Output
Use the markdown table format from cross-cutting.md. Group results by day.
If searching for an attendee, include an Attendees column:
## Search Results — "standup"
| Time | Event | Location | Calendar |
|------|-------|----------|----------|
| 09:00–09:30 | Daily standup | Zoom | Work |
| 09:00–09:30 | Daily standup | Zoom | Work |
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.
- yesterday First seen · 76 lines · 55 tokens per session scan A 93259aa7c272
search is a skill published in the GitHub repository ondrasek/cc-plugins (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 55 tokens to every session and 627 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.