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 instructions/adologyai/content-intelligence-plugin/claude-mdgit clone --depth 1 https://github.com/adologyai/content-intelligence-pluginWrote 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/instructions/adologyai/content-intelligence-plugin/claude-md)<a href="https://agentmods.dev/instructions/adologyai/content-intelligence-plugin/claude-md"><img src="https://agentmods.dev/badge/instructions/adologyai/content-intelligence-plugin/claude-md.svg" alt="Measured on agentmods" 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 | $0.00708 | $0.00708 |
| Opus 5 | $0.00354 | $0.00354 |
| Sonnet 5 | $0.00142 | $0.00142 |
| Haiku 4.5 | $0.00071 | $0.00071 |
Grade A, and why
content-intelligence-plugin CLAUDE.md 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
What this repo is
This is a Claude Code plugin (content-intelligence), not an application. It ships three things to AI agents — skills, slash commands, and an MCP server reference — plus the manifests and tooling to package and release them.
The MCP server is remote and hosted (https://mcp.adologyai.com/mcp, OAuth 2.1 via Stytch). The ~27 MCP tools live server-side and are not in this repo. There is nothing to build or run locally for the server — .mcp.json just points at the hosted endpoint. This repo is the distributable plugin package only.
This is a public repository. Do not put internal references (Slack links, ticket URLs, private channel names, internal threads) in commits, PR titles/bodies, issues, or committed files.
Layout
.claude-plugin/plugin.json+marketplace.json— plugin + marketplace manifests (validated as JSON in CI)..mcp.json— points the plugin at the remote MCP server.skills/*/SKILL.md— domain skills (markdown with---frontmatter; many havereferences/,assets/, orscripts/subdirs). This is where most of the substance lives.commands/*.md— slash commands (thin entrypoints that lean on the skills).scripts/—sync-versions.mjs(version propagation) andexport-plugin.sh(build the.zip);*.test.mjsare the only unit tests.docs/— user-facing install + reference docs.INSTALL.md/SUBMISSION*.mdat root are customer/registry-facing.
Commands
npm test # node --test scripts/*.test.mjs (the only test suite)
node --test scripts/sync-versions.test.mjs # run a single test file
npm run changeset # add a changeset (required for any release-cutting PR)
npm run version # apply changesets + sync versions across manifests
./scripts/export-plugin.sh # build dist/*.zip (version from plugin.json)
./scripts/export-plugin.sh --preview # PR preview build (suffixed with PR + SHA)
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 · 45 lines · 708 tokens per session scan A 34d29e7f1eb8
content-intelligence-plugin CLAUDE.md is an instructions file published in the GitHub repository adologyai/content-intelligence-plugin (2 stars, last pushed 29d ago), licensed Apache-2.0. It adds 708 tokens to every session, about $0.0035 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.