Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/leshchenko1979/fast-mcp-telegramWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/leshchenko1979/fast-mcp-telegram/docs-plain-language)<a href="https://agentmods.dev/rules/leshchenko1979/fast-mcp-telegram/docs-plain-language"><img src="https://agentmods.dev/badge/rules/leshchenko1979/fast-mcp-telegram/docs-plain-language/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/leshchenko1979/fast-mcp-telegram/docs-plain-language"><img src="https://agentmods.dev/badge/rules/leshchenko1979/fast-mcp-telegram/docs-plain-language.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00536 |
| Opus 5.5 | $0.00000 | $0.00214 |
| Sonnet 5.5 | $0.00000 | $0.00107 |
| Haiku 4.5 | $0.00000 | $0.00054 |
Grade A, and why
docs-plain-language scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
1 near-identical copy found in the catalogue:
- docs-plain-language — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plain-language documentation
When editing Markdown (README, docs/, SECURITY.md, CONTRIBUTING.md, ADRs, memory bank, example YAML comments):
Goal
A new operator or contributor should understand what to do and what happens without decoding project slang.
Keep (widely used or project-defined once)
- Standard product terms after a short gloss: MCP, Bearer token, principal, principal identifier, http-auth, Telegram, MTProto, ACL
- Env vars and YAML keys as literals:
ACL_ENABLED,allow_mtproto,chats - Linked internal names when they are the actual config surface (file paths, tool names)
Avoid or replace
| Avoid | Prefer |
|---|---|
Invented shorthand (bot-like, power profile without table context) |
Names from SECURITY.md / examples: bot, team_lane, analyst |
| Phase/version jargon alone (“Phase 2 guardrails”) | What changed: “listed principals need allow_mtproto: true for raw MTProto” |
| Implementation slang without explanation (“synthetic rule”, “empty lane”) | Plain outcome: “principal not in principals: is denied” or “listed principal with no chats cannot use chat tools” |
-like, -style, “footgun”, “blast radius” in operator runbooks |
Direct risk: “teammates with the same principal identifier can read login codes” |
| Stacking nouns (“dual pre/post enforcement”) | One sentence: what is checked before the tool runs and what is filtered after |
Style
- Prefer tables for profiles and flags; one row = one audience action.
- First mention of a restriction: symptom → cause → fix (troubleshooting), not error-code archaeology.
- Example tokens in tests/docs: use names from
acl.yaml.example(automation-token), not cute internal labels. - English only; short sentences; active voice (“Set
allow_mtproto: true”) over passive stacks.
Quick check before finishing doc edits
- Would someone who only runs http-auth understand this without reading
session_acl.py? - Did every coined phrase appear in a glossary table or get removed?
- Are env vars and YAML keys copy-pasteable and spelled exactly as in code?
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 43 lines · 0 tokens per session scan A d3b06d733f09
docs-plain-language is a cursor rule published in the GitHub repository leshchenko1979/fast-mcp-telegram (50 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 536 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other cursor rules, from other repositories
example
You are in a workspace with Bifrost MCP tools enabled. Use them for code navigation, understanding, and modification. Follow these guidelines.
mcp
Rules written in Chinese for choosing an enhancement service based on the user's request. They cover feature changes, bug analysis, and project or architecture analysis.
bootstrap-alwayson
Minimal always-required LLM fixes.
monitoring
Monitoring, observability, and alerting rules.
data-fetching
Data fetching patterns with TanStack Query, Server Components, and Supabase.
single-commit-pr
Pull requests have exactly one commit: squash before opening, amend and force-push after.