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/lfnovo/content-core/claude-mdgit clone --depth 1 https://github.com/lfnovo/content-coreWrote 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/lfnovo/content-core/claude-md)<a href="https://agentmods.dev/instructions/lfnovo/content-core/claude-md"><img src="https://agentmods.dev/badge/instructions/lfnovo/content-core/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.02748 | $0.02748 |
| Opus 5 | $0.01374 | $0.01374 |
| Sonnet 5 | $0.00550 | $0.00550 |
| Haiku 4.5 | $0.00275 | $0.00275 |
Grade A, and why
content-core 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 4d 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Core
Library for extracting and summarizing content from URLs, files, and text.
Commands
- Install dependencies:
uv sync --group dev - Run tests:
make test(unit + integration) oruv run pytest -v - Run single test:
uv run pytest -k "test_name" - Run e2e tests:
make test-e2e(requires network + API keys) - Run all tests:
make test-all - Linting:
make ruff(runsruff check . --fix) - Build package:
uv build
CLI
content-core extract <source> [--format text|json] [--engine ENGINE]
content-core summarize [content] [--context CONTEXT]
content-core mcp
content-core config list|set|delete
For Automated Agents
If you are an automated coding agent (harny, Claude Code in headless mode, etc.) working on this repo:
Install command
uv sync --group dev
Validator command
uv run pytest tests/unit tests/integration -v
This is the gate. It returns clean pass/fail in ~15s, requires no credentials or network, and matches what CI enforces on main (CI runs only tests/unit; integration tests are also safe locally — no network/API keys). For targeted feedback during iteration, use uv run pytest -k "<keyword>" per the table in the Testing section below.
Do NOT use as gates
ruff check— available viamake ruffbut NOT enforced in CI. Including it as a validator gate would surface unaudited pre-existing findings unrelated to your task.mypy— not enforced in CI. No baseline configured. Same risk.make test-e2e/make test-e2e-heavy— require network access, API keys for LLM/STT providers, and large model downloads. Will fail in a sandboxed worktree.
If you believe a task genuinely requires lint or type cleanup, do it as a separate task with explicit scope, not as a side effect of an unrelated change.
Scope guidance
- Single processor changes (
processors/url/*.py,processors/document/*.py,processors/media/*.py) are the natural unit of work — keep changes confined to one file plus its matching test intests/unit/. - Avoid touching
extraction.py(orchestrator) orconfig.pyunless the task explicitly targets routing or configuration. - New processors should follow the
Processorprotocol insrc/content_core/processors/protocol.py.
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.
- 4d ago First seen · 217 lines · 2,748 tokens per session scan A 73252dd5ec5e
content-core CLAUDE.md is an instructions file published in the GitHub repository lfnovo/content-core (170 stars, last pushed 2d ago), licensed MIT. It adds 2,748 tokens to every session, about $0.0137 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-30.
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.