agentleFS
CohozenCohozen/magasins-u-mcp-server/AGENTS.md

magasins-u-mcp-server

AGENTS.md1 starsChanged 20 days agoMITView on GitHub

Guidance for coding agents working on this repository. Read docs/design.md before changing the browser layer or adding a tool. - This repository is public. Never commit personal data: store ids, account, order, list or receipt ids, real receipts, names, addresses, loyalty card numbers, cookies, tokens, HAR files, screenshots or HTML dumps of account pages. Test fixtures are synthetic or anonymised. Public catalogue data (product names, EANs, prices) is fine. - English everywhere in the repository: docs, code comments, test names,…

  • 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 32,671 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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    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:

    This repository is public: Never commit personal data: store ids, account, order, list or receipt ids, real receipts, names, addresses, …

    line 8
  2. Distinctive:

    The README documents Docker only: No instructions for a specific host, vendor or hardware: users adapt the Docker setup to their own …

    line 14
  3. Distinctive:

    Keep pure logic (parsing, rules) in tested functions.

    line 27
  4. Distinctive:

    Do not add a dependency for what a few lines can do.

    line 28
  5. Distinctive:

    Read-only by default. Ask the maintainer before a login, a write (cart, list, slot, order) or anything that changes the account.

    line 34
  6. Distinctive:

    Never solve or click a Cloudflare challenge, never spoof the browser fingerprint, never route through a VPN or proxy.

    line 36
  7. Distinctive:

    No feature that collects the catalogue in bulk: the site's legal notice targets database extraction.

    line 38
  8. Distinctive:

    Commit often, in small steps that can each be reverted on their own: one tool, one fix, one docs change, as soon as check and tests pass.

    line 45

≈ “Common” is an estimate: at least 1 in 5 of the 41,581 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

AGENTS.md

Guidance for coding agents working on this repository. Read docs/design.md before changing the browser layer or adding a tool.

Repository rules

  • This repository is public. Never commit personal data: store ids, account, order, list or receipt ids, real receipts, names, addresses, loyalty card numbers, cookies, tokens, HAR files, screenshots or HTML dumps of account pages. Test fixtures are synthetic or anonymised. Public catalogue data (product names, EANs, prices) is fine.
  • English everywhere in the repository: docs, code comments, test names, log messages and tool descriptions. Product data stays in French, as the site returns it.
  • The README documents Docker only. No instructions for a specific host, vendor or hardware: users adapt the Docker setup to their own environment.
  • No mention of the maintainer's private projects or personal setup. Describe consumers generically ("an MCP client", "an agent").
  • Local, private notes go in .local/ (git-ignored), never in docs/.

Development

  • npm install, then npx patchright install chromium for local runs.
  • npm run check (Biome, then TypeScript) and npm test (Vitest) must pass before a commit.
  • npm run build compiles to dist/; npm run dev runs src/server.ts directly.
  • Source files are TypeScript run with Node's type stripping: no enums, no parameter properties, import type for types, relative imports end in .ts.
  • Keep pure logic (parsing, rules) in tested functions; only thin functions touch the browser.
  • Do not add a dependency for what a few lines can do.

Working against the live site

The site is a real account behind Cloudflare. Use the live-check skill for any live test.

  • Read-only by default. Ask the maintainer before a login, a write (cart, list, slot, order) or anything that changes the account.
  • Never solve or click a Cloudflare challenge, never spoof the browser fingerprint, never route through a VPN or proxy.
  • No feature that collects the catalogue in bulk: the site's legal notice targets database extraction. Tools serve one user's requests on their own account.
  • On a challenge, a login wall or an HTTP 403/429, stop live checks and report.
  • Live captures (HAR, page dumps) stay in .local/ or a scratch directory, never in the repo.

Commits and releases

Commit often, in small steps that can each be reverted on their own: one tool, one fix, one docs change, as soon as check and tests pass. Keep a fix on its own branch and pull request, apart from feature work.

Pull requests are merged with "Rebase and merge" only: every commit of a pull request lands on main as is. So each commit must pass check and tests on its own and carry a conventional message; no "wip" or "fixup" commits (squash them locally before pushing).

Conventional commits (feat:, fix:, docs:, chore:…), subject in the imperative, in English. They drive the version: release-please keeps a release PR open that bumps package.json and writes CHANGELOG.md (feat → minor, fix → patch while in 0.x). Never edit the version or the changelog by hand; merging the release PR tags the release and publishes the image to GHCR.

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.