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.
git clone --depth 1 https://github.com/GktuOktay/ai-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/rules/gktuoktay/ai-skills/copywriting)<a href="https://agentmods.dev/rules/gktuoktay/ai-skills/copywriting"><img src="https://agentmods.dev/badge/rules/gktuoktay/ai-skills/copywriting/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/rules/gktuoktay/ai-skills/copywriting"><img src="https://agentmods.dev/badge/rules/gktuoktay/ai-skills/copywriting.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.00000 | $0.00696 |
| Opus 5 | $0.00000 | $0.00348 |
| Sonnet 5 | $0.00000 | $0.00139 |
| Haiku 4.5 | $0.00000 | $0.00070 |
Grade A, and why
copywriting 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 6d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI/UX Copywriting Guidelines
This skill focuses on writing effective microcopy for user interfaces, marketing assets, and onboarding flows. Good copy guides the user seamlessly while reflecting the brand's personality.
1. Tone of Voice
Our tone is Friendly, Professional, and Concise.
- Friendly: Welcoming, helpful, and empathetic, especially when things go wrong.
- Professional: Authoritative without being overly formal. We know what we are doing.
- Concise: Respect the user's time. Say more with fewer words.
2. Writing Clear CTAs (Calls to Action)
CTAs should clearly indicate what will happen when the user clicks.
- Use strong verbs: Start with an action word (e.g., Get, Create, Save, Subscribe).
- Be specific: Avoid generic terms if a more descriptive term fits.
- Bad: Submit, Click Here, OK
- Good: Create Account, Send Message, Save Changes
- Keep it short: Aim for 2-4 words.
3. Handling Error Messages
Error messages should never blame the user. They must explain what went wrong and how to fix it.
- Be empathetic: Avoid aggressive words like "Failed," "Prohibited," or "Illegal."
- Provide a solution: Tell the user what to do next.
- Examples:
- Bad: Invalid password. Try again.
- Good: Your password needs to be at least 8 characters long.
- Bad: System error 404.
- Good: We couldn't find that page. Let's get you back to the home page.
4. Designing Empty States
Empty states are opportunities to educate and encourage action, not dead ends.
- Explain the value: Tell the user what goes here and why they should care.
- Provide an action: Always include a CTA to help them get started.
- Example (Empty Inbox):
- Headline: You're all caught up!
- Body: When you receive new messages, they'll appear right here.
- CTA: Browse Contacts
5. Onboarding Copy
Onboarding should highlight value, not just explain features.
- Focus on benefits: Explain why a feature matters, not just how it works.
- Keep it digestible: One concept per screen/tooltip.
- Allow skipping: Respect users who prefer to explore independently.
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.
- 6d ago First seen · 69 lines · 696 tokens per session scan A 2419b16b982e
copywriting is a cursor rule published in the GitHub repository GktuOktay/ai-skills (2 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 696 tokens. 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 cursor rules, from other repositories
figma-translator
Translate any technical specification into five precise, self-contained Figma Make prompts ready to paste and generate.
canonical__hhadcn-ui
Cursor rule "canonical__hhadcn-ui" from Bilal140202/the-lord-of-the-skills, covering shadcn/ui best practices, installation, initial setup, initialize shadcn/ui in your project and add components as needed.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.