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 Contentrain/ai --skill contentrain-diffgit clone --depth 1 https://github.com/Contentrain/aiWrote 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/contentrain/ai/contentrain-diff)<a href="https://agentmods.dev/skills/contentrain/ai/contentrain-diff"><img src="https://agentmods.dev/badge/skills/contentrain/ai/contentrain-diff/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/contentrain/ai/contentrain-diff"><img src="https://agentmods.dev/badge/skills/contentrain/ai/contentrain-diff.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.00029 | $0.00385 |
| Opus 5.5 | $0.00012 | $0.00154 |
| Sonnet 5.5 | $0.00006 | $0.00077 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
contentrain-diff 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 1mo 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.
What it actually says
Skill: Review Pending Branches with contentrain diff
Inspect pending Contentrain branches and decide whether to merge, reject, or defer them.
When to Use
Use this when:
- the project has pending
contentrain/*branches - the user asks to review or merge changes
- branch pressure is growing and cleanup is needed
Steps
1. Check Branch Pressure
Start with contentrain status.
If many contentrain/* branches are active, move into review immediately.
2. Run contentrain diff
Use the CLI to:
- list pending branches
- inspect the diff summary
- review full patch output
3. Evaluate the Change
Check:
- which model/content files changed
- whether the change matches the intended operation
- whether validation/normalize work was completed properly
4. Choose an Outcome
- merge when the diff is correct and complete
- delete when the change is wrong or should be rejected
- defer only when more human input is required
5. Report the Decision
Summarize:
- branch reviewed
- action taken
- base branch affected
- any follow-up branch still pending
Browser Alternative
For visual branch review, use CLI serve:
contentrain serve
Navigate to http://localhost:3333/branches to see all pending branches with diffs, and merge or delete them visually.
Related Skills
- contentrain-serve — Browser-based branch review and merge
- contentrain — Core architecture and MCP tool catalog
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.
- 1mo ago First seen · 78 lines · 29 tokens per session scan A 2d1ec79f5719
contentrain-diff is a skill published in the GitHub repository Contentrain/ai (6 stars, last pushed today), licensed MIT. It adds 29 tokens to every session and 385 once invoked, about $0.0001 per session on Opus 5.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
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
chinese-commit-conventions
A Chinese-language guide to Conventional Commits, a format for writing consistent Git commit messages, plus related changelog, commit-checking, and commit-helper configuration.
managing-git
Manages Git workflows including branching, commits, and pull requests. Use when working with Git, creating commits, opening PRs, managing branches, resolving conflicts, or when asked about version control best practices.
devops/changelog-generation
A method for creating a CHANGELOG, a document that records what changed in each software release. It reads Git commit history and release-pipeline reports, then groups changes using common commit and changelog conventions.