What is claude-skill-registry-core CLAUDE.md?

Repository instructions for a three-repository skill registry. They explain which repository owns source files, archived skill data, and the combined published output.

Choosing where to edit workflows, registry data, generated search indexes, documentation, and publishing code.

They prevent edits being made in generated files or in the wrong repository. This keeps the source of truth and publishing process consistent.

How majiayu000/claude-skill-registry-core configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to majiayu000/claude-skill-registry-core. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/majiayu000/claude-skill-registry-core/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/majiayu000/claude-skill-registry-core

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/majiayu000/claude-skill-registry-core/claude-md/github.svg)](https://agentmods.dev/instructions/majiayu000/claude-skill-registry-core/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/majiayu000/claude-skill-registry-core/claude-md"><img src="https://agentmods.dev/badge/instructions/majiayu000/claude-skill-registry-core/claude-md/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/majiayu000/claude-skill-registry-core/claude-md"><img src="https://agentmods.dev/badge/instructions/majiayu000/claude-skill-registry-core/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 555 This file is loaded in full into every session.

When invoked 555 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 100% copy Near-identical to another mod in the catalogue.

Token cost

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.00555	$0.00555
Opus 5	$0.00278	$0.00278
Sonnet 5	$0.00111	$0.00111
Haiku 4.5	$0.00056	$0.00056

Measured 12d ago against content hash a4f597f80a28, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

claude-skill-registry-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 12d 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.

Origin

This is a copy

100% identical to claude-skill-registry CLAUDE.md — 0 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.

CLAUDE.md · 36 lines

How it starts

The opening of the file, as written. The whole thing — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md

This project is a three-repo split. Before editing anything, identify which repo you are in and route the change to the owner repo instead of patching generated outputs in the wrong place.

Repo Map

claude-skill-registry-core: source of truth for discovery, download, dedupe, security scanning, registry/search-index generation, Pages, and publish orchestration.
claude-skill-registry-data: archive repo. Canonical layout is <category>/<skill>/SKILL.md + <category>/<skill>/metadata.json at category folders in the repo root.
claude-skill-registry: merged publish artifact. It is rebuilt from pinned core_sha + data_sha; it is not where canonical pipeline behavior should be invented.

How To Decide Where To Edit

Touch core for workflows, scripts, pipeline docs, registry/search-index generation, Pages behavior, or publish orchestration.
Touch data for archived skill bodies, archive-only README/counts, or fixes to files that exist only in the archive.
Touch main only for main-owned wiring that core/scripts/sync_main_repo.sh intentionally excludes from sync. Current exceptions are .github/workflows/publish-from-core.yml, .github/workflows/metadata-compliance.yml, and .github/workflows/sync-data.yml (deprecated stub).

Generated vs Owned Files In Main

Treat these as generated in main and do not hand-edit them:

skills/**
registry.json
registry_summary.json
docs/search-index.json
docs/stats.json
docs/categories/**
pipeline scripts copied from core

Publish Flow

core/.github/workflows/sync-data.yml discovers/downloads skills and updates data.
core rebuilds registry metadata and commits its own outputs.
core/.github/workflows/build-index.yml rebuilds site/search artifacts and deploys Pages.
core dispatches main/.github/workflows/publish-from-core.yml with pinned core_sha and data_sha.
main rebuilds the merged artifact from those pinned refs and records them in provenance/merge-source.json.

Read the full file on GitHub · 36 lines

Changes

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.

12d ago First seen · 36 lines · 555 tokens per session scan A a4f597f80a28

Subscribe to this mod's changes

claude-skill-registry-core CLAUDE.md is an instructions file published in the GitHub repository majiayu000/claude-skill-registry-core (23 stars, last pushed yesterday), licensed MIT. It adds 555 tokens to every session, about $0.0028 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to claude-skill-registry CLAUDE.md, differing in 0 lines, and is treated as a copy.

Claude Code ai-skills automation codex github-pages search-index

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.

vercel/next.js · 7,296 tokens

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.

openai/codex · 5,153 tokens

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).

microsoft/vscode · 6,785 tokens

claude-skill-registry-core: Instructions file for Claude Code