agentleFS
Sign inStart free
everyinfraeveryinfra/everyinfra-agent-plugins/llms.txt

everyinfra-agent-plugins

llms.txt347 starsChanged 2 months agoApache-2.0View on GitHub

Public, host-portable agent integration for EveryInfra. It combines reusable skills with remote MCP connection metadata; it does not contain the private gateway implementation. Canonical documentation: - Public source: https://github.com/everyinfra/everyinfra-agent-plugins - README: ./README.md - AI discovery contract: ./docs/ai-discovery.md - Architecture boundaries: ./docs/architecture.md - Installation: ./docs/installation.md - MCP install steps for agents: ./llms-install.md - Troubleshooting: ./docs/troubleshooting.md - Permissions and billing: ./docs/permissions.md - AI API: https://everyinfra.com/en/products/ai - REST-only product boundary: ./docs/rest-only.md - Portable plugin manifest: ./plugins/everyinfra/plugin.json - Skill router: ./plugins/everyinfra/skills/everyinfra/SKILL.md Runtime endpoint: https://api.everyinfra.com/mcp…

  • In this repositoryOne other file it gives its agents.

The file

We split this llms.txt into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Do not infer live availability, price, billing, official marketplace approval, or app registration from this file.

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 3,592 llms.txt 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
llms.txt
# EveryInfra agent plugin

> Public, host-portable agent integration for EveryInfra. It combines reusable skills with remote
> MCP connection metadata; it does not contain the private gateway implementation.

Canonical documentation:
- Public source: https://github.com/everyinfra/everyinfra-agent-plugins
- README: ./README.md
- AI discovery contract: ./docs/ai-discovery.md
- Architecture boundaries: ./docs/architecture.md
- Installation: ./docs/installation.md
- MCP install steps for agents: ./llms-install.md
- Troubleshooting: ./docs/troubleshooting.md
- Permissions and billing: ./docs/permissions.md
- AI API: https://everyinfra.com/en/products/ai
- REST-only product boundary: ./docs/rest-only.md
- Portable plugin manifest: ./plugins/everyinfra/plugin.json
- Skill router: ./plugins/everyinfra/skills/everyinfra/SKILL.md

Runtime endpoint: https://api.everyinfra.com/mcp
API documentation: https://everyinfra.com/en/docs

Current package boundary:
- MCP workflows: EveryData, EverySearch, EveryAI (AI API, free for accounts that have topped up),
  EverySolve
- REST-only guidance: EveryNumber, EveryMail, EveryProxy
- Command line: the `everyinfra-cli` skill drives the `everyinfra` tool (`pipx install everyinfra`)
- Eleven skills total: one router, seven product skills, two outcome workflows, one command-line skill

Do not infer live availability, price, billing, official marketplace approval, or app registration
from this file. Use live MCP discovery, public catalogs, and host status for those facts.

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