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/sonichi/sutando/macos-toolsnpx skills add sonichi/sutando --skill macos-toolsgit clone --depth 1 https://github.com/sonichi/sutandoWrote 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/sonichi/sutando/macos-tools)<a href="https://agentmods.dev/skills/sonichi/sutando/macos-tools"><img src="https://agentmods.dev/badge/skills/sonichi/sutando/macos-tools.svg" alt="Measured on agentmods" 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 | $0.00052 | $0.00615 |
| Opus 5 | $0.00026 | $0.00308 |
| Sonnet 5 | $0.00010 | $0.00123 |
| Haiku 4.5 | $0.00005 | $0.00061 |
Grade A, and why
macos-tools 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 4d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
macOS Tools
Native macOS integrations via AppleScript. No API keys needed — works on any Mac.
When to Use
- Screen: "What's on my screen?", "help me with this", "describe what I'm looking at"
- Calendar: "What's on my schedule?", "do I have meetings today?"
- Reminders: "Add a reminder", "what's on my todo list?", "mark X as done"
- Contacts: "What's Bob's email?", "find contact for..."
- Email: "Send an email to...", "draft a message to..."
- File search: "Find my resume", "where's that PDF?"
Tools
Screen Capture
bash "$SKILL_DIR/scripts/screen-capture.sh"
Returns path to PNG screenshot. Use the Read tool on the path to view it.
Calendar
Prefer the google-calendar skill if installed. Fallback to macOS Calendar:
python3 "$SKILL_DIR/scripts/calendar-reader.py" 7 # next 7 days, JSON
python3 "$SKILL_DIR/scripts/calendar-reader.py" 1 text # today, plain text
Reminders
python3 "$SKILL_DIR/scripts/reminders.py" list # all incomplete
python3 "$SKILL_DIR/scripts/reminders.py" add "Call Bob" # add reminder
python3 "$SKILL_DIR/scripts/reminders.py" add "Fix bug" "2026-03-17" # with due date
python3 "$SKILL_DIR/scripts/reminders.py" complete "Call Bob" # mark done
Contacts
python3 "$SKILL_DIR/scripts/contacts.py" search "Bob" # find by name
Returns name, emails, phones. Use before sending email to resolve names to addresses.
Email (Apple Mail)
python3 "$SKILL_DIR/scripts/email-sender.py" "[email protected]" "Subject" "Body"
python3 "$SKILL_DIR/scripts/email-sender.py" "[email protected]" "Subject" "Body" --draft
Sends via Mail.app. Use --draft to create without sending. Always confirm with user before sending.
Spotlight File Search
mdfind "quarterly report" # search by content or filename
mdfind -name "resume.pdf" # search by filename only
Requirements
- macOS (uses AppleScript)
- Calendar, Reminders, Contacts, Mail apps (built into macOS)
- Grant Accessibility permissions if prompted
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 66 lines · 52 tokens per session scan A b7868a8f9511
macos-tools is a skill published in the GitHub repository sonichi/sutando (390 stars, last pushed today), licensed MIT. It adds 52 tokens to every session and 615 once invoked, about $0.0003 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
cc-hooks
Multi-agent hook system: author hooks once as rulesync-canonical hooks.json (HookDefinitionSchema), deploy via superskill install / superskill hook emit to Claude Code, Codex, OpenCode, Pi (pi-hooks), and Gemini CLI. Covers command, prompt, and http hooks, cross-platform event mapping, and safety invariants.
mode
Adopt the lead role for this session: plan work, delegate to executors via relay, review reports, never implement large work directly. Invoke with /relay:mode.
verify
Machine-check an executor's report against its staged reality — TL;DR block well-formed, claimed files actually staged, declared counts cross-checked — stamping MALFORMED / MISMATCH / INCONCLUSIVE / COUNTS-MATCH. Invoke with /relay:verify, or when asked "check that report", "did it really do what it says", "verify X's…
auto
Flip this lead session's autonomous posture: proceed by default on routine in-plan steps instead of asking, or go back to waiting. Invoke with /relay:auto, or when asked to "go autonomous", "stop asking me every time", "just proceed", "turn auto off", "what posture am I in".
collaborating-with-gemini
Delegates coding tasks to Gemini CLI for prototyping, debugging, and code review. Use when needing algorithm implementation, bug analysis, or code quality feedback. Supports multi-turn sessions via SESSIONID.
handoff
Hand this lead session off to a fresh successor. Invoke with /relay:handoff, or when asked to "hand off", "hand this off to a new session", "start a successor lead".