agentleFS
GastonGelhornGastonGelhorn/jevmate/skills/stats/SKILL.md

stats

Skill1 starsChanged 40 days agoMITView on GitHub

Show what jev decided in this session, what that text would have cost the agent to read, and the session's estimated spend.

17 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use scan and start.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • rajnavakotiSkill

    scan

    Run the AI dashboard scanner and generate the HTML report.

    Also in 3 projects that use this

  • AnthropicSkill

    start

    Set up your bio-research environment and explore available tools. Use when first getting oriented with the plugin, checking which literature, drug-discovery, or visualization MCP servers are connected, or surveying available analysis skills before starting a new project.

    Also in 4 projects that use this

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 12 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 person wants these numbers without asking, they are on the line above the prompt (Claude Code 2.1.287 or later), and /jevmate opens …

    line 24

“Common” is measured: kept by at least 6 in 10 of the 12 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

This session, as measured

jev session --plain

Explain the rows briefly to the person: "went through jev" is everything jev handled, hooks included; "kept out" is only the text jev judged instead of the agent reading it, plus trimmed output (the safety checks are listed apart because the agent would not have read that text); "would have cost" prices each piece at the model of the turn that would have read it, once, then as cache reads until the next compaction; "saved" is the difference, a ceiling because the uncertain band was read anyway. On a subscription the dollars are an API equivalent and the "plan" row gives the share of the 5-hour window and of the week. "safety" counts what the hooks caught, which is their value: it is not money. When the saving is small, lead with what the hooks caught, and say where jev saves most: large searches, logs, test suites, long diffs and many items to sort. The model side is an estimate from the transcript. If the person wants these numbers without asking, they are on the line above the prompt (Claude Code 2.1.287 or later), and /jevmate opens the same table in a pane.

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.