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-initnpx skills add Contentrain/ai --skill contentrain-initgit 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.00032 | $0.00964 |
| Opus 5 | $0.00016 | $0.00482 |
| Sonnet 5 | $0.00006 | $0.00193 |
| Haiku 4.5 | $0.00003 | $0.00096 |
Grade A, and why
contentrain-init 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 2d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Initialize Contentrain in a Project
Set up Contentrain content infrastructure in an existing project.
When to Use
The user wants to add Contentrain to their project, or says something like "set up contentrain", "initialize contentrain", "add content management".
Steps
1. Detect the Tech Stack
Read package.json to identify the framework:
| Dependency | Stack |
|---|---|
nuxt |
Nuxt 3 |
next |
Next.js |
@astrojs/astro or astro |
Astro |
@sveltejs/kit |
SvelteKit |
If none match, treat as a generic Node.js project. Report the detected stack to the user before proceeding.
2. Ask for Configuration
Ask the user for:
- Supported locales: Which languages will the project support? Default:
["en"]. Use ISO 639-1 codes. - Source locale: Which locale is the primary/source locale? Default:
"en". - Domain names: Suggest domains based on the project structure (e.g.,
marketing,blog,app,docs). Ask the user to confirm or modify.
3. Initialize the Project
Call the MCP tool:
contentrain_init(stack: "<detected>", locales: ["en", ...], domains: ["marketing", ...])
This creates the .contentrain/ directory structure, config.json, and initial context.json.
4. Analyze Project Conventions
After initialization, review the project for conventions to inform content creation:
- Tone: Analyze existing copy in the project (README, landing page, UI text) to determine the appropriate tone (e.g.,
professional,casual,technical). - Naming conventions: Note any patterns in file naming, component naming, or content structure.
Note: Do NOT manually edit
context.json. It is managed automatically by MCP tools and updated after every write operation.
5. Suggest Initial Models
Based on the project analysis, suggest models that would be useful:
- If the project has a landing page: suggest
hero(singleton),features(singleton or collection). - If the project has a blog section: suggest
blog-post(document),categories(collection),authors(collection). - If the project has UI text: suggest
ui-labels(dictionary),error-messages(dictionary).
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.
- 2d ago First seen · 117 lines · 32 tokens per session scan A e1f577c8cd62
contentrain-init is a skill published in the GitHub repository Contentrain/ai (4 stars, last pushed 2d ago), licensed MIT. It adds 32 tokens to every session and 964 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
product-ui-taste
Anti-slop skill for PRODUCT UI - dashboards, data tables, forms, multi-step flows, settings, list/detail, app shells. The agent reads the surface, budgets the frame first, and ships dense interfaces that are correct at every edge case (overflow, long labels, empty/error/loading states, i18n expansion, keyboard/a11y).…
save-progress
Save current project task progress to local task state file for cross-session continuity. Use when the user asks to save progress, uses an equivalent localized trigger phrase, the session is interrupted, or the user wants to resume work later. Writes to .claude/project-task-state.json so next session can load it via…
inclusive-design
Use when working on inclusion, i18n/localization, global name/address forms, low-end devices, slow/metered networks, affordability, or first-time/low-confidence users; not WCAG/screen readers (see accessibility).
flutter-best-practices
Use when writing, reviewing, refactoring, or planning Flutter/Dart code — screens, features, project structure, state management, folders, widgets, cubits/blocs, repositories, services, or tests.
unreal-large-blueprint-analysis
Systematically analyze and translate large UE Blueprints (10+ functions) into C++ or other targets. Use when the user asks to convert a Blueprint to C++, audit a complex Blueprint, or understand a large Blueprint's full logic.
unreal-plugin-localization
翻译 UE 插件本地化 PO 文件。当用户要求本地化、翻译或国际化 Unreal Engine 插件时使用。 处理 GatherText 采集、PO 导出、AI 翻译、PO 导入和 locres 编译的完整流程。.