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 aAAaqwq/AGI-Super-Team --skill calendly-automationgit clone --depth 1 https://github.com/aAAaqwq/AGI-Super-TeamWrote 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/aaaaqwq/agi-super-team/calendly-automation)<a href="https://agentmods.dev/skills/aaaaqwq/agi-super-team/calendly-automation"><img src="https://agentmods.dev/badge/skills/aaaaqwq/agi-super-team/calendly-automation/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/aaaaqwq/agi-super-team/calendly-automation"><img src="https://agentmods.dev/badge/skills/aaaaqwq/agi-super-team/calendly-automation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 5 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 41 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 91 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 102 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 151 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 172 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00042 | $0.02643 |
| Opus 5 | $0.00021 | $0.01321 |
| Sonnet 5 | $0.00008 | $0.00529 |
| Haiku 4.5 | $0.00004 | $0.00264 |
Grade A, and why
calendly-automation 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 6d 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 — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Calendly Automation via Rube MCP
Automate Calendly operations including event listing, invitee management, scheduling link creation, availability queries, and organization administration through Composio's Calendly toolkit.
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Calendly connection via
RUBE_MANAGE_CONNECTIONSwith toolkitcalendly - Always call
RUBE_SEARCH_TOOLSfirst to get current tool schemas - Many operations require the user's Calendly URI, obtained via
CALENDLY_GET_CURRENT_USER
Setup
Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitcalendly - If connection is not ACTIVE, follow the returned auth link to complete Calendly OAuth
- Confirm connection status shows ACTIVE before running any workflows
Core Workflows
1. List and View Scheduled Events
When to use: User wants to see their upcoming, past, or filtered Calendly events
Tool sequence:
CALENDLY_GET_CURRENT_USER- Get authenticated user URI and organization URI [Prerequisite]CALENDLY_LIST_EVENTS- List events scoped by user, organization, or group [Required]CALENDLY_GET_EVENT- Get detailed info for a specific event by UUID [Optional]
Key parameters:
user: Full Calendly API URI (e.g.,https://api.calendly.com/users/{uuid}) - NOT"me"organization: Full organization URI for org-scoped queriesstatus:"active"or"canceled"min_start_time/max_start_time: UTC timestamps (e.g.,2024-01-01T00:00:00.000000Z)invitee_email: Filter events by invitee email (filter only, not a scope)sort:"start_time:asc"or"start_time:desc"count: Results per page (default 20)page_token: Pagination token from previous response
Pitfalls:
- Exactly ONE of
user,organization, orgroupmust be provided - omitting or combining scopes fails - The
userparameter requires the full API URI, not"me"- useCALENDLY_GET_CURRENT_USERfirst invitee_emailis a filter, not a scope; you still need one of user/organization/group- Pagination uses
count+page_token; loop untilpage_tokenis absent for complete results - Admin rights may be needed for organization or group scope queries
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.
- 6d ago First seen · 212 lines · 42 tokens per session scan A c52fab71441c
calendly-automation is a skill published in the GitHub repository aAAaqwq/AGI-Super-Team (91 stars, last pushed yesterday), licensed MIT. It adds 42 tokens to every session and 2,643 once invoked, about $0.0002 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-09-05.
Other skills, from other repositories
mission-control
Interact with Mission Control — AI agent orchestration dashboard. Use when registering agents, managing tasks, syncing skills, or querying agent/task status via MC APIs.
triage
Triage a GitHub repository's open issues by finding exact duplicates, rejecting evidenceably off-base requests, requesting concrete clarification, applying only existing labels, and opening a linked root-cause issue when multiple reports share one underlying invariant failure. Use when a maintainer asks to triage…
dos-goal-fleet
Launch multiple goal-scoped workers in waves, each with a witness-gated stop condition and dos arbitrate file-tree safety. Use when an operator asks to run several independent goals in parallel and fold only verified ships.
flo
MoFlo ticket spell - analyze and execute GitHub issues.
dos-next-up
Snapshot the repo's phased-plan portfolio into a dispatch packet: audit candidates with dos verify, render who-does-what, and emit a dos gate verdict. Use when you need the current next-work view before dispatching agents.
dos-dispatch
Plan and ship the next batch on one lane: run dos-next-up, acquire a lease with dos arbitrate, gate empty work, dispatch the packet, and archive the run. Use when a single lane should move end to end with collision safety.