context-kernel

A shared set of workspace and file-ownership rules for a content-production system made of several connected skills.

In plain words
What is it for?
Use it to define where brand notes, research, analysis, content concepts, and delivery files live, and how those files pass between stages.
Why use it?
It prevents different skills from using different locations, overwriting the wrong files, or losing information as work moves from research to publishing.

Skill for Claude CodeCodex

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 skills/themattberman/openclaw-100k-posts-kit/context-kernel
Any agent
npx skills add TheMattBerman/openclaw-100k-posts-kit --skill context-kernel
Clone the repo
git clone --depth 1 https://github.com/TheMattBerman/openclaw-100k-posts-kit

Made for: Claude Code, Codex.

Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 707 The whole file, excluding the scripts and references it only reads on demand.
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.00046 $0.00707
Opus 5 $0.00023 $0.00353
Sonnet 5 $0.00009 $0.00141
Haiku 4.5 $0.00005 $0.00071

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

Security

Grade A, and why

context-kernel 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.

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.

skills/context-kernel/SKILL.md · 81 lines

How it starts

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

Context Kernel

This skill is the shared system layer for this repo.

It exists to keep the other skills aligned around one runtime contract:

  • where shared files live
  • which skill owns which files
  • what can be overwritten vs appended
  • how to pass context between skills without inventing missing state

Shared Workspace

All persistent state lives under ~/clawd/workspace/.

Brand Context

  • ~/clawd/workspace/brand/voice-profile.md
  • ~/clawd/workspace/brand/notes.md

Research + Analysis

  • ~/clawd/workspace/content-radar/config.yaml
  • ~/clawd/workspace/content-radar/briefings/
  • ~/clawd/workspace/content-dna/outputs/
  • ~/clawd/workspace/content-dna-batch/dna-cache/
  • ~/clawd/workspace/content-dna-batch/reports/

Production + Delivery

  • ~/clawd/workspace/the-forge/outputs/
  • ~/clawd/workspace/monday-drop/outputs/

Ownership Rules

  • voice-lab owns voice-profile.md.
  • voice-lab may append useful discoveries to notes.md.
  • content-radar owns briefing files in content-radar/briefings/.
  • content-dna owns single-video analysis files.
  • content-dna-batch owns pattern reports and DNA cache.
  • the-forge owns forged concept output.
  • monday-drop owns delivery logs and exported run summaries.

Read Rules

  • voice-lab may read any file in workspace/brand/.
  • content-radar should only read config.yaml.
  • content-dna should read voice-profile.md only when adapting concepts.
  • content-dna-batch should read Content DNA outputs and its own cache.
  • the-forge should read voice-profile.md, pattern reports, and optionally the latest content-radar briefing.
  • monday-drop should read config, reports, and forged outputs. It should not invent missing brand state.

Write Rules

  • Never overwrite voice-profile.md without showing the user what will change.
  • notes.md is append-only.
  • Dated run artifacts should create new files instead of overwriting old ones.
  • If a script or skill cannot produce a promised artifact, say that clearly in the output instead of faking completeness.

Read the full file on GitHub · 81 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. 2d ago First seen · 81 lines · 46 tokens per session scan A ce4e20eb8341

Subscribe to this mod's changes

context-kernel is a skill published in the GitHub repository TheMattBerman/openclaw-100k-posts-kit (20 stars, last pushed 5mo ago), licensed MIT. It adds 46 tokens to every session and 707 once invoked, about $0.0002 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.