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.
curl -O https://raw.githubusercontent.com/majiayu000/claude-skill-registry-core/main/AGENTS.mdgit clone --depth 1 https://github.com/majiayu000/claude-skill-registry-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/majiayu000/claude-skill-registry-core/agents-md)<a href="https://agentmods.dev/instructions/majiayu000/claude-skill-registry-core/agents-md"><img src="https://agentmods.dev/badge/instructions/majiayu000/claude-skill-registry-core/agents-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.
<a href="https://agentmods.dev/instructions/majiayu000/claude-skill-registry-core/agents-md"><img src="https://agentmods.dev/badge/instructions/majiayu000/claude-skill-registry-core/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.00709 | $0.00709 |
| Opus 5.5 | $0.00284 | $0.00284 |
| Sonnet 5.5 | $0.00142 | $0.00142 |
| Haiku 4.5 | $0.00071 | $0.00071 |
Grade A, and why
claude-skill-registry-core AGENTS.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.
This is a copy
100% identical to claude-skill-registry AGENTS.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.
How it starts
The opening of the file, as written. The whole thing — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Policy (Core-First)
- Core repo is the source of truth for scripts, workflows, index generation, site outputs, and pipeline docs.
- Data repo stores the archived skill tree in category-at-root layout:
<category>/<skill>/SKILL.md+<category>/<skill>/metadata.json. - Main repo is a merged publishing artifact (
core + data). During publish, the archive is read from the data checkout;main/skills/**contains frozen, non-installable legacy URL pointers. - If behavior or docs conflict across repos, follow core implementation and sync others to match.
Repo Identity Map
claude-skill-registry-core: authority repo for discovery, download, dedupe, security scan, registry generation, search-index generation, Pages, and publish orchestration.claude-skill-registry-data: archive repo for the heavy skill contents and archive-specific metadata.claude-skill-registry: merged publish artifact for browsing and compatibility consumers.
Edit Routing
- If a task touches discovery, download, dedupe, security scan, registry generation, search-index generation, Pages, or dispatch/publish logic, edit
claude-skill-registry-core. - If a task touches archived skill bodies, archive-only metadata, or archive README counts/layout, edit
claude-skill-registry-dataor letcoreworkflows update it. - If a task touches merged-artifact packaging that is intentionally main-owned, edit
claude-skill-registry. - In
main, do not directly edit generated outputs such asskills/**,registry.json,registry_summary.json,docs/search-index.json,docs/stats.json,docs/categories/**, or pipeline scripts mirrored fromcore.
Publish Contract
- Canonical flow:
core sync-data -> data commit -> core metadata commit -> core build-index -> main publish-from-core. mainshould useprovenance/merge-source.jsonto identify the exactcore_shaanddata_shathat produced the current merged artifact.- If
coreandmaindisagree, treatcoreas authoritative and re-publishmaininstead of patching generated files in place. - Main-owned workflow exceptions are intentionally excluded by
core/scripts/sync_main_repo.sh; today that is.github/workflows/publish-from-core.yml,.github/workflows/metadata-compliance.yml, and the deprecated.github/workflows/sync-data.yml.
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 Changed · +14 tokens per session fc7b4c9a73a3
- 1mo ago First seen · 37 lines · 695 tokens per session scan A 613cdf14eac9
claude-skill-registry-core AGENTS.md is an instructions file published in the GitHub repository majiayu000/claude-skill-registry-core (23 stars, last pushed yesterday), licensed MIT. It adds 709 tokens to every session, about $0.0028 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to claude-skill-registry AGENTS.md, differing in 0 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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.