orchestkit AGENTS.md

A contributor guide for OrchestKit, a source-built Claude Code plugin containing reusable skills, specialist agents, and lifecycle hooks.

In plain words
What is it for?
Finding plugin source files, adding skills or agents, changing hooks or manifests, running the build, and verifying the generated plugin tree.
Why use it?
It prevents edits to generated files and explains that source changes must be rebuilt and committed with their generated output.

Instructions file for CodexOpenCode

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/yonatangross/orchestkit/agents-md
Clone the repo
git clone --depth 1 https://github.com/yonatangross/orchestkit

Made for: Codex, OpenCode.

Per session 934 This file is loaded in full into every session.
When invoked 934 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.00934 $0.00934
Opus 5 $0.00467 $0.00467
Sonnet 5 $0.00187 $0.00187
Haiku 4.5 $0.00093 $0.00093

Measured 3d ago against content hash 078615c33daa, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

AGENTS.md · 74 lines

How it starts

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

AGENTS.md

Instructions for AI coding agents working in the OrchestKit repository. This is the vendor-neutral companion to CLAUDE.md; where both exist, they say the same thing.

OrchestKit is a plugin for Claude Code (Anthropic's agentic CLI). It packages reusable skills, specialist agents, and lifecycle hooks. It is source-built: you edit src/ and a build step assembles the installable plugins/ tree. It is not a hosted service and has no runtime backend.

The one rule that prevents most broken PRs

Edit src/ and manifests/. Never edit plugins/ by hand — it is generated.

src/                         ← EDIT HERE
  skills/<name>/SKILL.md      # skills (YAML frontmatter + Markdown body, <500 lines)
  agents/<name>.md            # agents (frontmatter: name, description, model, tools, skills)
  hooks/src/<category>/*.ts   # TypeScript lifecycle hooks
manifests/                   ← EDIT HERE (plugin definitions)
plugins/                     ← GENERATED by `npm run build` — do not hand-edit

After any src/ change, run npm run build, then stage the resulting plugins/ diff together with your src/ change in the same commit. A plugins/ diff after a build is expected, not noise. If plugins/ comes out empty, the build was interrupted — run it again.

Build and verify

npm run build            # assemble plugins/ from src/ — required after editing src/
npm test                 # full suite (lint + unit + security + integration + e2e)
npm test --quick         # skip integration/e2e/performance
npm run test:skills      # skill structure validation
npm run test:agents      # agent frontmatter validation
npm run test:security    # security tests — MUST pass, gates push
npm run typecheck        # TypeScript check (run if hooks changed)

Before opening a PR: npm test and npm run test:security must pass, and git diff should show real changes (not no-ops left over from a previous session).

Adding a component

  • Skill — create src/skills/<name>/SKILL.md with frontmatter (name, description, tags, user-invocable, complexity); body stays under 500 lines. Add it to manifests/ork.json, then npm run build. See src/skills/CONTRIBUTING-SKILLS.md.
  • Agent — create src/agents/<name>.md with the required frontmatter, add to the manifest, rebuild.
  • Hook — create src/hooks/src/<category>/<name>.ts and register it in both src/hooks/hooks.json and the entries map src/hooks/src/entries/<event>.ts. One without the other is a silently-dead hook. Rebuild with cd src/hooks && npm run build.

Read the full file on GitHub · 74 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. 3d ago First seen · 74 lines · 934 tokens per session scan A 078615c33daa

Subscribe to this mod's changes

orchestkit AGENTS.md is an instructions file published in the GitHub repository yonatangross/orchestkit (224 stars, last pushed 3d ago), licensed MIT. It adds 934 tokens to every session, about $0.0047 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.