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.
npx agentmods add instructions/deandevz/king-context/claude-mdgit clone --depth 1 https://github.com/deandevz/king-contextWrote 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.
[](https://agentmods.dev/instructions/deandevz/king-context/claude-md)<a href="https://agentmods.dev/instructions/deandevz/king-context/claude-md"><img src="https://agentmods.dev/badge/instructions/deandevz/king-context/claude-md.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00494 | $0.00494 |
| Opus 5 | $0.00247 | $0.00247 |
| Sonnet 5 | $0.00099 | $0.00099 |
| Haiku 4.5 | $0.00049 | $0.00049 |
Grade A, and why
king-context 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 32 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.
@AGENTS.md
The imported AGENTS.md above is the canonical rule set: project identity (CLI-first, MCP legacy), the two retrieval stacks, commands, code conventions, testing, commits, ADRs, and the working agreement with the maintainer. Everything below is Claude-Code-specific.
Skills
This repo ships and uses Claude Code skills. Use them instead of improvising the equivalent workflow:
| Task | Skill |
|---|---|
| Create a PR | pr-create (authoritative; minimal Summary and Scope body) |
| Review a contributor PR | pr-review-flow (Portuguese verdict first, English preview after approval, confirm before every GitHub action) |
| Create a commit | commit-create |
| Capture a deferred idea as a GitHub issue | idea-issue (plain English, no invented solutions, preview first, idea label) |
| Record an architecture decision | king-record-decision (drives kctx adr, never hand-written ADR markdown) |
| Query past decisions | king-decisions |
| Search indexed documentation | king-context |
| Scrape and index docs | scraper-workflow |
| Research a topic into a corpus | king-research |
The five king-context skills (king-context, scraper-workflow, king-research, king-decisions, king-record-decision) are also distributed to user projects by the installer; their templates live in installer/templates/skills/. When editing a skill, keep the repo copy and the template in sync. See docs/skills.md.
Claude-specific notes
- The repo's own
.claude/skills/king-context/skill.mdintentionally calls barekctx, while the installer template uses.king-context/bin/kctxwrapper paths. Do not "fix" one to match the other. - Tests for MCP server tools mock
search_cascade()and otherdbfunctions with full module paths (king_context.db.x,king_context.server.x). - When verifying CLI behavior end to end, use the repo venv:
.venv/bin/kctx,.venv/bin/king-scrape,.venv/bin/king-research.
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.
- 4d ago First seen · 32 lines · 494 tokens per session scan A 43120162d16d
king-context CLAUDE.md is an instructions file published in the GitHub repository deandevz/king-context (52 stars, last pushed 3mo ago), licensed MIT. It adds 494 tokens to every session, about $0.0025 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.
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).
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.
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.
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.
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).
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.