agentleFS
toby7979toby7979/sealmyapp-tools/AGENTS.md

sealmyapp-tools

AGENTS.md0 starsChanged 32 days agoMITView on GitHub

Free tools and an ownership-verified scan: https://sealmyapp.com

  • 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 repositoryOne other file it gives its agents.

The file

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

7 rules. About 1 is common, 3 are distinctive, and 3 are very specific to this project.

  • ≈1

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Never put secret keys in client code or in NEXT_PUBLIC_, VITE_, EXPO_PUBLIC_, PUBLIC_ or REACT_APP_ variables.

    line 5
  2. Distinctive:

    Call paid APIs from server code that checks the signed-in user and rate-limits.

    line 7
  3. Common:

    If a secret was ever exposed, rotate it first.

    line 8
  4. Very specific:

    Never "fix" empty results or permission errors with using (true), with check (true), disabling RLS or granting to anon.

    line 10
  5. Very specific:

    Keep the Supabase service_role / secret key server-only.

    line 11
  6. Distinctive:

    Don't let users update their own role, plan, credits or admin flags.

    line 12
  7. Distinctive:

    Every API route / server action checks the signed-in user and ownership.

    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
<!-- Copy this section into your project's AGENTS.md (read by Codex, Cursor, Jules, Amp and other agents). -->

Security rules (vibe-coded app)

  • Never put secret keys in client code or in NEXT_PUBLIC_, VITE_, EXPO_PUBLIC_, PUBLIC_ or REACT_APP_ variables. Secrets include Stripe sk_/rk_/whsec_, OpenAI/Anthropic sk-, Supabase service_role/sb_secret_, AWS AKIA, GitHub ghp_, database URLs with passwords.
  • Public by design: Supabase anon/sb_publishable_ key, Stripe pk_ key, Firebase web apiKey.
  • Call paid APIs from server code that checks the signed-in user and rate-limits.
  • If a secret was ever exposed, rotate it first; deleting it from code is not enough.
  • Enable Row Level Security on every Supabase public table, with owner policies using (select auth.uid()). Update policies need both using and with check.
  • Never "fix" empty results or permission errors with using (true), with check (true), disabling RLS or granting to anon. using (true) is only for SELECT on genuinely public data.
  • Keep the Supabase service_role / secret key server-only.
  • Don't let users update their own role, plan, credits or admin flags.
  • Lock Firebase rules: no test-mode if true rules; check request.auth.uid against the owner.
  • Every API route / server action checks the signed-in user and ownership. Prices and paid status come from the server or a verified webhook.

Free tools and an ownership-verified scan: https://sealmyapp.com

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.