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 jqlts1/omnifocus-mcp-enhanced --skill omnifocus-cligit clone --depth 1 https://github.com/jqlts1/omnifocus-mcp-enhancedWrote 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/jqlts1/omnifocus-mcp-enhanced/omnifocus-cli)<a href="https://agentmods.dev/skills/jqlts1/omnifocus-mcp-enhanced/omnifocus-cli"><img src="https://agentmods.dev/badge/skills/jqlts1/omnifocus-mcp-enhanced/omnifocus-cli/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/jqlts1/omnifocus-mcp-enhanced/omnifocus-cli"><img src="https://agentmods.dev/badge/skills/jqlts1/omnifocus-mcp-enhanced/omnifocus-cli.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 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 MCP Rug Pull · line 468 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 474 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 502 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00068 | $0.06056 |
| Opus 5 | $0.00034 | $0.03028 |
| Sonnet 5 | $0.00014 | $0.01211 |
| Haiku 4.5 | $0.00007 | $0.00606 |
Grade A, and why
omnifocus-cli 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 9d 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 — 512 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OmniFocus CLI
Overview
Use the local bundled CLI instead of direct MCP tool-calling for OmniFocus requests. The MCP server exposes 26 consolidated tools; loading all their schemas into chat is expensive. This CLI gives you the same capabilities as deterministic shell commands.
CLI location: bin/omnifocus-enhanced.cjs (relative to this skill directory).
Flag Conventions
These matter — getting them wrong causes confusing errors:
- Booleans need an explicit value:
--flagged true(NOT bare--flagged) - Arrays are comma-separated:
--task-status Available,Next - Empty string means "move to root":
--new-parent-folder-name "" - Complex/nested args: use
--raw '<json>'to bypass flag parsing entirely - Output: default text is best for user replies; add
-o jsononly when post-processing
Reading Tasks
Use get-tasks with --source to select the view. All views support task-tree
aware output with [N subtasks] counts.
Detailed reads render an assigned tag's full OmniFocus hierarchy, for example
团队 / 守一. Structured results keep the assigned leaf id and name and
add path plus ancestorIds; compact reads continue to omit tags.
# Inbox, flagged, forecast
bin/omnifocus-enhanced.cjs get-tasks --source inbox
bin/omnifocus-enhanced.cjs get-tasks --source flagged
bin/omnifocus-enhanced.cjs get-tasks --source forecast --days 7
# By tag
bin/omnifocus-enhanced.cjs get-tasks --source tag --tag-name "work"
# Custom perspectives (OmniFocus Pro) — read the tasks a perspective produces
bin/omnifocus-enhanced.cjs get-tasks --source custom --perspective-name "今日计划"
# Custom perspectives — read and edit the filter rules themselves
bin/omnifocus-enhanced.cjs manage-perspectives --action list
bin/omnifocus-enhanced.cjs manage-perspectives --action get --name "今日计划"
# Always preview a rule change first; --rules takes the document returned by get
bin/omnifocus-enhanced.cjs manage-perspectives --action update --name "今日计划" \
--rules '{"match":"all","rules":[{"type":"availability","value":"available"}]}' --dry-run true
# Subtask expansion
bin/omnifocus-enhanced.cjs get-tasks --source inbox --show-subtasks true
bin/omnifocus-enhanced.cjs get-tasks --source flagged --show-subtasks true --max-subtask-depth 1
bin/omnifocus-enhanced.cjs get-tasks --source forecast --days 7 --show-subtasks true --max-subtask-depth 2
bin/omnifocus-enhanced.cjs get-tasks --source tag --tag-name "work" --show-subtasks true
# Single task with attachment metadata
bin/omnifocus-enhanced.cjs get-task-by-id --task-id "<id>"
bin/omnifocus-enhanced.cjs get-task-by-id --task-id "<id>" --show-subtasks true
# Completed today
bin/omnifocus-enhanced.cjs filter-tasks --completed-today true --task-status Completed --sort-by completedDate
What ships with it
1 file 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.
- 9d ago First seen · 512 lines · 68 tokens per session scan A 75412752e0e6
omnifocus-cli is a skill published in the GitHub repository jqlts1/omnifocus-mcp-enhanced (61 stars, last pushed 23d ago), licensed MIT. It adds 68 tokens to every session and 6,056 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.