fix: replace token-like example with obvious placeholder in telegram.md

[marcusquinn]

Summary

• Resolve both GitHub secret scanning alerts (🤖 CodeRabbit AI Integration - Comprehensive Code Review Setup #1 and 🚀 CodeRabbit Pro Comprehensive Analysis - Full Codebase Review #2) — both false positives from fake/example credentials
• Replace example Telegram bot token in telegram.md that matched the real token regex and triggered alert 🚀 CodeRabbit Pro Comprehensive Analysis - Full Codebase Review #2
• Add inline comment to MongoDB test fixture in leak-detector.test.ts explaining it's an intentionally fake credential (alert 🤖 CodeRabbit AI Integration - Comprehensive Code Review Setup #1)
• Add **/leak-detector.test.* to .secretlintignore since leak-detector tests must contain realistic-looking secrets by design

Alert #1 — MongoDB Atlas URI (used_in_tests)

• File: .agents/scripts/simplex-bot/src/leak-detector.test.ts:155
• Fix: Inline comment + .secretlintignore entry. Test fixture kept realistic since that's the point of a leak detector test.

Alert #2 — Telegram Bot Token (false_positive)

• File: .agents/services/communications/telegram.md:114
• Fix: Replaced 123456:ABC-DEF1234ghIkl-zyx57W2v1u123ew11 (matched \d+:[A-Za-z0-9_-]{35}) with 123456789:YOUR-TOKEN-FROM-BOTFATHER (won't match scanner patterns).

[coderabbitai]

Warning

Rate limit exceeded

@marcusquinn has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 15 minutes and 32 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 442a721 and b05d2e5.

📒 Files selected for processing (1)

• .agents/services/communications/telegram.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/fix-example-token-pattern

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses a false positive secret scanning alert by updating example Telegram bot tokens in the telegram.md documentation. The changes ensure that documentation examples do not inadvertently trigger security warnings, improving the clarity and security posture of the project's documentation.

Highlights

• Example Token Replacement: Replaced a Telegram bot token example in telegram.md that was triggering GitHub secret scanning alerts due to matching a real token regex pattern.
• Improved Placeholder: Introduced new, visually obvious placeholders (123456789:YOUR-TOKEN-FROM-BOTFATHER and <your-token>) that will not match secret scanner patterns.
• Secret Scanning Alert Resolution: The related GitHub secret scanning alert was resolved as a false_positive since the original example was from Telegram's public documentation.

Changelog

• .agents/services/communications/telegram.md
  • Updated the example API token format to include a clear placeholder (123456789:YOUR-TOKEN-FROM-BOTFATHER).
  • Modified the example token used in the credentials.sh snippet to a generic <your-token>.

Activity

• No human activity has occurred on this pull request yet.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[github-actions]

🔍 Code Quality Report

�[0;35m[MONITOR]�[0m Code Review Monitoring Report

�[0;34m[INFO]�[0m Latest Quality Status:
SonarCloud: 0 bugs, 0 vulnerabilities, 113 code smells

�[0;34m[INFO]�[0m Recent monitoring activity:
Tue Mar 3 17:16:49 UTC 2026: Code review monitoring started
Tue Mar 3 17:16:50 UTC 2026: SonarCloud - Bugs: 0, Vulnerabilities: 0, Code Smells: 113

📈 Current Quality Metrics

• BUGS: 0
• CODE SMELLS: 113
• VULNERABILITIES: 0

Generated on: Tue Mar 3 17:16:52 UTC 2026

---

Generated by AI DevOps Framework Code Review Monitoring

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[gemini-code-assist]

Code Review

This pull request effectively addresses the GitHub secret scanning alert by replacing the token-like examples in telegram.md with clear, generic placeholders. The updated examples, such as 123456789:YOUR-TOKEN-FROM-BOTFATHER and <your-token>, are visually obvious and prevent false positives from secret scanning tools, improving the security posture of the repository without compromising clarity for users.

_{Note: Security Review has been skipped due to the limited scope of the PR.}