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.
curl -O https://raw.githubusercontent.com/s-morgan-jeffries/omnifocus-mcp/main/.claude/skills/integration-testing/SKILL.mdgit clone --depth 1 https://github.com/s-morgan-jeffries/omnifocus-mcpWrote 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/s-morgan-jeffries/omnifocus-mcp/integration-testing)<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.
<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>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.00073 | $0.01310 |
| Opus 5.5 | $0.00029 | $0.00524 |
| Sonnet 5.5 | $0.00015 | $0.00262 |
| Haiku 4.5 | $0.00007 | $0.00131 |
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 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 — 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
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 · 166 lines · 73 tokens per session scan A ad84e3286b75
integration-testing is a skill published in the GitHub repository s-morgan-jeffries/omnifocus-mcp (8 stars, last pushed 5mo ago), licensed MIT. It adds 73 tokens to every session and 1,310 once invoked, about $0.0003 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
opik-compare
Run a candidate against the baseline over an Opik test suite and read the numbers back — which cases broke, which got fixed, the per-metric deltas, worst rows, and whether the two runs are comparable — with the Opik compare-view link. Runs via the SDK; reads results via the MCP when connected. Does not issue a…
opik-test
Turn a failing Opik trace (or a described failure) into a repeatable regression check — a test-suite item with the trace's input and one or two binary assertions — so a fix can be verified by the compare skill. Works over the SDK; uses the MCP write tool when connected. Returns the suite, the item, and the assertion.…
opik-verify
Decide ship or hold for a candidate from the compare skill's numbers, against an explicit release policy — regressions, pass rate, safety-tagged cases, subgroup consistency, latency and cost budgets, flakiness, evidence size, and whether the judge is validated. Reads two experiments on an Opik test suite via the SDK…
qec-memory-experiment
A local simulation workflow for testing error correction in a small surface-code quantum memory. It adds a defined error rate, samples measurement results, and uses a matching decoder to estimate logical errors.
quantum-circuit-verification
A local checker for deciding whether two small OpenQASM 2 quantum circuits perform the same quantum transformation. OpenQASM 2 is a text format for describing quantum circuits.
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…