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-querygit 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-query)<a href="https://agentmods.dev/skills/contentrain/ai/contentrain-query"><img src="https://agentmods.dev/badge/skills/contentrain/ai/contentrain-query/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-query"><img src="https://agentmods.dev/badge/skills/contentrain/ai/contentrain-query.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.00046 | $0.01123 |
| Opus 5.5 | $0.00018 | $0.00449 |
| Sonnet 5.5 | $0.00009 | $0.00225 |
| Haiku 4.5 | $0.00005 | $0.00112 |
Grade A, and why
contentrain-query 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- contentrain-sdk — 86% identical, 94 lines differ
How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contentrain Query SDK
@contentrain/query is a Prisma-pattern generated client that provides type-safe access to Contentrain content. Generated output lives in .contentrain/client/ — never edit it manually.
Quick Start
npx contentrain generate # Generate client from models
import { query, singleton, dictionary, document } from '#contentrain'
// Collection
const posts = query('blog-post').where('category', 'eq', 'engineering').sort('published_at', 'desc').limit(10).all()
// Singleton
const hero = singleton('hero').get()
// Dictionary
const t = dictionary('ui-texts').get()
const loginLabel = t['auth.login.button']
// Document
const doc = document('blog-post').bySlug('getting-started')
Runtime API
QueryBuilder (collections)
| Method | Description |
|---|---|
.all() |
Get all entries |
.first() |
Get first entry |
.count() |
Return count of matching entries |
.where(field, value) |
Equality filter (shorthand for eq) |
.where(field, op, value) |
Operator filter: eq, ne, gt, gte, lt, lte, in, contains |
.sort(field, direction?) |
Sort (asc/desc, default asc) |
.limit(n) |
Limit results |
.offset(n) |
Skip results |
.include(relation) |
Resolve relation (1 level deep) |
SingletonAccessor
| Method | Description |
|---|---|
.get() |
Get the singleton data |
.include(relation) |
Resolve relation fields |
DictionaryAccessor
| Method | Description |
|---|---|
.get() |
Get all key-value pairs |
.get(key) |
Get single value by key |
.get(key, params) |
Get with interpolation: {placeholder} → value |
DocumentQuery
| Method | Description |
|---|---|
.all() |
Get all documents |
.bySlug(slug) |
Get document by slug |
.first() |
Get first document |
.count() |
Return count of matching documents |
.where(field, value) |
Equality filter (shorthand) |
.where(field, op, value) |
Operator filter (same ops as QueryBuilder) |
.include(relation) |
Resolve relation fields |
What ships with it
1 file 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.
- 1mo ago First seen · 130 lines · 46 tokens per session scan A 994c179a3797
contentrain-query is a skill published in the GitHub repository Contentrain/ai (6 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 1,123 once invoked, about $0.0002 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
cqrs-implementation
Implement Command Query Responsibility Segregation for scalable architectures. Use when separating read and write models, optimizing query performance, or building event-sourced systems.
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
workflow-orchestration-patterns
Design durable workflows with Temporal for distributed systems. Covers workflow vs activity separation, saga patterns, state management, and determinism constraints. Use when building long-running processes, distributed transactions, or microservice orchestration.
microservices-patterns
Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.
diagnose-backend-bug
Diagnose a bounded backend or multi-service failure from GitHub Issues, Jira, Aone, user-provided exports, logs, traces, responses, stack traces, or job records. Use when a service, API, RPC, worker, queue, CLI, or scheduled job bug needs correlation through the project's existing observability route before repair; do…
durable-objects
Build, debug, or review Cloudflare Durable Objects code for persistent state and coordination.