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 Xiaowen-Jiang/agent-enterprise --skill meeting_schedulinggit clone --depth 1 https://github.com/Xiaowen-Jiang/agent-enterpriseWrote 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/xiaowen-jiang/agent-enterprise/meeting_scheduling)<a href="https://agentmods.dev/skills/xiaowen-jiang/agent-enterprise/meeting_scheduling"><img src="https://agentmods.dev/badge/skills/xiaowen-jiang/agent-enterprise/meeting_scheduling/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/xiaowen-jiang/agent-enterprise/meeting_scheduling"><img src="https://agentmods.dev/badge/skills/xiaowen-jiang/agent-enterprise/meeting_scheduling.svg" alt="Reviewed on agentmods" width="80" 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.00014 | $0.00407 |
| Opus 5 | $0.00007 | $0.00204 |
| Sonnet 5 | $0.00003 | $0.00081 |
| Haiku 4.5 | $0.00001 | $0.00041 |
Grade A, and why
Meeting Scheduling 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 10d 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
Process
- Understand the request: who needs to meet, how long, what topic, any time preferences
- Check calendar availability for the requested date range
- Identify free slots that match the requested duration
- Propose 2-3 options with specific times, considering:
- Avoid back-to-back meetings (leave 15-min buffer)
- Prefer morning for important meetings, afternoon for routine
- Respect time zones if attendees are in different locations
- Create the event once the CEO approves a time slot
- Confirm with a summary of what was scheduled
Output Format
Available Slots for [Meeting Title]
Duration: X minutes | Attendees: list
| Option | Date & Time | Notes |
|---|---|---|
| 1 | Mon Mar 24, 10:00-10:30 AM | Morning slot, no conflicts |
| 2 | Mon Mar 24, 2:00-2:30 PM | After lunch, 1hr gap before next meeting |
| 3 | Tue Mar 25, 9:00-9:30 AM | Next day, first slot available |
Shall I schedule one of these?
Guidelines
- Always check for conflicts before proposing times
- Include time zone if relevant (default to CEO's local time)
- For recurring meetings, suggest a consistent weekly slot
- When creating events, include: title, attendees (with email), description, duration
- Use
save_memoryto remember scheduling preferences (preferred meeting times, buffer preferences) - Never create calendar events without CEO confirmation — propose first, create after approval
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.
- 10d ago First seen · 43 lines · 14 tokens per session scan A e83179a40f21
Meeting Scheduling is a skill published in the GitHub repository Xiaowen-Jiang/agent-enterprise (52 stars, last pushed 5mo ago), licensed MIT. It adds 14 tokens to every session and 407 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 skills, from other repositories
live-tutorial
Create an annotated MP4 tutorial from a workflow demonstrated in the owner's actual application. Use when asked for a tutorial video, not merely to watch an action live.
google-calendar-tool
Google Calendar integration tool for listing and creating events via OAuth2 Calendar API access. Use when: checking upcoming events, creating appointments, or updating your schedule.
telegram-userbot
A skill for connecting to and working through the owner's personal Telegram account, rather than a Telegram bot. It can read personal chats, search messages, and send messages as the account owner after setup and consent.
dbrain-processor
Personal assistant for processing daily voice/text entries from Telegram. Classifies content, saves thoughts to Obsidian with wiki-links, generates HTML reports. Integrates Your Business context (clients, projects, CRM). Triggers on /process command or daily 21:00 cron.
cron
A scheduling and reminder helper that manages recurring or one-time jobs through a command-line tool. The jobs are reread regularly, run in a separate cron session, and send results to the user in Telegram.
calendar-scheduling
Use when a product needs a booking surface — a pick-a-slot page, a Cal.com/Calendly embed, or real availability plus the confirmed meeting written to Google/Outlook — or when fixing double-booking, DST drift, or orphaned reschedule events. NOT calendar CRUD with no booking surface (that is google-workspace), NOT the…