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 skills/deandevz/king-context/king-decisionsnpx skills add deandevz/king-context --skill king-decisionsgit 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/skills/deandevz/king-context/king-decisions)<a href="https://agentmods.dev/skills/deandevz/king-context/king-decisions"><img src="https://agentmods.dev/badge/skills/deandevz/king-context/king-decisions.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.00061 | $0.00400 |
| Opus 5 | $0.00030 | $0.00200 |
| Sonnet 5 | $0.00012 | $0.00080 |
| Haiku 4.5 | $0.00006 | $0.00040 |
Grade A, and why
king-decisions 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 5d 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.
What it actually says
King Decisions
Retrieve project architectural decisions through .king-context/bin/kctx adr.
Use this skill when the user asks about existing decisions, current architecture rationale, decision history, supersession, or conflicts with planned changes.
Goal
Answer from the minimum relevant decision context.
Behavior
Be direct and evidence-oriented. Cite ADR IDs. Prefer making a scoped retrieval attempt over asking for clarification when the topic is clear enough.
Rules
- Prefer active ADRs for current guidance.
- Use timeline when the user asks why something changed or when active results supersede older decisions.
- Use historical ADRs only when they affect the answer.
- If no ADR exists, say that no indexed decision was found. Do not invent one.
- Do not scan or read
.king-context/adr/*.mddirectly for retrieval. Usekctx adr status,kctx adr index,kctx adr search,kctx adr timeline, andkctx adr read.
Retrieval Budget
- Start with
.king-context/bin/kctx adr status; if stale, run.king-context/bin/kctx adr indexbefore searching. - First call:
.king-context/bin/kctx adr search "<topic>" --active --top 5 - If enough:
.king-context/bin/kctx adr read <ADR-ID> --previewor full read - If history matters:
.king-context/bin/kctx adr timeline "<topic>" - Stop when the current decision and relevant history are clear.
Output
- State the current decision first.
- Mention superseded decisions only when relevant.
- Cite ADR IDs.
- Keep the answer concise.
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.
- 5d ago First seen · 42 lines · 61 tokens per session scan A d0ee13200a54
king-decisions is a skill published in the GitHub repository deandevz/king-context (52 stars, last pushed 3mo ago), licensed MIT. It adds 61 tokens to every session and 400 once invoked, about $0.0003 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…