core

core is a cursor rule for Cursor from groupultra/telegram-search. It costs 0 tokens per session (588 once invoked), scanned A, original, AGPL-3.0.

A set of coding rules for the core parts of a Telegram search application, including events, database access, message processing, errors, and logs.

In plain words
What is it for?
Use it when changing packages/core, event handling, the Drizzle database layer, message resolvers, processing pipelines, or error and logging code.
Why use it?
It gives work in these shared foundations consistent boundaries and conventions, reducing the risk of changes breaking other parts of the application.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it when changing packages/core, event handling, the Drizzle database layer, message resolvers, processing pipelines, or error and logging code.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/groupultra/telegram-search/core
About the project

Telegram Search exports Telegram chat history and provides local full-text, fuzzy, and semantic search across the saved messages and media. It is used to back up personal conversations, locate information across large multilingual chats, and ask AI questions based on message history. The catalogue entries add agent and CLI workflows for exporting, synchronizing, and searching Telegram data.

groupultra/telegram-search · 4,126 stars · on GitHub · search.lingogram.app

Install

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.

Clone the repo
git clone --depth 1 https://github.com/groupultra/telegram-search

Made for: Cursor.

Wrote 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.

agentmods badge for core

README.md
[![agentmods](https://agentmods.dev/badge/rules/groupultra/telegram-search/core/github.svg)](https://agentmods.dev/rules/groupultra/telegram-search/core)
Your own site
<a href="https://agentmods.dev/rules/groupultra/telegram-search/core"><img src="https://agentmods.dev/badge/rules/groupultra/telegram-search/core/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.

agentmods 80×15 button for core

Your own site · 80×15
<a href="https://agentmods.dev/rules/groupultra/telegram-search/core"><img src="https://agentmods.dev/badge/rules/groupultra/telegram-search/core.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 588 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00588
Opus 5.5 $0.00000 $0.00235
Sonnet 5.5 $0.00000 $0.00118
Haiku 4.5 $0.00000 $0.00059

Measured 1mo ago against content hash f16381a13e04, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

core 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.

.cursor/rules/core.mdc · 58 lines

The source is not reproduced here

Licensed AGPL-3.0

The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

Changes

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.

  1. 1mo ago First seen · 58 lines · 0 tokens per session scan A f16381a13e04

Subscribe to this mod's changes

core is a cursor rule published in the GitHub repository groupultra/telegram-search (4,126 stars, last pushed today), licensed AGPL-3.0. It costs nothing until one of its globs matches a file; then it loads 588 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.