Alternatives
Products that do what Sloppoke does
Blazing fast LLM slop removal from code before you commit
- 1AA
Hi, I’m Kenny, I’ve been building aislop. I starting working on this after using Claude Code, codex and opencode several times and noticing some slops. They aren’t syntax and passes most tests, they are patterns like empty catch blocks, useless comments, duplicated helpers, dead code and many more. So I built a tool to scan and check for these patterns and wired it into hooks so after each tool call, the agent checks for the slops. You can try it out with npx aislop scan. It’s all local and no code is transferred. Thank you.
May 2026 · github.com
- 2
- 3SL
I made a free tool that stuns LLMs with invisible Unicode characters. *Use cases:* Anti-plagiarism, text obfuscation against LLM scrapers, or just for fun! Even just one word's worth of “gibberified” text is enough to block most LLMs from responding coherently.
Nov 2025 · gibberifier.com
- 4
- 5
- 6YA
- 7
- 8
- 9
- 10
- 11
- 12TC
Hi HN, I spent my easter weekend stuck in the house with COVID and I decided to play with llama.cpp [1] and fauxpilot [2] to see if I could get LLM code assist working on pure CPU. As a proof of concept I'd say I've proven that it's possible. However there's still a lot to do. The auto complete is quite slow at the moment. PRs welcome. [1] https://github.com/ggerganov/llama.cpp [2] https://github.com/fauxpilot/fauxpilot
2023 · github.com
- 13
- 14FA
Hi HN, Lately Github PRs have been drowning in a flood of AI slop. I’ve been seeing it myself, and I’m not the only one: https://x.com/mitchellh/status/2011819428061855915 I think it’s great that folks are using AI tools to code faster and better, but too many folks are abusing them to make low-quality contributions to public repos. This takes a lot of reviewers’ mindshare. IMO there needs to be a mechanism to flag low-effort PRs with AI slop, so you can just skip reading them. So I built one: https://haystackeditor.com/slop-detector It’s a simple AI…
Jan 2026 · haystackeditor.com
- 15CM
I built a CLI tool to generate as much slop as possible
Mar 2026 · github.com
- 16
Aggregate uptime monitoring across OpenAI, Claude, and more
Apr 2026 · tools.lamatic.ai
- 17HT
Ok, so maybe "how to revive the internet" would be more accurate, but if you're reading this, I got your attention, right? Here's why I want you to read on: I built a free extension, D-slop, to disincentivize anyone from posting AI writing, and eventually images and video as well, on the internet. For writing, it checks known vocab and punctuation tells, as well as subtler tells related to cadence, and assigns it a score subject to an adjustable threshold. If the text fails, users have the option to flag offending text, hide it, or block the page entirely (with the option to see anyway). For…
May 2026 · chromewebstore.google.com
- 18SO
I’ve been building a crowd-sourced AI detection benchmark. Two responses to the same prompt — one from a real human (pre-2022, provably pre prevalence of AI slop on the internet), one generated by AI. You pick the slop. Three wrong and you’re out. The dataset: 16K human posts from Reddit, Hacker News, and Yelp, each paired with AI generations from 6 models across two providers (Anthropic and OpenAI) at three capability tiers. Same prompt, length-matched, no adversarial coaching — just the model’s natural voice with platform context. Every vote is logged with model, tier, source, response…
Mar 2026 · slop-or-not.space
- 19
- 20
- 21TJ
What it is: A fully functional academic journal where every paper must be co-authored by an LLM, and peer review is conducted by a rotating panel of 5 LLMs (Claude, Grok, GPT-4o, Gemini, Llama). If 3+ vote "publish," it's published. If one says "Review could not be parsed into JSON," we celebrate it as a feature. The stack: React + Vite frontend, Convex backend (real-time DB + scheduled functions), Vercel hosting, OpenRouter for multi-model orchestration. Each review costs ~$0.03 and takes 4-8 seconds. Why I built it: Academic publishing is already slop—LLMs write drafts, LLMs review papers,…
Dec 2025 · journalofaislop.com
- 22SM
About 6 years ago I wrote a blog post [0] with some ideas on how to help popular open source maintainers deal with all the noise on Github. Patted myself in the back and never did anything about it :) There's recently been a lot more discussion around this due to AI, so I've built a simple tool called "Slop Meter" [1]. It gives maintainers a quick snapshot of the user's history in open source: 1) Do they just open issues and expect you to do everything, or will they put in the work to fix the problems and open a PR? What's the issues : PR ratio? 2) If they do contribute, what percentage of…
Mar 2026
- 23
I know we are very wary of AI slop but disclaimer: AI was used. I don't think that it is slop though and it was mostly used for formatting.
Jul 2026 · github.com
- 242C
Single-agent LLMs suck at long-running complex tasks. We’ve open-sourced a multi-agent orchestrator that we’ve been using to handle long-running LLM tasks. We found that single LLM agents tend to stall, loop, or generate non-compiling code, so we built a harness for agents to coordinate over shared context while work is in progress. How it works: 1. Orchestrator agent that manages task decomposition 2. Sub-agents for parallel work 3. Subscriptions to task state and progress 4. Real-time sharing of intermediate discoveries between agents We tested this on a Putnam-level math problem, but the…
Feb 2026 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →