jko-claude-plugins: Instructions file for Claude Code

CLAUDE.md

jko-claude-plugins CLAUDE.md is an instructions file for Claude Code from johnkozaris/jko-claude-plugins. It costs 832 tokens per session, scanned A, original, MIT.

A set of instructions for using jko-skills, a collection of specialised tools for several command-line coding assistants. It explains the repository layout and how to register and install the local marketplace.

In plain words
What is it for?
Use it to inspect the plugin marketplace, register a local checkout, and install plugins such as backend, SwiftUI, ESP32, or testing tools.
Why use it?
It removes guesswork when developing or installing these plugins across different coding assistants.

Instructions file for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable. Also seen: mentions Claude Code; mentions Codex; mentions OpenCode.

This is johnkozaris/jko-claude-plugins's own configuration. It tells Claude Code how to work on jko-claude-plugins 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 jko-claude-plugins 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 johnkozaris/jko-claude-plugins. 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/johnkozaris/jko-claude-plugins/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/johnkozaris/jko-claude-plugins

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 jko-claude-plugins CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/johnkozaris/jko-claude-plugins/claude-md.svg)](https://agentmods.dev/instructions/johnkozaris/jko-claude-plugins/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/johnkozaris/jko-claude-plugins/claude-md"><img src="https://agentmods.dev/badge/instructions/johnkozaris/jko-claude-plugins/claude-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 832 This file is loaded in full into every session.
When invoked 832 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.00832 $0.00832
Opus 5 $0.00416 $0.00416
Sonnet 5 $0.00166 $0.00166
Haiku 4.5 $0.00083 $0.00083

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

Security

Grade A, and why

jko-claude-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 7d 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 · 68 lines

How it starts

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

jko-skills

Multi-CLI plugin marketplace with specialized skills and integrations.

Project Structure

myClaudeSkills/
├── .github/plugin/marketplace.json    # GitHub Copilot CLI marketplace manifest
├── .claude-plugin/marketplace.json    # Symlink to the Copilot marketplace manifest
├── plugins/
│   ├── backend-architecture/           # Small cross-stack architecture guide
│   ├── code-cleanup/                  # Evidence-first dead-island and split-brain cleanup
│   ├── swiftui/                       # SwiftUI-specific judgment
│   ├── esp32-cpp/                     # ESP32 hardware/runtime judgment
│   ├── backend-validator/             # Token acquisition + HTTP/WS validation (hurl, oauth2c, websocat)
│   ├── peekaboo-macos-validator/      # macOS app UI validation via peekaboo CLI
│   ├── electron-playwright-validator/ # Electron app validation via persistent CDP session (e-cli)
│   ├── maestro-mobile-validator/      # iOS/Android flow validation via Maestro
│   └── seam-probe/                    # FFI dylib / UDS seam probing (Rust CLI built on demand)

Installing This Marketplace

# Register as a marketplace for local development
claude plugin marketplace add "$PWD"

# Then install any plugin from the local checkout
claude plugin install <plugin-name>@jko-skills

After publishing or updating the GitHub-hosted marketplace, end users should use:

claude plugin marketplace add johnkozaris/jko-claude-plugins
claude plugin install <plugin-name>@jko-skills

Or load a single plugin for one session:

claude --plugin-dir "$PWD/plugins/<plugin-name>"

Local Iteration

  • In Claude Code, run /reload-plugins after installing, enabling, disabling, or updating plugins in the current session.
  • In GitHub Copilot CLI, reinstall a local plugin after edits because installed plugins are cached.

Conventions

  • Before committing plugin changes, run python3 scripts/lint-plugins.py (no CI — local only) and include its output. It checks description length limits, pattern-ID citation drift (CODE-/ARCH-/AP-/DN-), marketplace↔plugin.json version sync, orphaned reference files, private project-name leakage, empty hooks stubs, and dangling slash-command references.
  • Never name private projects in plugin content — plugins must be app-agnostic (app specifics go in env vars, manifests, or arguments). The linter's PRIVATE_NAMES blocklist enforces this.
  • When a plugin's content changes substantively, bump its version in BOTH plugin.json files and BOTH marketplace.json files (the linter catches mismatches).

Read the full file on GitHub · 68 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. 7d ago First seen · 68 lines · 832 tokens per session scan A edc4ae827247

Subscribe to this mod's changes

jko-claude-plugins CLAUDE.md is an instructions file published in the GitHub repository johnkozaris/jko-claude-plugins (11 stars, last pushed 10d ago), licensed MIT. It adds 832 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-30.

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

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

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

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,469 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

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