no-ai-slop
Removes 20+ patterns of AI slop from any piece of writing.
Runs with mockssource: GitHubhomepagePythonMITcommit 000650b15698
Python, MIT licensed.
no-ai-slop runs, with stand-ins for the services it depends on. An Argusic agent installed it in 2 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Plugin builds valid ZIP archive and installs globally into ~/.agents/skills/no-ai-slop, symlinked to Codex and GitHub Copilot agents, with SKILL.md and eval.md identical to source.
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 92 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.
- npx [email protected] requires Node >=22.20.0, container has Node 18.19.1. SyntaxError on styleText export from node:util.1 minute
- Install time
- 2 minutes
- Cold machine to finish
- 2 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- python3 scripts/build_plugin.py --check exited 0; npx [email protected] list --global shows no-ai-slop installed; installed SKILL.md and eval.md match originals via diff; ffmpeg -v error -i assets/no-ai-slop.png -f null - exited 0; zipfile.is_zipfile confirms archive
- Model tokens used
- 77,583
- Exact commit tested
- 000650b15698
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
**Errors:** One error encountered and fixed — the latest `skills` CLI (1.7.0) requires Node >=22.20…
**Verification:** Build archive validated (7 expected files present, ZIP well-formed, PNG passes ff…
**Final state:** Plugin builds and installs correctly — no app to launch since this is a markdown-b…
exec
/bin/sh -lc "echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 2…
succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 2, "errors": [{"msg": "npx…
exec
/bin/sh -lc "echo 'ARGUSIC_RESULT:{\"install_succeeded\":true,\"launch_succeeded\":true,\"install_m…
succeeded in 0ms:
tokens used
77,583Replay 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
- Installed in 2 minutes, faster than the median of the 10 comparable projects Argusic has measured.
- Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 11 Python projects Argusic has installed and timed, no-ai-slop was the 4th fastest to reach a running state, and 6 of 11 reached one at all.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.01 |
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/no-ai-slop)Questions
- Does no-ai-slop run?
- no-ai-slop runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 2 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test no-ai-slop?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 000650b15698. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test no-ai-slop?
- 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 no-ai-slop take to install?
- 2 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 no-ai-slop need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing no-ai-slop?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does no-ai-slop compare with the alternatives?
- Of the 11 Python projects Argusic has installed and timed, no-ai-slop was the 4th fastest to reach a running state, and 6 of 11 reached one at all.
- Where is the evidence for no-ai-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.