agentleFS
Sign inStart free
kid7stkid7st/agenticseo/AGENTS.md

agenticseo

AGENTS.md2 starsChanged 52 days agoMITView on GitHub

This repository is an independent, agent-first adaptation of OpenSEO's SEO capabilities: a local CLI plus ten agent skills. Read docs/DESIGN.md for the architecture and local-first boundary, and docs/openseo-parity.md for the capability inventory against upstream.

The file

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

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

  • ≈1

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep SEO operations usable without a required server or MCP connection.

    line 7
  2. Common:

    Keep agent-facing results concise with provenance and a path to detailed local evidence.

    line 9
  3. Very specific:

    Before opening a PR, run npm run check.

    line 11

≈ “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

AgenticSEO development guidance

This repository is an independent, agent-first adaptation of OpenSEO's SEO capabilities: a local CLI plus ten agent skills. Read docs/DESIGN.md for the architecture and local-first boundary, and docs/openseo-parity.md for the capability inventory against upstream.

  • Documentation is user-facing first. README.md stays short: what it does, install, accounts, getting started. Command details go in docs/commands.md, Google setup in docs/google.md, skills in docs/skills.md. Update the matching page when a command's behavior changes, and the parity row when upstream coverage changes.
  • Keep SEO operations usable without a required server or MCP connection. Do not import Cloudflare Worker, hosted billing, or Web UI dependencies into the local CLI.
  • Validate external provider data before using it. Missing metrics remain unknown, not zero. Report provider errors and costs when known; do not require product-level approval or budgets.
  • Keep agent-facing results concise with provenance and a path to detailed local evidence. Never store credentials in project files or Git.
  • Preserve OpenSEO's copyright and license notices in any source ported from it. Do not claim this project is an official OpenSEO release.
  • Before opening a PR, run npm run check. Keep tests fixture-backed; live paid calls are optional manual checks. Follow CONTRIBUTING.md for the PR workflow. Do not push directly to protected main.

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