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 seo-content-briefgit 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/seo-content-brief)<a href="https://agentmods.dev/skills/zacharticulatev/designer-pro-and-seo/seo-content-brief"><img src="https://agentmods.dev/badge/skills/zacharticulatev/designer-pro-and-seo/seo-content-brief/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/seo-content-brief"><img src="https://agentmods.dev/badge/skills/zacharticulatev/designer-pro-and-seo/seo-content-brief.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.00112 | $0.00706 |
| Opus 5 | $0.00056 | $0.00353 |
| Sonnet 5 | $0.00022 | $0.00141 |
| Haiku 4.5 | $0.00011 | $0.00071 |
Grade A, and why
seo-content-brief 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 12d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
seo-content-brief
Family: seo Status: Stable
Purpose
The production-planning side of content. Produces a brief a writer (or content-draft)
can execute: H1 + H2/H3 structure, per-section word-count guidance anchored on the
actual top-ranking pages, required entities/sub-topics, internal/external links, and
schema recommendations. Free path: analyze the competitor URLs you provide;
auto-SERP-fetch is the optional DataForSEO path.
Triggers
- "content brief" / "write a brief" / "writing brief"
- "content outline" / "outline for" / "brief for [keyword]"
- "blog brief" / "service page brief"
Inputs
- Target keyword(s) and page type (blog / service / pillar / comparison / glossary)
- Mode: new | improve (improve requires the existing URL)
- 3–10 top-ranking competitor URLs (or let DataForSEO fetch the SERP)
- Target audience
Steps
- Gather the competition. Use the provided top-ranking URLs (free path) or, if DataForSEO is configured, fetch the live SERP. Fetch each page's content.
- Extract patterns. Common H2/H3 themes, entities/sub-topics every competitor covers, average and range of word counts per section, and any gaps none cover (your differentiation angle).
- Set the structure. Recommend H1 + heading outline with a per-section word-count range (grounded in competitor averages, not a generic "1,500-word minimum").
- Specify requirements. Required entities, internal links (to/from related
pages), external authoritative citations, and schema (via
seo-schema). - Add citability guidance — note where to place specific, sourced claims so the
page is GEO-citable (see
seo-geo). - Render the brief, paste-ready for a writer or
content-draft. For improve mode, diff the existing page against the brief and list what to add/cut.
Outputs
- Structured brief (markdown): outline, per-section word counts, entities, links, schema
- For improve mode: a gap list against the existing page
Dependencies
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.
- 12d ago First seen · 65 lines · 112 tokens per session scan A c638c3d4173d
seo-content-brief is a skill published in the GitHub repository ZachArticulateV/designer-pro-and-seo (8 stars, last pushed 2mo ago), licensed MIT. It adds 112 tokens to every session and 706 once invoked, about $0.0006 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.
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…
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…
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.…
engineering-onboarding
Create an onboarding guide for an engineer joining a team that consumes the design system. Trigger when someone says: onboard new engineer, developer getting started guide, new engineer guide, engineering onboarding, first day for developers, frontend onboarding, or anything about helping an engineer new to the team…