anti-slop is a set of opinionated Oxlint rules that reject low-evidence and low-signal TypeScript and JavaScript patterns — a lint layer aimed at the kind of code that passes review because it looks plausible. Installation runs through an agent skill: one command adds the skill, then the coding agent copies the plugin, installs current Oxlint dependencies, merges the plugin into the existing lint configuration, enables every generic rule and validates the result, with an opt-in rule group for repositories that depend on Effect.
The distribution decision is the interesting part. The project states it is meant to be vendored rather than treated as a fixed npm dependency: copy the rules in, read them, and change them to match your team's standards, after which the vendored files are yours to maintain. That inverts the usual incentive. A pinned dependency lets a team adopt someone else's judgement without reading it, while vendoring forces the rules to be understood before they start failing builds.
Machine-checkable standards are what make review scale, which is the constraint recorded in verification bandwidth being the scarce resource and observed where judgment becomes the scarce resource in agent workflows. The coding agents hub tracks the guardrail layer.
This is a repository README: it documents rules and installation without published detection rates or false-positive data. The condition to watch is whether the rule set publishes examples it deliberately allows, because a linter defined only by what it rejects tends to accumulate rules nobody can justify removing.