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/vmobifystudio/app-dev-team/content-designnpx skills add vmobifystudio/app-dev-team --skill content-designgit clone --depth 1 https://github.com/vmobifystudio/app-dev-teamWrote 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/vmobifystudio/app-dev-team/content-design)<a href="https://agentmods.dev/skills/vmobifystudio/app-dev-team/content-design"><img src="https://agentmods.dev/badge/skills/vmobifystudio/app-dev-team/content-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.00632 |
| Opus 5 | $0.00034 | $0.00316 |
| Sonnet 5 | $0.00014 | $0.00126 |
| Haiku 4.5 | $0.00007 | $0.00063 |
Grade A, and why
content-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 today.
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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content design
The interface is mostly words. Words written last, by whoever was implementing, are the ones users actually read.
Buttons and labels
- A button says what happens when you press it.
Save changes, notOK.Delete 3 photos, notConfirm. - A destructive button names what is destroyed and whether it comes back. "This cannot be undone" belongs in the dialog, not in the button.
- Sentence case throughout. Never end a button label with a full stop.
Cancelmeans "nothing happens". Never label a buttonCancelwhen something happens.
Errors — three parts, always
- What happened, in the user's terms, not the system's.
- Whether their data is safe. This is the question they are actually asking.
- What to do next, as an action they can take right now.
Something went wrong fails all three. Couldn't save — your note is still here. Retry when you're back online. passes all three in one line. Never show an error code without also showing prose,
and never show raw exception text.
Empty states
An empty state is not a blank screen with an apology. It says what belongs here, why it is empty (new, filtered, or failed — three different states, three different messages), and the one action that fills it.
Permission prompts
Ask at the moment of need, never at launch. The prompt says what the user gets, not what the app
wants. The system string (NSCameraUsageDescription etc.) is written by you, not by an engineer at
build time — and a denied permission needs a working path, not a dead end.
The rules
- Every user-visible string goes into the localisation file from the moment it is written.
Retrofitting is far more expensive and is where hardcoded strings survive to ship (
localisation). - No placeholder text reaches a build.
Lorem ipsum,TODO,Testin a screenshot is an ASO and a review failure at once. - One term per concept, product-wide. A record is not an "item" here and an "entry" there. Keep
the list in
docs/14-components.md. - Numbers, dates, currencies and plurals are formatted by the platform's locale-aware API — never by string concatenation.
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.
- today First seen · 57 lines · 69 tokens per session scan A 74fdc33e865e
content-design is a skill published in the GitHub repository vmobifystudio/app-dev-team (4 stars, last pushed 24d ago), licensed MIT. It adds 69 tokens to every session and 632 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-09-03.
Other skills, from other repositories
fidelity-gate
Build a UI against a frozen visual reference without drift - an inventory extracted before any code, a relics list, and a gate that MEASURES computed styles on a fixture carrying the reference's own data. Use when a mockup, design spec or screenshot is the contract.
design
Create a doc-as-code design package from a PRD or SPEC. Conditionally generates C4 diagrams (Context/Container/Component), sequence diagrams, ER diagram + Data Dictionary, OpenAPI 3.0, AsyncAPI 3.0, ADRs, domain glossary, state diagrams, and deployment view as Mermaid-rendered Markdown files. Use when PM mentions…
execute-task
Implement one task (or a cohesion bundle) from a signed-off spec (Ready or Active): recompute the execution freshness gate, write the verifying test first, implement to green, run the project's full CI with adaptive retry, converge via the configured reviewsequence (default /polish --nested), then open a draft PR…
builder
Detect a project's stack and recommend or apply the universal mechanical quality guards from planwright's core catalog (formatter, linters, type-checker, test runner, secret scan, commit hooks, CI gate), plus the growable breadth dimensions. Escalates stake-bearing decisions (auth, data modeling, security posture…
spec-walkthrough
Render a spec bundle (or a chosen slice) into a plain-language, didactic comprehension artifact a human reads and judges for themselves: an unaided cold read before kickoff, re-orientation mid-execution, or onboarding to a finished or abandoned spec. Standalone and strictly read-only: it renders any status, never…
drain
Run the on-demand drain pass over every spec bundle's Gate deferral entries: evaluate structured GATE(when:) conditions, surface date and free-text gates, report malformed ones, inventory each live bundle's [manual] test-spec entries, and surface the observations log's unmined state. Read-only; nothing is…