anti-slop
Opinionated Oxlint rules for rejecting low-evidence TypeScript and JavaScript patterns
Runssource: GitHubTypeScriptMITcommit c44ef22ca116
TypeScript, MIT licensed. The project labels itself: agent skills, linting, oxlint and typescript.
anti-slop runs. An Argusic agent installed it in 10 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
pnpm install resolves all dependencies, pnpm check passes all 4 stages (lint, test, typecheck, skill-asset drift) with Node.js v23 and NODE_OPTIONS=--experimental-strip-types, and pnpm sync:skill-assets copies source into the skill bundle
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 100 of 100 (the mean of this project's run scores).
At a glance
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.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Node.js 18 lacks import.meta.dirname support and cannot load .ts plugin files3 minutes
- pnpm not found in container0.5 minutes
- oxlint native binding @oxlint/binding-linux-x64-gnu missing (optional dependency not installed by default)0.2 minutes
- Install time
- 10 minutes
- Cold machine to finish
- 12 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- pnpm check exited 0: oxlint src (lint) passed, all 23 tsx test suites passed, tsc --noEmit (typecheck) passed, and node scripts/sync-skill-assets.mjs --check (skill-asset drift) reported 'Skill assets match src'
- Model tokens used
- 145,512
- Exact commit tested
- c44ef22ca116
- 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.
3. Ran `pnpm check` (lint → test → typecheck → skill-asset drift check) — all stages passed. 4. Ran `pnpm sync:skill-assets` — synced skill assets. tokens used 145,512 All four stages of `pnpm check` passed with exit code 0. Let me now produce the final report. **Summary of what I did:** 1. Ran `pnpm install` — succeeded after installing pnpm and the missing `@oxlint/binding-linux-x64-… 2. Encountered two issues: - **Oxlint native binding missing**: fixed by adding `@oxlint/binding-linux-x64-gnu` as a depend… - **Oxlint plugins required `import.meta.dirname` and `.ts` loading**: these features require No… 3. Ran `pnpm check` (lint → test → typecheck → skill-asset drift check) — all stages passed. 4. Ran `pnpm sync:skill-assets` — synced skill assets.
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.
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Took 10 minutes to install, slower than the median of the 24 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 25 agent-skills projects Argusic has installed and timed, anti-slop was the 21st fastest to reach a running state, and 18 of 25 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 10 minutes after the clone.
Run history
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/anti-slop)Questions
- Does anti-slop run?
- Yes. anti-slop runs. Argusic installed and launched it on a clean machine in 10 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test anti-slop?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit c44ef22ca116. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test anti-slop?
- The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does anti-slop take to install?
- 10 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 anti-slop need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing anti-slop?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does anti-slop compare with the alternatives?
- Of the 25 agent-skills projects Argusic has installed and timed, anti-slop was the 21st fastest to reach a running state, and 18 of 25 reached one at all.
- Where is the evidence for anti-slop?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.