Borrowing it
Nothing to install: this file belongs to datathings/marketplace. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/datathings/marketplace/main/CLAUDE.mdgit clone --depth 1 https://github.com/datathings/marketplaceWrote 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/datathings/marketplace/claude-md)<a href="https://agentmods.dev/instructions/datathings/marketplace/claude-md"><img src="https://agentmods.dev/badge/instructions/datathings/marketplace/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.1 | $0.00915 | $0.00915 |
| Opus 5 | $0.00458 | $0.00458 |
| Sonnet 5 | $0.00183 | $0.00183 |
| Haiku 4.5 | $0.00092 | $0.00092 |
Grade A, and why
marketplace 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 6d 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 — 111 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.
Repository Overview
This is the Datathings Marketplace - a Claude Code plugin marketplace providing skills and LSP plugins for GreyCat development and local LLM inference.
Architecture
The marketplace follows a two-level structure:
- Marketplace level (
.claude-plugin/marketplace.json) - registry of all plugins - Plugin level (
plugins/<name>/) - individual skill or LSP plugins
Plugin Types
Skill Plugins (greycat, greycat-c, llamacpp):
skills/<name>/SKILL.md- entry point with YAML frontmatter (name,description)skills/<name>/references/- detailed docs loaded on-demandpackage.sh- creates.skilldistribution (zip with .skill extension)
LSP Plugins (greycat-lsp):
lspServersinplugin.json- LSP server configuration (command, args, transport)- Requires
greycat-langbinary in PATH
Commands
Package skills
./package.sh # Interactive skill selection
./package.sh -a # Package all skills to ./skills/
./package.sh greycat # Package a specific skill by name
./package.sh -s llamacpp # Same as above (explicit flag)
./package.sh -c -a # Clean existing before packaging all
./package.sh -o /output/dir -a # Custom output directory
Update skills (sync with upstream libs)
Maintenance commands live at the marketplace root in .claude/commands/:
/update-greycat # Sync greycat skill with latest library versions
/update-greycat-c # Update C SDK documentation
/update-llamacpp # Sync with upstream llama.cpp release
These are repo maintenance workflows, not distributed with the skills.
Create new skill
.claude/skills/skill-creator/scripts/init_skill.py <skill-name> --path <output-dir>
Bump versions
./bump-version.sh # Show current versions
./bump-version.sh 1.3.0 # Bump all plugins to 1.3.0
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.
- 6d ago First seen · 111 lines · 915 tokens per session scan A 878a530cc320
marketplace CLAUDE.md is an instructions file published in the GitHub repository datathings/marketplace (11 stars, last pushed 9d ago), licensed Apache-2.0. It adds 915 tokens to every session, about $0.0046 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
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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 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).
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.
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.