agentleFS
lynote-ailynote-ai/ai-text-detector/AGENTS.md

ai-text-detector

AGENTS.md549 starsChanged 6 months agoMITView on GitHub

Use this repository as an AI-generated text risk analysis tool. Use it when the user asks whether a passage, essay, email, article, review, or message may be AI-generated.

  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 33,315 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository2 other files it gives its agents.

The file

We split this AGENTS.md into the rules it gives an agent

6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this repository as an AI-generated text risk analysis tool.

    line 3
  2. Distinctive:

    Use it when the user asks whether a passage, essay, email, article, review, or message may be AI-generated.

    line 7
  3. Distinctive:

    Never present the score as proof.

    line 11
  4. Distinctive:

    Never accuse a named person of cheating, fraud, or misconduct.

    line 12
  5. Distinctive:

    Ask for a longer sample when text is under ~80 words.

    line 13
  6. Distinctive:

    Prefer: "AI-like signals are present" over "This was written by AI".

    line 14

≈ “Common” is an estimate: at least 1 in 5 of the 42,283 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

Agent Instructions: AI Detector Skill

Use this repository as an AI-generated text risk analysis tool.

When to use

Use it when the user asks whether a passage, essay, email, article, review, or message may be AI-generated.

Required behavior

  • Never present the score as proof.
  • Never accuse a named person of cheating, fraud, or misconduct.
  • Ask for a longer sample when text is under ~80 words.
  • Prefer: "AI-like signals are present" over "This was written by AI".
  • For high-stakes contexts, recommend human review and comparison with known writing samples.

How to run

ai-detect path/to/text.txt --json

or:

python -m aidetect.cli path/to/text.txt --json

Response format for users

  1. Give a one-sentence conclusion with uncertainty.
  2. Show score and confidence.
  3. List the strongest evidence signals.
  4. Include caveats.
  5. Suggest next steps only when useful.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.