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/datacore-one/datacore-mcp/claude-mdgit clone --depth 1 https://github.com/datacore-one/datacore-mcpWrote 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/datacore-one/datacore-mcp/claude-md)<a href="https://agentmods.dev/instructions/datacore-one/datacore-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/datacore-one/datacore-mcp/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.00206 | $0.00206 |
| Opus 5 | $0.00103 | $0.00103 |
| Sonnet 5 | $0.00041 | $0.00041 |
| Haiku 4.5 | $0.00021 | $0.00021 |
Grade A, and why
datacore-mcp 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.
This is a copy
88% identical to org-workspace CLAUDE.md — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
CLAUDE.md
datacore-mcp
TODO: Add project description, development setup, and key files.
Datacore Space Context
This project lives inside a Datacore space. Session lifecycle commands are available:
/wrap-up— write session entry to team journal, commit and push/continue— resume from yesterday's continuation notes;--savepersists current work/standup— generate/post standup from recent team journals/today— daily briefing (incremental if already generated)
| Key | Value |
|---|---|
| Space | 2-datacore |
| Journal | ~/Data/2-datacore/journal/YYYY-MM-DD.md |
| Org | ~/Data/2-datacore/org/next_actions.org |
When /wrap-up runs, use the team journal schema: ## @contributor narrative sections + ## Session Metadata YAML block.
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 · 22 lines · 206 tokens per session scan A e27b29bc49ad
datacore-mcp CLAUDE.md is an instructions file published in the GitHub repository datacore-one/datacore-mcp (0 stars, last pushed 3d ago), licensed MIT. It adds 206 tokens to every session, about $0.0010 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to org-workspace CLAUDE.md, differing in 2 lines, and is treated as a copy.
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.
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).
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.