Skip to content
cccskills
FreePublished on GitHub

context-audit

Audit an agent's context layout against the four places: system prompt, tools, history, tail. Use when the user asks to audit, review or fix their agent's context, prompt caching, token spend per turn, or CLAUDE.md / AGENTS.md layout. Read-only: reports findings and a fix list, changes nothing. Do NOT use for writing evals (evals-bootstrap) or for loop design (goal-test).

The English summary is being prepared. Showing the original description.

undefined-ui/second-brain-os
See how to install

Files included (1)

  • SKILL.md3.1 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Audit the context window

Theory: How models read context and The four places. Every piece of context belongs in exactly one of four places — a byte-stable system prompt, a frozen tool set, a compacting history, and a short live tail — and most agent problems trace back to something sitting in the wrong one.

Core rule

Report and rank; never edit. The output is an audit, and the user decides what to apply. If they ask you to apply fixes afterwards, that is a normal edit session, not this skill.

Workflow

  1. Find the context sources. Locate what actually reaches the model: system prompt (or CLAUDE.md / AGENTS.md for a Claude Code setup), tool definitions, and — if the project logs requests — one full mid-conversation payload. If nothing is logged, say so and audit the static files; ask for one captured request only if the user can produce it cheaply.
  2. Measure the five numbers. Approximate token counts for: system prompt, tool definitions, message history, retrieved content, current query. A rough count (chars / 4) is fine; write all five down.
  3. Hunt cache killers. Flag every dynamic value in the system prompt — timestamps, user names, injected memories, "current task" lines. Each one is a guaranteed cache miss on every call. Check whether the tool list can change mid-run; a changing list invalidates the whole prefix.
  4. Hunt window bloat. Find the largest single item in the history. A verbatim tool result over ~2,000 tokens should have been a file path plus a one-line receipt. Count tools: past twenty (or ~10K tokens of definitions), recommend deferred tools + tool search.
  5. Check the tail. Locate the current goal. If it appears only in the opening message, it lives in the weak middle of the window — recommend restating it in the tail every three to five steps.
  6. Check guides. If CLAUDE.md / AGENTS.md exists: it should be a few lines of constraints the code cannot show, not four pages of narrative. Flag anything the repo already records (structure, history).

Output format

Context audit — <project>
system prompt   <n> tok   <clean | N dynamic values: ...>
tools           <n> tok   <n> tools  <frozen | mutates mid-run>
history         <n> tok   largest item: <what, n tok>
tail            <present | goal only in opening message>

Top fixes, in order of saved tokens per turn:
1. ...
2. ...

Each fix names the file and line where possible, states what moves to which of the four places, and estimates the saving. Close with the one-line rule: stable prefix, frozen tools, compact history, live tail.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

evals-bootstrap

Free

Scaffold a first eval suite for an agent: mine real failures into cases, write behavioural checks over traces, and generate the runner. Use when the user wants evals, regression tests for an agent, a golden set, or asks how to know a prompt/model change did not break things. Do NOT use for a single task's done-check (goal-test) or for auditing context (context-audit).

The English summary is being prepared. Showing the original description.

undefined-ui/second-brain-os1.1KUpdated Oct 14, 2026

gate-check

Free

Find the decisions in a pipeline that do not need the expensive model and propose the gate for each: a rule, a classic classifier, or a small model, with fail-closed routing. Use when the user asks to cut model costs or latency, says the big model handles everything, or wants a triage / routing / filter layer in front of an agent. Analysis plus an optional baseline scaffold. Do NOT use for auditing context layout (context-audit) or for building eval suites (evals-bootstrap).

The English summary is being prepared. Showing the original description.

undefined-ui/second-brain-os1.1KUpdated Oct 14, 2026

goal-test

Free

Turn a vague task into a testable definition of done and generate an executable goal-test script for it, optionally with a bounded retry loop around a headless agent. Use when the user wants to run an agent in a loop, asks how to know when an agent task is finished, or says a goal like "improve X" needs to become checkable. Do NOT use for building eval suites over many cases — that is evals-bootstrap.

The English summary is being prepared. Showing the original description.

undefined-ui/second-brain-os1.1KUpdated Oct 14, 2026

harness-audit

Free

Audit an agent's harness against the four rings: containment, guides, sensors, permissions. Use when the user asks whether their agent setup is safe, wants a review of sandboxing / permissions / hooks / AGENTS.md guardrails, or asks what a bad session could break. Read-only: reports the blast radius and a hardening list, changes nothing. Do NOT use for context layout (context-audit) or cost routing (gate-check).

The English summary is being prepared. Showing the original description.

undefined-ui/second-brain-os1.1KUpdated Oct 14, 2026

second-brain-backfill

Free

Import a large archive into the vault in controlled batches: triage what is worth ingesting, process oldest first, checkpoint after every batch, and keep cost visible. Use this skill whenever the user wants to import years of bookmarks, an export from another notes app, a downloads folder, a chat history dump, or says "backfill", "bulk import", "process my archive". Do NOT use for ingesting one or a few new sources, which is second-brain-ingest.

The English summary is being prepared. Showing the original description.

undefined-ui/second-brain-os1.1KUpdated Oct 14, 2026

second-brain-changed-my-mind

Free

Trace where the user's recorded position on something has shifted: superseded claims, contradictions between sources of different dates, and what evidence moved them. Use this skill when the user asks what they have changed their mind about, how their thinking on a topic developed, what they used to believe, or wants a quarterly look back at their own positions. Do NOT use for finding contradictions between sources with no time dimension, or for a current-state answer.

The English summary is being prepared. Showing the original description.

undefined-ui/second-brain-os1.1KUpdated Oct 14, 2026

See all skills by undefined-ui

Report a problem with this skill