DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to scan a paper folder for AI-style surface traces with Absent Author

Run slop_lint.py for counts of 28 surface traces, each with a file, line, and snippet.

  • Research
  • Intermediate
  • 15 minutes
  • From the README
  • Any agent

Who it is forAnyone who wants a quick first pass over a draft or preprint before a deeper read.

The problemReading a full paper to spot writing patterns takes time, and the patterns are easy to miss on a first read.

The outcomeA markdown report of calibrated counts per check, with a band against human percentiles and a snippet for each hit.

What you need first

  • git and a shell to clone the repo
  • Python 3.9 or newer for tools/slop_lint.py (no dependencies)
  • Claude Code, Codex, or another agent that reads SKILL.md for the two skills
  • pymupdf (pip install pymupdf) for tools/pdf_hidden_text.py
  • Optional: poppler-utils and tesseract for the OCR check on remapped text

Steps

  1. Clone the repo with git clone https://github.com/THUROI0787/absent-author.git && cd absent-author.
  2. Run python tools/slop_lint.py paper/ --source -o lint.md on your paper folder.
  3. Open lint.md and read each hit at its file and line.
  4. Treat each hit as a candidate to judge, not a verdict.

Prompt for your agent

In the absent-author repo, run tools/slop_lint.py on <paper folder> with --source and write the output to lint.md. Summarize the checks in the high band and list their file, line, and snippet. Verify by reading two of the cited lines yourself.

Caveat. The README says a clean report proves nothing, and the calibration sample is small, so the counts only flag writing patterns for a human to read.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page