agentleFS
Sign inStart free
hranesshraness/atet/.agents/skills/save-url-kb/AGENTS.md

atet / save-url-kb

AGENTS.md7 starsChanged 47 days agoMITView on GitHub

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

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

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep public APIs, HTTP, cookies, browser rendering, media, and evidence as independent fallbacks with auditable attempts.

    line 11
  2. Distinctive:

    Never claim a thread or discussion is complete when declared counts, cursors, pagination nodes, or configured bounds disagree.

    line 12
  3. Very specific:

    Keep credentials in memory, user-owned private files, or short-lived mode-0600 operating-system temporary files.

    line 13
  4. Distinctive:

    Treat screenshots as potentially private evidence because pixels are not structurally sanitized.

    line 15
  5. Very specific:

    Verify the installed environment with wordcell doctor and the current platform matrix with wordcell adapters.

    line 16

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

Contents

  • SKILL.md – capture triggers, command surface, workflow, and verification contract.
  • references/ – platform routing and authentication safety guidance.
  • agents/openai.yaml – user-facing skill metadata.

Guidelines

  • Invoke the installed wordcell CLI; do not depend on a source checkout or implementation path.
  • Preserve missing, blocked, deleted, cyclic, paginated, and limit-boundary states in every report.
  • Keep public APIs, HTTP, cookies, browser rendering, media, and evidence as independent fallbacks with auditable attempts.
  • Never claim a thread or discussion is complete when declared counts, cursors, pagination nodes, or configured bounds disagree.
  • Keep credentials in memory, user-owned private files, or short-lived mode-0600 operating-system temporary files. Never place cookies, authorization values, browser state, authenticated raw DOM, or HARs in capture artifacts.
  • Capture only public or user-entitled content. Do not bypass access controls, CAPTCHA, rate limits, DRM, or platform policy.
  • Treat screenshots as potentially private evidence because pixels are not structurally sanitized.
  • Verify the installed environment with wordcell doctor and the current platform matrix with wordcell adapters.

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.

Check your setup, free