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/moasq/ios-dev-agent/content-composernpx skills add moasq/ios-dev-agent --skill content-composergit clone --depth 1 https://github.com/moasq/ios-dev-agentWrote 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/moasq/ios-dev-agent/content-composer)<a href="https://agentmods.dev/skills/moasq/ios-dev-agent/content-composer"><img src="https://agentmods.dev/badge/skills/moasq/ios-dev-agent/content-composer.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.00143 | $0.01964 |
| Opus 5 | $0.00072 | $0.00982 |
| Sonnet 5 | $0.00029 | $0.00393 |
| Haiku 4.5 | $0.00014 | $0.00196 |
Grade A, and why
content-composer 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 3d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Composer — Mobile UI Copy Rules
Every user-facing string in this app must pass this skill's rules. The point is simple, human, skimmable copy that fits a small screen and doesn't sound like a marketing template or an LLM.
The One Rule About Characters
No em-dashes (—). Ever.
LLMs love em-dashes. Humans typing on phones do not. Every — in UI copy is a tell that the text came from an AI and wasn't revised. Replace with a period, comma, or split into two sentences. The same applies to en-dashes in prose (–); keep en-dashes only for numeric ranges (3–5 min).
Other character rules:
- Ellipsis: use a real
…(U+2026), not three dots.... Use only for "in progress" indicators (Loading…). Never in button labels or headers. - Smart quotes (
""'') for prose inside cards, never in code identifiers. - Middle dot (
·) is allowed as a separator (Level 17 · Run 3). Keep it short. - No emoji in body copy. Icons belong in
Image(systemName:), not inline text.
Voice
- Second person. "You're on fire." not "The user is on fire."
- Active verbs in every CTA. "Continue drills", "Start speaking", "Retry run". Never "Continuation of drills".
- Present tense by default. "You practiced today." not "You have practiced today."
- Concrete over abstract. "3 runs to Level 18" beats "More progress awaits".
- No marketing dust. Ban: "unlock", "discover", "embark", "dive in", "journey awaits", "unleash". These are AI filler.
- No hedging. Ban: "Feel free to…", "You can now…", anything ending in "!" more than once per screen.
- No clichés. "A thousand-mile journey…", "Rome wasn't built in a day…" — kill on sight.
Length Caps (Mobile)
| Element | Max length | Example |
|---|---|---|
| Primary CTA button | 3 words, ≤ 20 chars | Continue drills |
| Secondary button | 2 words, ≤ 14 chars | Try again |
| Card title / headline | 5 words, ≤ 38 chars | Enterprise tier pre-brief |
| Card eyebrow (ALL CAPS kicker) | 3 words, ≤ 20 chars | NEXT CHALLENGE |
| Card subtitle | 1 sentence, ≤ 64 chars | 2 of 3 drills passed |
| Section header | 2–3 words | Recent activity |
| Inline toast / snackbar | 1 short sentence, ≤ 60 chars | Saved to your library |
| Empty state title | ≤ 6 words | No sessions yet |
| Empty state body | 1–2 short sentences, ≤ 120 chars | Finish a challenge to see it here. |
| Navigation title | 1–3 words | Your Journey |
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.
- 3d ago First seen · 131 lines · 143 tokens per session scan A 52a6fa234779
content-composer is a skill published in the GitHub repository moasq/ios-dev-agent (4 stars, last pushed 3mo ago), licensed MIT. It adds 143 tokens to every session and 1,964 once invoked, about $0.0007 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…