agentleFS
leshchenko1979leshchenko1979/fast-mcp-telegram/AGENTS.md

fast-mcp-telegram

AGENTS.md50 starsChanged 4 months agoMITView on GitHub

The file

We found no rules to list in this file: it reads as prose or reference rather than instructions.

Files
AGENTS.md

AGENTS.md — fast-mcp-telegram

Operator Preferences

  • Use pg_query tool for any database queries against the telemetry collector's PostgreSQL. This is the preferred and only way to inspect the telemetry database — do not use bash + psql or any other method.
  • Use grep_docs tool for searching library and framework documentation.
  • Use the built-in grep tool for code analysis in this repo — symbol search, function definitions, callers, impact analysis. There is no symbol-index tool for Python here: the fleet's codegraph indexer was removed 2026-09-14, and memory_search scope="external" indexes only /root/opencrabs/src/**/*.rs, so it cannot see this repository's code. Raw grep over the tree is the correct instrument, not a fallback.

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.