o9k-core

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.

Security

Grade A, and why

o9k-core 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 2d 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.

plugins/o9k-core/.claude-plugin/plugin.json · 18 lines

What it actually says

{
  "name": "o9k-core",
  "displayName": "o9k Core",
  "version": "0.12.0",
  "description": "The o9k doctrine: token-efficiency rules of engagement and the arbitration layer that keeps efficiency plugins from colliding. Zero-effort: a SessionStart hook activates the doctrine automatically, checks dependencies for updates (npm o9k package + git marketplace channels; refreshes multi-CLI skills/hooks after apply), /o9k-init runs the guided setup, and /o9k-guide gives the human a personalized one-minute orientation.",
  "author": {
    "name": "Bumblebiber"
  },
  "repository": "https://github.com/Bumblebiber/its-over-9k",
  "license": "MIT",
  "keywords": [
    "token-efficiency",
    "claude-code",
    "meta-framework",
    "o9k"
  ]
}

Contents

What it installs

The manifest is a name and a version. 5 skills, 1 hook travel with it, and installing the plugin installs all of them — 396 tokens a session between them. Each is measured on its own page, and each can be installed alone.

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.

Related

Other plugins, from other repositories