agentleFS
Noah-OSNoah-OS/longhaul/skills/inspect/SKILL.md

inspect

Skill4 starsChanged 24 days agoMITView on GitHub

Show where this conversation's tokens went: usage by kind and by model, the subagents by agent type and model, context growth, the cache, the biggest tool outputs, searches (their chains and big results, and whether a code index was seen), repeated reads, each hook's times by event and source, what the guard caught, and the Advisor's consultations when there were any. Numbers only, each with its source.

15 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 13 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If the user gave an argument ($ARGUMENTS), run ${CLAUDE_PLUGIN_ROOT}/bin/longhaul inspect "$ARGUMENTS" instead and show that.

    line 20

“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

The report below is Longhaul's reading of this conversation's own transcript, its subagents' transcripts, the ledger, the guard's record and the Advisor experiment's trace. It holds numbers, model names, tool names and file paths only; never message text or tool output. Each heading names where its numbers came from and how sure they are: measured, counted, inferred or estimated.

!${CLAUDE_PLUGIN_ROOT}/bin/longhaul inspect "${CLAUDE_SESSION_ID}"

Show the report to the user as it is, in a code block, without changing or rounding any number. If it says no transcript was found, say so and show the message: the conversation may be too new for Claude Code to have written its file, or Longhaul's folder may be elsewhere (LONGHAUL_HOME). If the user gave an argument ($ARGUMENTS), run ${CLAUDE_PLUGIN_ROOT}/bin/longhaul inspect "$ARGUMENTS" instead and show that.

The report may name an install command; show it, take no install step.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.