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/tecnomanu/mcp-telegram-agentWrote 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/tecnomanu/mcp-telegram-agent/git-workflow)<a href="https://agentmods.dev/rules/tecnomanu/mcp-telegram-agent/git-workflow"><img src="https://agentmods.dev/badge/rules/tecnomanu/mcp-telegram-agent/git-workflow/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/tecnomanu/mcp-telegram-agent/git-workflow"><img src="https://agentmods.dev/badge/rules/tecnomanu/mcp-telegram-agent/git-workflow.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.00261 | $0.00261 |
| Opus 5.5 | $0.00104 | $0.00104 |
| Sonnet 5.5 | $0.00052 | $0.00052 |
| Haiku 4.5 | $0.00026 | $0.00026 |
Grade A, and why
git-workflow 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.
What it actually says
Git Workflow Rules
Branch Strategy
feature/* ---> PR ---> main
fix/* ---> PR ---> main
hotfix/* ---> main (emergency only)
mainis release-only.- Avoid direct development on
main. - One branch per responsibility.
- Do not mix unrelated changes.
Commit Format
Use English Conventional Commits with emoji:
feat(scope): ✨ add featurefix(scope): 🐛 fix bugdocs(scope): 📝 update docsrefactor(scope): ♻️ refactor codetest(scope): ✅ add/update testschore(scope): 🔧 maintenance
Required Validation Before PR/Push
Run:
npm run check
npm run build
npm run test
Rules:
- Keep tests green.
- If behavior changes, update tests.
Onboarding Execution Rule
- If user asks to install/configure this MCP, execute tools end-to-end.
- Do not stop at explanation-only responses.
- Require explicit
chat_idconfirmation before finalizing onboarding.
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 · 52 lines · 261 tokens per session scan A cf967ec45235
git-workflow is a cursor rule published in the GitHub repository tecnomanu/mcp-telegram-agent (1 stars, last pushed 5mo ago), licensed MIT. It adds 261 tokens to every session, about $0.0010 per session on Opus 5.5. 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-31.
Other cursor rules, from other repositories
git
Git workflow — commit format, push policy, and PR process.
commit-sponsors
Every git commit message must acknowledge BetterDesk supporters.
no-ai-contributors
Never add AI tools as git authors or project contributors.
git-discipline
Commit, push, and branching rules. Owns ALL git behavior; other files state only their deviations.
git-commit-standards
Enforce structured Git commit messages.
conventional-commits
Use the Conventional Commit Messages specification to generate commit messages.