A short status report for recent work in the current coding session, or in the latest saved report if the session is unavailable. It is intended for quick updates such as a morning or evening check-in.

Use it when you ask for a brief, progress update, morning update, evening update, or a summary of what happened. It reports recent session activity and can follow the project's notification rules.

It removes the need to reconstruct recent activity from many messages or files. It gives the operator a compact view of what happened and what is currently active.

brief — Skill for Claude Code and Codex by gtapps: A short status report for recent work in the…

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/gtapps/claude-code-hermit/brief

Any agent

npx skills add gtapps/claude-code-hermit --skill brief

Clone the repo

git clone --depth 1 https://github.com/gtapps/claude-code-hermit

Made for: Claude Code, Codex.

Or install claude-code-hermit, the plugin that ships this one along with the rest of its 19 skills, 4 agents.

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

README.md

[![agentmods](https://agentmods.dev/badge/skills/gtapps/claude-code-hermit/brief.svg)](https://agentmods.dev/skills/gtapps/claude-code-hermit/brief)

Your own site

<a href="https://agentmods.dev/skills/gtapps/claude-code-hermit/brief"><img src="https://agentmods.dev/badge/skills/gtapps/claude-code-hermit/brief.svg" alt="Measured on agentmods" height="20"></a>

Per session 62 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,882 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.

Model	Per session	Once invoked
Fable 5	$0.00062	$0.02882
Opus 5	$0.00031	$0.01441
Sonnet 5	$0.00012	$0.00576
Haiku 4.5	$0.00006	$0.00288

Measured today against content hash 71eccc1fbcde, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

brief 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 today.

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.

plugins/claude-code-hermit/skills/brief/SKILL.md · 132 lines

How it starts

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

Session Brief

Provide a concise executive summary of recent session activity. Designed for morning check-ins, phone/channel consumption, and quick status updates.

Always-On Delivery Rule

If config.always_on is true, deliver all operator-facing output per CLAUDE-APPEND.md § Operator Notification. The terminal is unmonitored in always-on mode. For the push-fallback branch, condense the brief to a single line (per § Operator Notification push format): include whichever of open proposal count and active heartbeat alerts are present and non-zero; omit zero or unavailable fields. Example: Brief: 16 proposals open, 1 alert — open CC to view. In interactive mode, output to terminal. This applies to all flags below.

Dispatch

Before composing any brief, determine the dispatch mode:

Read session_state from .claude-code-hermit/state/runtime.json (live state — always in main).
Resolve the active flag (--morning, --evening, "brief today"/"daily summary", or no flag).

Live files (SHELL.md, alert-state.json, proposals/) are read fresh on this turn; a value held in context from before a compaction is stale.

Dispatch decision:

--morning → dispatch (mode: morning)
--evening → dispatch (mode: evening)
"brief today" / "daily summary" / "what happened today" → dispatch (mode: daily)
No flag + session_state is in_progress → no dispatch — summarize the live SHELL.md in main (Plan step 1a)
No flag + session_state is idle → no dispatch — read the live SHELL.md in main and emit the idle block (Plan step 1b)
No flag + no active session (no SHELL.md / no session_state) → dispatch (mode: default-no-session, Plan step 1c)

For dispatching modes: invoke claude-code-hermit:skill-eval-runner pointed at ${CLAUDE_PLUGIN_ROOT}/skills/brief/reference.md. Pass in the dispatch prompt: mode (one of the values above), today (current ISO date), and for morning only: context_recovery (set to true if auto-memory seems sparse — new instance, fresh machine — false otherwise).

Read the full file on GitHub · 132 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

reference.md 5.2 KB

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.

today Changed · +3 lines 71eccc1fbcde
3d ago First seen · 129 lines · 62 tokens per session scan A 7a828a82a67e

Subscribe to this mod's changes

brief is a skill published in the GitHub repository gtapps/claude-code-hermit (73 stars, last pushed today), licensed MIT. It adds 62 tokens to every session and 2,882 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.

ai ai-agent anthropic autonmous-agent claude claude-code

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens