omnifocus-mcp: Skill for Claude Code

.claude/skills/integration-testing/SKILL.md

integration-testing is a skill for Claude Code from s-morgan-jeffries/omnifocus-mcp. It costs 73 tokens per session (1,310 once invoked), scanned A, original, MIT.

Instructions for testing integrations with a real OmniFocus application. OmniFocus is a task-management app, and integration tests check the connection between code and the real app rather than using only simulated responses.

In plain words
What is it for?
Use it when setting up, running, or debugging OmniFocus integration tests, especially for AppleScript operations, recurring tasks, rich text, timing, and version-specific behavior.
Why use it?
Mocked tests can pass even when AppleScript or OmniFocus behavior is wrong; these tests help reveal those runtime problems safely using a separate test database.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is s-morgan-jeffries/omnifocus-mcp's own configuration. It tells Claude Code how to work on omnifocus-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything omnifocus-mcp configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is ./scripts/setup_test_database.sh.

Reuse

Borrowing it

Nothing to install: this file belongs to s-morgan-jeffries/omnifocus-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/s-morgan-jeffries/omnifocus-mcp/main/.claude/skills/integration-testing/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/s-morgan-jeffries/omnifocus-mcp

Made for: Claude Code.

Wrote 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.

agentmods badge for integration-testing

README.md
[![agentmods](https://agentmods.dev/badge/skills/s-morgan-jeffries/omnifocus-mcp/integration-testing/github.svg)](https://agentmods.dev/skills/s-morgan-jeffries/omnifocus-mcp/integration-testing)
Your own site
<a href="https://agentmods.dev/skills/s-morgan-jeffries/omnifocus-mcp/integration-testing"><img src="https://agentmods.dev/badge/skills/s-morgan-jeffries/omnifocus-mcp/integration-testing/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.

agentmods 80×15 button for integration-testing

Your own site · 80×15
<a href="https://agentmods.dev/skills/s-morgan-jeffries/omnifocus-mcp/integration-testing"><img src="https://agentmods.dev/badge/skills/s-morgan-jeffries/omnifocus-mcp/integration-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 73 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,310 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00073 $0.01310
Opus 5 $0.00036 $0.00655
Sonnet 5 $0.00015 $0.00262
Haiku 4.5 $0.00007 $0.00131

Measured 9d ago against content hash ad84e3286b75, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

integration-testing 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.

.claude/skills/integration-testing/SKILL.md · 166 lines

How it starts

The opening of the file, as written. The whole thing — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.

OmniFocus Integration Testing

Unit tests in this project mock AppleScript execution. This is fast but dangerous — mocked tests cannot catch AppleScript-level bugs. Integration tests run against a real OmniFocus instance and have caught critical bugs that unit tests missed.

Why Integration Tests Matter Here

The elifintervalDays story: A variable naming typo in AppleScript went undetected by 400+ unit tests because they mocked run_applescript(). The AppleScript was syntactically valid Python-side, but at runtime, AppleScript interpreted elifintervalDays as something unexpected. Only integration tests against real OmniFocus caught it.

Classes of bugs only integration tests catch:

  • Variable naming conflicts with OmniFocus properties (see applescript-omnifocus skill)
  • AppleScript syntax that's valid but produces wrong results
  • OmniFocus version-specific behavior changes
  • Timing issues with AppleScript execution
  • Rich text handling inconsistencies
  • Recurring task completion behavior differences

Test Database Setup

Integration tests use a separate OmniFocus database to prevent production data corruption.

Initial Setup

# Create test database in OmniFocus
# File > New Database > name it "OmniFocus-TEST"

# Set environment variables
export OMNIFOCUS_TEST_MODE=true
export OMNIFOCUS_TEST_DATABASE=OmniFocus-TEST.ofocus

# Generate test fixtures
./scripts/setup_test_database.sh

Switching Databases

# Switch to test database (sets env vars, switches OmniFocus)
./scripts/local/switch_to_test_db.sh

# Switch back to production
./scripts/local/switch_to_prod_db.sh

Cleaning Up

# Remove test data (keeps database)
./scripts/cleanup_test_data.sh

Running Integration Tests

# All integration tests
make test-integration

# Specific test file
pytest tests/test_integration_real.py -v

# E2E tests (full MCP stack)
make test-e2e
pytest tests/test_e2e_real.py -v

Prerequisites:

  • OmniFocus must be running
  • Test database must be active (check with ./scripts/local/switch_to_test_db.sh)
  • Test fixtures must be loaded

Read the full file on GitHub · 166 lines

Changes

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.

  1. 9d ago First seen · 166 lines · 73 tokens per session scan A ad84e3286b75

Subscribe to this mod's changes

integration-testing is a skill published in the GitHub repository s-morgan-jeffries/omnifocus-mcp (7 stars, last pushed 4mo ago), licensed MIT. It adds 73 tokens to every session and 1,310 once invoked, about $0.0004 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-31.

Related

Other skills, from other repositories

blazemeter-performance-testing

Comprehensive guide for BlazeMeter Performance Testing, including load configuration, reporting, JMeter configuration, Taurus, scenarios, and advanced features. Use when working with Performance tests for (1) Configuring load settings and distribution, (2) Creating and running tests (JMeter, Browser, URL/API…

Blazemeter/bzm-mcp · 138 tokens

blazemeter-api-reference

Comprehensive reference for BlazeMeter REST APIs, including authentication, identifiers, and API endpoints. Use when working with BlazeMeter APIs for (1) Understanding BlazeMeter REST API structure, (2) Authenticating API requests, (3) Obtaining identifiers (Workspace ID, Project ID, Test ID, etc.), (4) Using Test…

Blazemeter/bzm-mcp · 109 tokens

blazemeter-private-locations

Comprehensive guide for BlazeMeter Private Locations, including Radar Agent, installation (Docker, Kubernetes, Helm), configuration, management, and troubleshooting. Use when working with Private Locations for (1) Installing agents (Docker, Kubernetes, Helm Chart), (2) Configuring Radar Agent for API Monitoring, (3)…

Blazemeter/bzm-mcp · 103 tokens

blazemeter-administration

Comprehensive guide for BlazeMeter Administration, including workspaces, projects, security, alerts, and team management. Use when working with administration for (1) Managing workspaces and projects, (2) Configuring security settings (SAML SSO, 2FA, API keys), (3) Creating workspace alerts, (4) Managing private…

Blazemeter/bzm-mcp · 111 tokens

blazemeter-functional-testing

Comprehensive guide for BlazeMeter Functional Testing, including GUI Functional Tests, API Tests (deprecated), Action Library, and debugging. Use when working with Functional Testing for (1) Creating GUI Functional Tests (YAML, Java IDE, Python IDE), (2) Managing Functional Tests (duplicate, delete, move, rename), (3)…

Blazemeter/bzm-mcp · 124 tokens

blazemeter-getting-started

Getting started guides for BlazeMeter, including onboarding, migration guides, continuous testing journey, glossary, and mobile testing. Use when getting started with BlazeMeter for (1) Navigating BlazeMeter University onboarding, (2) Migrating from Runscope or JMeter, (3) Understanding the continuous testing journey…

Blazemeter/bzm-mcp · 96 tokens