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 lisihao/Solar --skill officegit clone --depth 1 https://github.com/lisihao/SolarWrote 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/lisihao/solar/office)<a href="https://agentmods.dev/skills/lisihao/solar/office"><img src="https://agentmods.dev/badge/skills/lisihao/solar/office/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/lisihao/solar/office"><img src="https://agentmods.dev/badge/skills/lisihao/solar/office.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.00024 | $0.01158 |
| Opus 5 | $0.00012 | $0.00579 |
| Sonnet 5 | $0.00005 | $0.00232 |
| Haiku 4.5 | $0.00002 | $0.00116 |
Grade A, and why
office 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 7d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/office - 办公助手模式
基于 Moltbot 的办公能力集成
启动
当用户说 "我要办公" 时，自动进入办公模式并显示：
┌─ 📋 Office Mode ────────────────────────────────┐
│ 办公助手已启动 │
├─────────────────────────────────────────────────┤
│ 📧 邮件 /office email himalaya CLI │
│ ⏰ 提醒 /office reminders Apple Reminders │
│ ✅ 任务 /office tasks Things 3 │
│ 📝 笔记 /office notes Apple Notes │
│ 📓 Notion /office notion Notion API │
│ 📋 Trello /office trello Trello 看板 │
├─────────────────────────────────────────────────┤
│ 💡 直接说需求，我会自动选择合适的工具 │
│ 例如: "查看今天的邮件" "添加一个提醒" │
└─────────────────────────────────────────────────┘
功能模块
📧 邮件管理 (/office email)
使用 Himalaya CLI 管理邮件：
| 操作 | 命令 |
|---|---|
| 列出邮件 | himalaya envelope list |
| 读取邮件 | himalaya message read <id> |
| 发送邮件 | himalaya message write |
| 回复邮件 | himalaya message reply <id> |
| 搜索邮件 | himalaya envelope list from xxx subject xxx |
配置: ~/.config/himalaya/config.toml
⏰ 提醒管理 (/office reminders)
使用 remindctl 管理 Apple Reminders：
| 操作 | 命令 |
|---|---|
| 今日提醒 | remindctl today |
| 添加提醒 | remindctl add "内容" --due tomorrow |
| 完成提醒 | remindctl complete <id> |
| 列出清单 | remindctl list |
前提: macOS + Reminders 权限
✅ 任务管理 (/office tasks)
使用 things CLI 管理 Things 3：
| 操作 | 命令 |
|---|---|
| 今日任务 | things today |
| 收件箱 | things inbox |
| 添加任务 | things add "标题" --when today |
| 搜索任务 | things search "关键词" |
前提: macOS + Things 3 + Full Disk Access
📝 笔记管理 (/office notes)
使用 AppleScript 管理 Apple Notes：
| 操作 | 方法 |
|---|---|
| 创建笔记 | osascript |
| 搜索笔记 | osascript |
📓 Notion (/office notion)
使用 Notion API：
| 操作 | 说明 |
|---|---|
| 搜索页面 | POST /v1/search |
| 创建页面 | POST /v1/pages |
| 查询数据库 | POST /v1/data_sources/{id}/query |
配置: ~/.config/notion/api_key
📋 Trello (/office trello)
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.
- 7d ago First seen · 146 lines · 24 tokens per session scan A 2e32f869f33b
office is a skill published in the GitHub repository lisihao/Solar (2 stars, last pushed 28d ago), licensed MIT. It adds 24 tokens to every session and 1,158 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-09-03.
Other skills, from other repositories
things-mac
Manage Things 3 via the things CLI on macOS (add/update projects+todos via URL scheme; read/search/list from the local Things database). Use when a user asks Otto to add a task to Things, list inbox/today/upcoming, search tasks, or inspect projects/areas/tags.
gsd-ns-manage
Route to the appropriate management skill based on the user's intent. gsd-config (settings + advanced + integrations + profile) and gsd-workspace (new + list + remove) are post-#2790 consolidated entries.
slack-tools
Slack workspace management and automation specialist.
triage-inbox
Triage academic email and calendar (Gmail / Google Calendar via the session's MCP) into a prioritized digest plus a referee-obligations tracker — classifying referee requests, R&R and editor correspondence, co-author threads, seminar and conference invites, and grant/admin deadlines, and proposing a human-gated action…
ceo-setup
One-time onboarding for the executive/manager commitment workflow — delegation-heavy, meeting prep, decision capture, morning and evening digests. Creates a commitments project and installs two dashboard widgets. After successful setup this skill is excluded from selection until the marker file is deleted.
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…