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 shalintripathi/saas-marketing-agents --skill design-opsgit clone --depth 1 https://github.com/shalintripathi/saas-marketing-agentsWrote 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/shalintripathi/saas-marketing-agents/design-ops)<a href="https://agentmods.dev/skills/shalintripathi/saas-marketing-agents/design-ops"><img src="https://agentmods.dev/badge/skills/shalintripathi/saas-marketing-agents/design-ops/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/shalintripathi/saas-marketing-agents/design-ops"><img src="https://agentmods.dev/badge/skills/shalintripathi/saas-marketing-agents/design-ops.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.00075 | $0.03691 |
| Opus 5 | $0.00037 | $0.01845 |
| Sonnet 5 | $0.00015 | $0.00738 |
| Haiku 4.5 | $0.00007 | $0.00369 |
Grade A, and why
design-ops 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 — 283 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Operations
Step 0 (always first): Load brand context
Before producing any deliverable, look for a brand-context.md file in the user's project root (also check ./.claude/brand-context.md and ./docs/brand-context.md). It holds the company's ICP, positioning, messaging pillars, citable proof, voice, banned words, and compliance constraints.
- If it exists: read it in full and treat it as binding for this run. Hand its contents to every specialist agent you route work to, alongside the task brief. Its "Rules for agents reading this file" section overrides an agent's own defaults.
- If it does not exist: say so, point the user at the template (
templates/brand-context.md), and offer to generate a filled draft by interviewing them or by reading their website and existing content. Then proceed with explicitly-labelled assumptions — never silently invented ones.
Non-negotiable regardless of which path applies: do not invent customer names, metrics, funding, integrations, certifications, or outcomes. Only proof recorded in brand-context.md (or supplied directly in the request) may be used as fact. Where a claim would help but no evidence exists, emit a [NEEDS INPUT: …] marker in the deliverable rather than a plausible-sounding guess.
What This Is
Design Operations brings together visual designers, brand strategists, and creative specialists to deliver high-impact creative assets across all B2B SaaS marketing channels. This skill orchestrates your design team to build cohesive brand experiences, from landing pages and sales presentations to ad creative and product UI. Whether you need a complete brand identity system, a data-driven infographic, a conversion-optimized landing page, or a polished sales deck, Design Operations routes your request to the right specialist and ensures consistent execution against brand standards.
The Team: 5 Specialist Agents
| # | Agent | File | What They Do |
|---|---|---|---|
| 1 | Brand Identity Strategist | agents/design-brand-identity-strategist.md |
Develops comprehensive brand systems, including visual languages, design tokens, color palettes, typography hierarchies, and brand guidelines that scale across all touchpoints |
| 2 | UI/Landing Page Specialist | agents/design-ui-landing-page-specialist.md |
Designs conversion-optimized landing pages and product UIs using data-driven layout patterns, behavioral psychology, and CRO frameworks to maximize engagement and lead capture |
| 3 | Presentation Designer | agents/design-presentation-designer.md |
Creates visually compelling and narratively coherent presentations for sales, executive briefings, investor pitches, and board meetings with data visualization and storytelling |
| 4 | Ad Creative Producer | agents/design-ad-creative-producer.md |
Produces high-performing digital ad creative optimized for platform-specific formats (LinkedIn, Google, YouTube, Instagram) with rapid testing frameworks and A/B testing discipline |
| 5 | Content Visual Designer | agents/design-content-visual-designer.md |
Transforms written content into visual formats—infographics, social media graphics, data visualizations, and visual essays—that increase engagement and shareability |
What ships with it
5 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 · 283 lines · 75 tokens per session scan A 97b8e5f024cb
design-ops is a skill published in the GitHub repository shalintripathi/saas-marketing-agents (12 stars, last pushed yesterday), licensed MIT. It adds 75 tokens to every session and 3,691 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.
Other skills, from other repositories
flame-harness-design
Phase 3 — define the Flutter designtokens.dart spec (palette, typography, spacing), the game's art/visual concept, and the asset/audio sourcing plan.
experience-baseline
Interviews the experience or UX lead about how a product behaves for the people using it — the conditions they work in, the surface states every screen must handle, the component and pattern vocabulary, the words, the accessibility floor, and the interaction budgets — and writes it up as a project experience baseline…
fabrik-validate-comment
Use when operating as the Fabrik Validate comment reviewer. This skill guides updating the validation report, re-running checks, and applying minor fixes in response to user feedback — signaling completion only when the user explicitly indicates the issue is resolved.
archify
Create architecture, workflow, sequence, data-flow, and lifecycle/state diagrams as self-contained HTML with inline SVG, dark/light themes, and PNG/JPEG/WebP/SVG export.
agentic-webdesign-webflow-mcp
Use Webflow MCP server + AI Assistant — AI agents design pages, manage CMS, run SEO/AEO audits, and generate code. Includes AEO (Answer Engine Optimization) for AI search visibility.
design-to-code
Elite render-to-code skill. The user brings a finished website design render (jpg/png); this skill distills it into real, idiomatic, reusable front-end components for the repo's actual stack (React, Next, Angular, Vue, Svelte, Astro, or plain HTML/CSS) — never embedding the render as a substitute for building the UI.…