fast-jev-compaction

Claude Code plugin that replaces the compaction summary with Jev decisions: every tool call and result is scored in one fast request, stale ones are dropped or truncated, everything kept stays verbatim.

Runssource: GitHubTypeScriptMITcommit e3f262a7f4d4

TypeScript, MIT licensed.

fast-jev-compaction runs. An Argusic agent installed it in 0.1 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

npm install added 50 packages with no errors; npm test runs 29 tests across 2 files passing; npm run build produces dist/; npm run typecheck passes for both library and hook tsconfigs

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 96 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
96 / 100
cost of the verifying run
$0.01 (measured)
recorded runs
2
last tested
stars
7,980
forks
589
open issues
125
watchers
14
size
0 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Install time
under a minute
Cold machine to finish
2 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
npm test exited 0, 29 tests passed (2 suites); npm run build and npm run typecheck both exited 0
Model tokens used
64,056
Exact commit tested
e3f262a7f4d4
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

console.log('OK: library imports work');
\" 2>&1" in /work/repo
 succeeded in 0ms:
compactMessages: function
reductionRatio: function
OK: library imports work
All works. Let me clean up and report.
2026-11-05T16:17:40.126302Z ERROR codex_core::tools::router: error=exec_command failed: CreateProce…
All standard commands (`npm install`, `npm test`, `npm run build`, `npm run typecheck`) succeeded w…
tokens used
64,056
All standard commands (`npm install`, `npm test`, `npm run build`, `npm run typecheck`) succeeded w…

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Installed in 0.1 minutes, faster than the median of the 35 comparable projects Argusic has measured.
  • Nothing broke on the way: zero errors between clone and running.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

Of the 36 TypeScript projects Argusic has installed and timed, fast-jev-compaction was the 1st fastest to reach a running state, and 30 of 36 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.
  • A quick evaluation: it was running 0.1 minutes after the clone.
  • Following its own README: the documented path worked with nothing to fix.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.01
Argusic Runner1/3Runs with mocks92.000.02

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/fast-jev-compaction.svg)](https://argusic.com/subject/fast-jev-compaction)

Questions

Does fast-jev-compaction run?
Yes. fast-jev-compaction runs. Argusic installed and launched it on a clean machine in 0 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test fast-jev-compaction?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit e3f262a7f4d4. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test fast-jev-compaction?
The run that produced this verdict cost $0.01: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does fast-jev-compaction take to install?
0.1 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does fast-jev-compaction need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing fast-jev-compaction?
Nothing did, in the recorded run: zero errors between clone and running.
How does fast-jev-compaction compare with the alternatives?
Of the 36 TypeScript projects Argusic has installed and timed, fast-jev-compaction was the 1st fastest to reach a running state, and 30 of 36 reached one at all.
Where is the evidence for fast-jev-compaction?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion