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 mrstev3n/balise-skills --skill balise-affinitygit clone --depth 1 https://github.com/mrstev3n/balise-skillsWrote 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/mrstev3n/balise-skills/balise-affinity)<a href="https://agentmods.dev/skills/mrstev3n/balise-skills/balise-affinity"><img src="https://agentmods.dev/badge/skills/mrstev3n/balise-skills/balise-affinity/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/mrstev3n/balise-skills/balise-affinity"><img src="https://agentmods.dev/badge/skills/mrstev3n/balise-skills/balise-affinity.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.00550 |
| Opus 5 | $0.00036 | $0.00275 |
| Sonnet 5 | $0.00015 | $0.00110 |
| Haiku 4.5 | $0.00007 | $0.00055 |
Grade A, and why
balise-affinity 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 11d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Affinity Design Literacy
Use this skill for Affinity reasoning before automation. It helps choose the right Affinity concept, object type, workflow, and verification method. It is complementary to balise-affinity-mcp, which executes changes through the MCP.
Core Posture
Treat Affinity as a unified creative environment with vector, pixel, and layout capabilities in one document. Before recommending an action, identify the user's intent:
- create or edit vector artwork
- retouch or manipulate pixels
- structure a layout or publication
- build reusable design systems
- prepare exportable assets
- diagnose a visual or UI-state issue
- automate through MCP
Do not reduce Affinity work to poster recreation. Posters are only one possible composition use case.
Reference Routing
- Read
references/affinity-mental-model.mdfor architecture, Studios, object model, and workflow decisions. - Read
references/affinity-decision-matrix.mdfor concrete object and verification choices. - If the answer requires live document manipulation, switch to
balise-affinity-mcpand follow its SDK-first workflow.
Reasoning Rules
- Separate what is artwork from what is Affinity UI state.
- Prefer non-destructive workflows unless final flattening is explicitly requested.
- Prefer reusable systems for repeated design elements: symbols, text styles, global colors, assets, and named groups.
- Choose text mode deliberately: Artistic Text for display fragments, Frame Text for layout containers.
- Use artboards/pages/spreads for variants, screen states, and multi-page work instead of separate files when a shared system matters.
- Treat exact feature names, AI tools, shortcuts, and version-specific behavior as verify-first details.
- When the user wants a detailed synthesis, prefer HTML over long Markdown.
Output Expectations
For audits or strategy:
- classify findings by concept area
- explain practical impact
- recommend the safest Affinity-native approach
- identify what should be verified through MCP or visual render
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.
- 11d ago First seen · 61 lines · 73 tokens per session scan A 5ec68523d925
balise-affinity is a skill published in the GitHub repository mrstev3n/balise-skills (11 stars, last pushed 22d ago), licensed Apache-2.0. It adds 73 tokens to every session and 550 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-30.
Other skills, from other repositories
ijfw-ui-spec
Use when the user says: 'ui spec', 'design contract', 'ui audit setup', 'lock the design', 'visual contract', 'ui review setup', or '/ijfw-ui-spec'. Produces UI-SPEC.md as the visual design contract before any frontend or visual-artifact build, and dispatches ijfw-ui-auditor as the final 6-pillar gate.
ijfw-design
Use when the user says: 'design', 'redesign', 'UI', 'UX', 'dashboard', 'page', 'component', 'make it look better', 'polish', 'pretty', 'professional', 'user experience', 'layout', 'visual', 'accessibility', 'colors', 'typography', 'brand'.
Add Claude design-system and accessibility workflows with UX/UI Agent Skills
Use UX/UI Agent Skills when Claude should generate tokens, component specs, accessibility audits, and framework-specific UI code from a repeatable design workflow.
design-maker
name: design-maker description: Used when the Design Brief is complete and the user needs to generate mockups. Reads Product-Spec.md and Design-Brief.md, then generates a complete set of design deliverables through a design tool MCP, including all pages, state variants, component specifications, design tokens…
design-brief-builder
name: design-brief-builder description: Used when the user wants to define a design style or visual direction, or says something vague like 'I want a premium/sleek/modern look'. Guides the user through a design interview to clarify visual preferences and outputs Design-Brief.md. After Brief is saved, MUST run Next…
ui-designer
Designs and builds interface work on top of the design system the repo already has: layout, spacing, hierarchy, interaction states, and accessible defaults, with creativity calibrated to the surface instead of an unrequested redesign. Use when asked for a new screen, a redesign, empty, loading, and error states, or to…