toolshed: Instructions file for Claude Code

CLAUDE.md

toolshed CLAUDE.md is an instructions file for Claude Code from knitli/toolshed. It costs 2,552 tokens per session, scanned A, original, MIT.

Project instructions for Toolshed, a marketplace that packages multiple Claude Code add-ons in one repository.

In plain words
What is it for?
They are for maintaining plugin files, marketplace metadata, versions, and the repository's validation workflow.
Why use it?
They explain how the repository is organized and how to validate it and keep its version information synchronized.

Instructions file for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable. Also seen: mentions .claude-plugin; mentions CLAUDE.md; mentions subagents.

This is knitli/toolshed's own configuration. It tells Claude Code how to work on toolshed itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything toolshed configures →

Runs only inside a plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else, and the catalogue could not identify which plugin ships it.

Reuse

Borrowing it

Nothing to install: this file belongs to knitli/toolshed. 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/knitli/toolshed/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/knitli/toolshed

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.

agentmods badge for toolshed CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/knitli/toolshed/claude-md/github.svg)](https://agentmods.dev/instructions/knitli/toolshed/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/knitli/toolshed/claude-md"><img src="https://agentmods.dev/badge/instructions/knitli/toolshed/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.

agentmods 80×15 button for toolshed CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/knitli/toolshed/claude-md"><img src="https://agentmods.dev/badge/instructions/knitli/toolshed/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2,552 This file is loaded in full into every session.
When invoked 2,552 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 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.1 $0.02552 $0.02552
Opus 5.5 $0.01021 $0.01021
Sonnet 5.5 $0.00510 $0.00510
Haiku 4.5 $0.00255 $0.00255

Measured 1mo ago against content hash 2eb4d1cce4fb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

toolshed 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 1mo 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.

CLAUDE.md · 149 lines

How it starts

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

What this is

Toolshed is a Claude Code plugin marketplace monorepo (knitli/toolshed). It packages multiple plugins for installation from a single source. Users add the marketplace with /plugin marketplace add knitli/toolshed and install individual plugins by name.

Commands

bun run validate          # Run marketplace validation (structure, JSON, version sync)

packages/openapi-mcp is a compiled TypeScript package with Bun tests, Node transport/stdio tests, and Biome checks. Its build and package-consumer checks are:

bun run --cwd packages/openapi-mcp build
bun test packages/openapi-mcp
bun run --cwd packages/openapi-mcp test:node-transport
bun run --cwd packages/openapi-mcp test:node-stdio
bun scripts/generate.mts --check

Architecture

Plugin logic is markdown prompts interpreted by Claude Code at runtime. The separate packages/openapi-mcp package compiles OpenAPI catalogs and serves MCP through a local Node adapter; it has portable runtime/conformance exports and Node compiler/SQLite/stdio exports. See its README for artifact format 5, runtime contract 1, prepared-call format 2, and pending publication/D1 gates.

Version sync

Each plugin's package.json is the source of truth for that plugin's version — semantic-release bumps it on merge to main. The generate script reads the version from package.json and propagates it to plugin.json.

The marketplace version follows the same pattern at the repo root: package.json.version at repo root → marketplace.json.metadata.version, with semantic-release driven by .releaserc.json (generated). The release workflow runs bun scripts/generate.mts after each release to keep all mirrors in sync.

Release routing — scope is authoritative

Release routing is driven entirely by commit scope, not file paths. semantic-release-monorepo is not used. Each plugin's package.json.release uses @semantic-release/commit-analyzer releaseRules gated on its own scope, with a catchall { "release": false } that short-circuits the preset defaults. The marketplace release config at .releaserc.json does the same for scope marketplace. All release configs are fully generated by scripts/generate.mts; don't hand-edit.

Read the full file on GitHub · 149 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. 1mo ago Changed · +13 lines · +143 tokens per session 2eb4d1cce4fb
  2. 1mo ago Changed · +3 lines · +62 tokens per session 20da01f17dd9
  3. 1mo ago First seen · 133 lines · 2,347 tokens per session scan A 0c68b0b4240a

Subscribe to this mod's changes

toolshed CLAUDE.md is an instructions file published in the GitHub repository knitli/toolshed (1 stars, last pushed today), licensed MIT. It adds 2,552 tokens to every session, about $0.0102 per session on Opus 5.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

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 · 9,649 tokens

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,257 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, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

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

microsoft/vscode · 2,731 tokens

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.

deepseek-ai/deepseek-harness · 4,159 tokens