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 dcadolph/vamoose --skill skillgit clone --depth 1 https://github.com/dcadolph/vamooseWrote 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/dcadolph/vamoose/skill)<a href="https://agentmods.dev/skills/dcadolph/vamoose/skill"><img src="https://agentmods.dev/badge/skills/dcadolph/vamoose/skill/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/dcadolph/vamoose/skill"><img src="https://agentmods.dev/badge/skills/dcadolph/vamoose/skill.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.00092 | $0.00630 |
| Opus 5.5 | $0.00037 | $0.00252 |
| Sonnet 5.5 | $0.00018 | $0.00126 |
| Haiku 4.5 | $0.00009 | $0.00063 |
Grade A, and why
vamoose 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 1mo 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vamoose
Drive the vamoose CLI to run a time-off request end to end.
Before you start
Confirm the environment is configured. If VAMOOSE_CLIENT_ID is unset, stop and
point the user at the README setup section; the flow cannot run without it.
vamoose version # confirm the binary is on PATH
If the binary is missing, build it from the repo root with go build -o vamoose .
and use ./vamoose.
Gather the request
Ask the user for, and confirm back:
- Departure date (or date-time). Accept
YYYY-MM-DDor RFC3339. - Return date (or date-time).
- Subject line, for example "Out: beach week".
- Optional: a note for the body, and a manager email if they do not want the directory lookup.
Do not guess dates. If the user is vague ("next week"), resolve to explicit calendar dates and read them back before running anything.
Run the flow
-
Create the hold and invite the manager:
vamoose request --start <start> --end <end> --subject "<subject>"Add
--body,--manager, or--tzwhen the user supplied them. Offer--dry-runfirst if the user wants to preview. -
Tell the user the manager was invited and must accept the invite to approve. The command prints the hold id and caches it, so later steps need no id.
-
When the user says the manager approved, or to check, run:
vamoose check -
Once
checkreports approval, fan out to the team:vamoose promoteOr run
vamoose check --promoteto promote automatically the moment approval lands.
Notes
- The hold is shown as free, so it never blocks anyone's calendar.
- The manager is a required attendee; their acceptance is the approval.
- Team members are added as optional attendees.
- Two backends:
--provider graph(default) or--provider google. Google has no directory, so on Google pass--managerand set the team withvamoose team set. - Report command output plainly. On an error, surface the exact message rather than retrying blindly.
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.
- 1mo ago First seen · 79 lines · 92 tokens per session scan A 417aa23fc83f
vamoose is a skill published in the GitHub repository dcadolph/vamoose (0 stars, last pushed 1mo ago), licensed MIT. It adds 92 tokens to every session and 630 once invoked, about $0.0004 per session on Opus 5.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-31.
Other skills, from other repositories
c-calendar
View and create calendar events via gog (Google Calendar) or icalBuddy (Apple Calendar). Check availability, list upcoming events, create/update/delete events, and manage multiple calendars.
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…
notion-cli
Work with Notion from the terminal using the notion CLI. Use when the user needs to read, create, update, query, or manage Notion pages, databases, blocks, comments, users, or files programmatically. Covers the entire Notion API with 50+ commands. Triggers: Notion workspace automation, database queries, page creation…
Pear - iCloud Calendar, Reminders, Contacts & Mail
Pear provides hosted MCP access to iCloud Calendar, Contacts, Mail, and legacy CalDAV reminder data. Tools are prefixed with pear. Calendar and legacy reminders use CalDAV; Contacts use CardDAV; Mail uses IMAP/SMTP. Apple's upgraded Reminders store is not accessible through this connection.
lx
Codebase exploration tool that reads many files or whole directories in a single call, with per-file headers, glob include/exclude filters, function/type skeleton extraction (signatures only, no bodies), and head/tail line slicing.
rem-cli
Create, list, update, complete, tag, and search macOS Reminders via the rem CLI. Use when the user wants to manage Apple Reminders from the terminal, automate reminder workflows, reference reminders in shell scripts, or schedule anything on macOS.