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/sekharmalla/affinity-mcp-server/affinity-designnpx skills add sekharmalla/affinity-mcp-server --skill affinity-designgit clone --depth 1 https://github.com/sekharmalla/affinity-mcp-serverWrote 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/sekharmalla/affinity-mcp-server/affinity-design)<a href="https://agentmods.dev/skills/sekharmalla/affinity-mcp-server/affinity-design"><img src="https://agentmods.dev/badge/skills/sekharmalla/affinity-mcp-server/affinity-design.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.00069 | $0.01756 |
| Opus 5 | $0.00034 | $0.00878 |
| Sonnet 5 | $0.00014 | $0.00351 |
| Haiku 4.5 | $0.00007 | $0.00176 |
Grade A, and why
affinity-design 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 5d 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Affinity Design Workflow Skill
This skill teaches you how to orchestrate 23 MCP tools to control Affinity creative suite on macOS. The tools are low-level primitives — this skill provides the high-level workflow knowledge to combine them into real design tasks.
Affinity UI Mental Model
Understand Affinity's interface before interacting with it:
- Menu bar: File, Edit, Text, Document, Pixel, View, Window, Help — access via
affinity_get_menusandaffinity_click_menu - Toolbar: Drawing and editing tools along the left — access via
affinity_select_tool - Canvas: The central work area — interact via
affinity_mouse_actionwith screen coordinates - Panels: Right side (Layers, Color, Swatches, etc.) — inspect via
affinity_get_ui, interact viaaffinity_click_ui - Dialogs: Modal windows for export, save, preferences — inspect and interact via
affinity_get_ui+affinity_click_ui
Core Workflow Patterns
Start a Session
Always begin by checking status, launching if needed, then creating or opening a document:
- Call
affinity_statusto check if Affinity is running and see open windows - Call
affinity_launchif not running (waits 3 seconds for startup) - Call
affinity_new_documentto create a blank document, oraffinity_open_fileto open an existing file - Call
affinity_screenshotto confirm the current state visually
Navigate the Menu System
Explore menus before clicking — never guess menu item names:
- Call
affinity_get_menuswith a top-level menu name (e.g., "File", "Edit", "Pixel") to list all items - Call
affinity_get_submenufor items that have submenus (e.g., File > Export, Pixel > Filters) - Call
affinity_click_menuwith the full path array (e.g.,["File", "Export", "Export…"])
Menu paths use an array from the menu bar item down to the target item. Maximum depth is 4 levels.
Inspect and Interact with UI
When dialogs, panels, or unknown UI appears:
- Call
affinity_get_uito list all UI elements in the front window (buttons, text fields, checkboxes, etc.) - Read the output to find the element you need — note its description or title
- Call
affinity_click_uiwith the element's description/title and type (button, checkbox, text field, etc.)
What ships with it
2 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.
- 5d ago First seen · 153 lines · 69 tokens per session scan A 2d9b23d3d39b
affinity-design is a skill published in the GitHub repository sekharmalla/affinity-mcp-server (21 stars, last pushed 2mo ago), licensed MIT. It adds 69 tokens to every session and 1,756 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
apple-notes
Use this skill when the user wants to interact with Apple Notes on macOS - creating, searching, reading, updating, deleting, organizing, or formatting notes and folders. This skill provides access to Apple Notes through MCP tools and includes safe formatting guidance.
applescript-mail
Use when writing, modifying, or debugging ANY AppleScript that interacts with Apple Mail. Also use when encountering AppleScript errors, unexpected Mail.app behavior, when adding new connector methods, or when debugging JSON output from ASObjC. Covers string escaping, attachment handling, Gmail compatibility, message…
apple-mail
Use this skill when the user wants to manage Apple Mail on macOS - reading, searching, sending, replying to, forwarding, and organizing emails and mailboxes. This skill provides access to Apple Mail through MCP tools.
performance-patterns
Use when optimizing Apple Mail MCP operations, diagnosing slow queries, adding new filtering logic, or modifying how data is fetched from Mail.app. Covers osascript overhead, whose clause optimization, batch operation patterns, and known operation timings.
integration-testing
Use when setting up, running, or debugging integration tests against real Apple Mail. Also use when unit tests pass but behavior seems wrong, when adding new AppleScript operations, or when you need to understand why mocked tests are insufficient for this project.
api-design
Use BEFORE adding any new tool, parameter, or endpoint to the Apple Mail MCP server. Also use when considering API changes, evaluating feature requests, or when tempted to create a specialized operation. Contains the decision tree that prevents tool sprawl and the anti-pattern catalog.