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/contentrain/ai/contentrain-qualitynpx skills add Contentrain/ai --skill contentrain-qualitygit clone --depth 1 https://github.com/Contentrain/aiWhat 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.00034 | $0.01589 |
| Opus 5 | $0.00017 | $0.00794 |
| Sonnet 5 | $0.00007 | $0.00318 |
| Haiku 4.5 | $0.00003 | $0.00159 |
Grade A, and why
contentrain-quality 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contentrain Quality
Quality rules govern how AI agents create, edit, and review content in Contentrain projects. These rules ensure every piece of content meets standards for writing quality, SEO, accessibility, and media optimization before publication.
Quick Checklist
Before committing any content, verify all of the following:
- Heading hierarchy is sequential (H1 -> H2 -> H3, no skips)
- Exactly one H1 per page
- Title is 50-60 characters, primary keyword within first 30 chars, unique
- Description is 120-160 characters, complete sentence, unique, differs from title
- No placeholder text anywhere (no Lorem ipsum, TODO, TBD, [insert here])
- No duplicate content across entries in the same collection
- Tone matches
context.json > conventions.toneconfiguration - All terms match
vocabulary.json(canonical terms, brand terms, no forbidden terms) - All field constraints (length, pattern, required, unique) are satisfied
- Content follows the correct content type pattern (blog, landing page, docs, etc.)
- System fields (
id,createdAt,updatedAt,status,order) are not in write payload - Slug is lowercase, hyphenated, 3-5 words, no special characters
- All images have descriptive alt text (max 125 chars) or empty string for decorative
- OG/social fields populated if model supports them
- Media files follow naming conventions and size limits
Key Writing Rules
Heading Hierarchy
- Exactly ONE H1 per page (the page/entry title).
- Follow sequential order: H1 -> H2 -> H3 -> H4. Never skip levels.
- Every heading must have content beneath it. No empty sections.
Titles
- Length: 50-60 characters. Measure before committing.
- Place the primary keyword within the first 30 characters.
- Use action-oriented phrasing: "Build a REST API" not "REST API Overview".
- No clickbait, no ALL CAPS. Every title must be unique within its collection.
Descriptions and Excerpts
- Length: 120-160 characters. Must be a complete sentence ending with a period.
- Summarize the VALUE the reader gets, not the process of writing.
- Must differ from the title.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 188 lines · 34 tokens per session scan A 5466b94c810e
contentrain-quality is a skill published in the GitHub repository Contentrain/ai (4 stars, last pushed 3d ago), licensed MIT. It adds 34 tokens to every session and 1,589 once invoked, about $0.0002 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
etsy-category-listing
Etsy category page scraper: given an Etsy category URL (e.g. https://www.etsy.com/c/jewelry) and optional page number, returns paginated product listings with listingId, shopId, title, url, image, salePrice, originalPrice, currency, rating, reviewCount, shopName, isAd, freeShipping, badge from category and subcategory…
human-approval
Request human approval before performing a SAFETY-CRITICAL, IRREVERSIBLE, or SCOPE-EXPANDING action — submit a structured context (action, scope, risk, consequence) plus options, then STOP the current turn. The platform redispatches the agent after the human decides. NEVER use for routine deliverables (writing docs /…
firebase-analytics
Use when logging analytics events, setting user properties, configuring default event parameters, building funnels, or adding screen-view tracking.
firebase-remote-config
Use when implementing feature flags, running A/B tests, setting parameter defaults, fetching/activating config, or enabling real-time config updates.
git-master
MUST USE whenever a task needs a commit or git-history investigation. Covers atomic commits, staging, commit-message style, rebase, squash, fixup/autosquash, blame, bisect, reflog, git log -S/-G, and questions like who wrote this or when was this added. Do not use for ordinary code edits unless the user asks for git…
prismer-evolve-record
Record the outcome of applying an evolution strategy. Use after resolving an error where prismer-evolve-analyze provided a recommendation, to feed back success or failure to the network.