claude-code-plugins CLAUDE.md

A project instruction file describing the structure, architecture, and working conventions of the Edge Delta official Claude Code plugin marketplace.

In plain words
What is it for?
Use it when developing or reviewing the marketplace, its plugins, their skills, and related configuration files.
Why use it?
It gives a coding agent the repository context needed to make changes that fit the project.

Instructions file

Install

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.

agentmods
npx agentmods add instructions/edgedelta/claude-code-plugins/claude-md
Clone the repo
git clone --depth 1 https://github.com/edgedelta/claude-code-plugins
Per session 846 This file is loaded in full into every session.
When invoked 846 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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.

ModelPer sessionOnce invoked
Fable 5 $0.00846 $0.00846
Opus 5 $0.00423 $0.00423
Sonnet 5 $0.00169 $0.00169
Haiku 4.5 $0.00085 $0.00085

Measured yesterday against content hash 250c18fa1309, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

claude-code-plugins 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 yesterday.

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.

CLAUDE.md · 65 lines

How it starts

The opening of the file, as written. The whole thing — 65 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.

Project Overview

This is the Edge Delta Official Plugins marketplace — a collection of Claude Code plugins that provide AI-powered observability automation for EdgeDelta customers. The repository is published as a Claude Code plugin marketplace at edgedelta/claude-code-plugins.

Repository Structure

.claude-plugin/marketplace.json    # Marketplace manifest (lists all plugins)
plugins/
  edgedelta-ottl/                  # OTTL function reference (124 functions)
  edgedelta-pipelines/             # Pipeline creation, validation, deployment
  edgedelta-reference/             # Component reference (sources/processors/destinations)
  edgedelta-teammates/             # AI teammate configuration
  edgedelta-workflows/             # Workflow automation configs
  edgedelta-docker-image/          # Custom agent Docker images + SELinux

Each plugin follows the same internal layout:

plugins/<name>/
  .claude-plugin/plugin.json       # Plugin manifest (name, version, description, skills list)
  skills/<name>/
    SKILL.md                       # Main skill file (frontmatter + instructions)
    references/                    # Reference docs loaded by the skill
    assets/                        # Templates, scripts, examples (pipelines plugin)

Architecture

Marketplace manifest (.claude-plugin/marketplace.json): Central registry listing all plugins with version, description, source path, category, and tags. Each plugin entry's source field points to its directory under plugins/.

Plugin manifests (plugins/<name>/.claude-plugin/plugin.json): Each plugin declares its own metadata and a skills array pointing to skill directories. Currently all plugins expose exactly one skill.

Skills are the core component type used — markdown files with YAML frontmatter (name, version, description, dependencies) that Claude auto-invokes based on context matching. The description field in both plugin.json and SKILL.md frontmatter is critical for triggering — it must contain the phrases users would say.

Read the full file on GitHub · 65 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.

  1. yesterday First seen · 65 lines · 846 tokens per session scan A 250c18fa1309

Subscribe to this mod's changes

claude-code-plugins CLAUDE.md is an instructions file published in the GitHub repository edgedelta/claude-code-plugins (2 stars, last pushed 5mo ago), licensed MIT. It adds 846 tokens to every session, about $0.0042 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-31.

Related

Other instructions, from other repositories

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,182 tokens

buildNext

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

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.

vercel/next.js · 7,296 tokens

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

microsoft/vscode · 5,001 tokens

spec-kit 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.

github/spec-kit · 7,040 tokens

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

langchain-ai/langchain · 4,345 tokens