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 ZachArticulateV/designer-pro-and-seo --skill content-draftgit clone --depth 1 https://github.com/ZachArticulateV/designer-pro-and-seoWrote 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/zacharticulatev/designer-pro-and-seo/content-draft)<a href="https://agentmods.dev/skills/zacharticulatev/designer-pro-and-seo/content-draft"><img src="https://agentmods.dev/badge/skills/zacharticulatev/designer-pro-and-seo/content-draft/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/zacharticulatev/designer-pro-and-seo/content-draft"><img src="https://agentmods.dev/badge/skills/zacharticulatev/designer-pro-and-seo/content-draft.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.00086 | $0.00647 |
| Opus 5 | $0.00043 | $0.00324 |
| Sonnet 5 | $0.00017 | $0.00129 |
| Haiku 4.5 | $0.00009 | $0.00065 |
Grade A, and why
content-draft 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
content-draft
Family: content-and-data Status: Stable
Purpose
Turn a brief or outline into an actual first draft — the production counterpart to
the analysis skills. Fills the hole between seo-content-brief (which plans) and
seo-content (which audits): neither writes the content. This does, on-intent and
structured for both human readers and AI-search citability.
Triggers
- "draft this" / "first draft"
- "write the blog post" / "write the page" / "write this guide"
- "turn this brief into content"
Inputs
- A brief or outline (from
seo-content-brief, or pasted) — or just a topic + target keyword + intent - Audience and search intent
- Tone / brand voice (or pull from a design system)
- Target length / section structure
Steps
- Confirm intent and structure. Restate the search intent and the section outline (use the brief's per-section word counts if available).
- Draft section by section. Open with a direct answer to the query (good for readers and AI Overviews), then develop each section. Make each paragraph one clear, source-able claim.
- Weave keywords naturally — primary in title/H1/intro, related terms across sections; never stuff.
- Add structure for citability — descriptive H2/H3s, lists/tables where they aid scanning, a short TL;DR, and FAQ where intent is question-led.
- Originality + accuracy pass. Remove generic-AI phrasing; mark any factual
claim that needs a source with
[cite]so the human editor can verify. - Hand off to
seo-content(E-E-A-T audit) andseo-page(on-page checks) before publishing. Always label output as a first draft for human edit.
Outputs
- A structured first draft matching the brief
[cite]markers on claims that need verification- A short list of what a human editor should confirm (facts, brand specifics)
Dependencies
- None required (pure method). Composes with
seo-content-brief(upstream),seo-content+seo-page(downstream review).
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 · 64 lines · 86 tokens per session scan A df883c32bc97
content-draft is a skill published in the GitHub repository ZachArticulateV/designer-pro-and-seo (8 stars, last pushed 2mo ago), licensed MIT. It adds 86 tokens to every session and 647 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
designlang-tokens
Use when styling UI for cal.com — references the extracted design system tokens instead of inventing colors, spacing, or typography.
stakeholder-brief
Write a one-page stakeholder brief translating design system health or status into business language. Trigger when someone says: stakeholder update, exec brief, leadership summary, status report for leadership, system status for non-designers, write a brief for the business, or anything about communicating design…
token-audit
Audit a design system's token definitions for naming violations, missing semantic tiers, and structural debt. This audits how tokens are defined and organised, NOT how they are consumed in code. Trigger when someone says: audit my tokens, token naming review, are my tokens consistent, token health check, review my…
governance-encoder
Convert governance policies into machine-executable JSON constraint files that AI agents and CI pipelines validate against automatically. This produces rule engine files in .ai/governance/, NOT narrative decision records or documentation. Trigger when someone says: encode governance rules, governance as code, automate…
cicd-integration
Generate CI/CD pipeline configurations that automate design system quality checks — token validation, component linting, visual regression, accessibility scanning, and release gating. Produces ready-to-use pipeline files for GitHub Actions, GitLab CI, CircleCI, or Bitbucket Pipelines, configured to enforce the…
codebase-index
Generate a pre-computed component index from a design system codebase — YAML infrastructure files containing a component inventory, relationship graph, and summary statistics that AI agents and MCP servers consume. This produces machine-readable index files in .ai/index/, NOT a health report or quality assessment.…