materialgram
AGENTS.md1.2k starsChanged 31 days agoGPL-3.0View on GitHub
This guide defines repository-wide instructions for coding agents working with the Telegram Desktop codebase. In this repository "task" is a specific term. It always means one work record in the…
Trending
Quiet since September.thin dataabout the whole repository
Who's talking about kukuruzka165/materialgram
- NixOS/nixpkgs“materialgram: init at 5.4.1.1”GitHub · Jun 21, 2024 · 12 reactions
- SylEleuth/gruvbox-plus-icon-pack“Missing icon: Matrialgram”GitHub · Sep 8, 2026
- SylEleuth/gruvbox-plus-icon-pack“Missing icon: materialgram”GitHub · Sep 6, 2026
- lutit/UzbekGramDesktop“fix(workflow): use ubuntu latest”GitHub · Feb 24, 2026
- NixOS/nixpkgs“Update Request: materialgram 5.14.3.1 → 5.16.4.1”GitHub · Jul 18, 2025
The biggest 5 of 10 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 10
Talked about on GitHub (10 times).
On GitHub · 10
- Jun 21, 2024materialgram: init at 5.4.1.1 — NixOS/nixpkgs12 reactions · 22 comments
- Sep 8, 2026Missing icon: Matrialgram — SylEleuth/gruvbox-plus-icon-pack0 reactions · 2 comments
- Sep 6, 2026Missing icon: materialgram — SylEleuth/gruvbox-plus-icon-pack0 reactions · 1 comment
- Feb 24, 2026fix(workflow): use ubuntu latest — lutit/UzbekGramDesktop0 reactions
- Jul 18, 2025Update Request: materialgram 5.14.3.1 → 5.16.4.1 — NixOS/nixpkgs0 reactions
5 more on GitHub
- Nov 3, 2024materialgram: 5.6.1.1 -> 5.7.0.1 — NixOS/nixpkgs0 reactions · 3 comments
- Oct 8, 2024materialgram: 5.5.4.1 -> 5.6.1.1 — NixOS/nixpkgs0 reactions · 3 comments
- May 23, 2024[Request]: Materialgram — ScoopInstaller/Extras0 reactions · 1 comment
- Apr 15, 2024some missing icons — Mibea/Hatter0 reactions · 3 comments
- Oct 31, 2023Add io.github.kukuruzka165.materialgram — flathub/flathub0 reactions · 25 comments
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,700 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository7 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- code-healthSkill
- continueSkill
- dependency-watchSkill
- perform-taskSkill
- process-inboxSkill
- rebaseSkill
The file
Show its rules and text
We split this AGENTS.md into the rules it gives an agent
34 rules. About 0 are common, 11 are distinctive, and 23 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
This author's own choices. Worth a look.
23
Very specific
Tied to their project's names, files or tools. Probably skip.
Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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
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.

