Skip to content

docs(arsenal): add TGScope to §38 Telegram & Messaging Intelligence - #31

Merged
elementalsouls merged 2 commits into
elementalsouls:mainfrom
Courier-Britva:docs/arsenal-tgscope
Oct 20, 2026
Merged

elementalsouls merged 2 commits into
elementalsouls:mainfrom
Courier-Britva:docs/arsenal-tgscope

Conversation

@Courier-Britva

Copy link
Copy Markdown
Contributor

Pull Request

Description

Adds one tool line to offensive-osint §38 (Telegram & Messaging Intelligence): TGScope, a free search over public Telegram channels that matches by meaning in any language, plus a free check that dates a channel from its numeric ID. It helps find channels that use a target's brand name and tell a long-running channel from a fresh one.

Type of change

  • Wordlist / catalog expansion (non-breaking)

Affected skills

  • offensive-osint

Affected sections (if applicable)

  • arsenal §38

Checklist

  • My change is OSINT-only (no active exploitation, post-exploit, malware tradecraft).
  • No client/engagement identifiers in the diff.
  • I updated CHANGELOG.md under [Unreleased].
  • My commits follow the format <type>(<scope>): <subject>.

Not applicable: no new section, skill, trigger or capability, so README tables, frontmatter triggers, smoke-test prompts and doc counts are unchanged.

Sample prompt that exercises this change

Find public Telegram channels that use the ACME brand name and tell which of them were created recently.

Expected response

The §38 tool list now offers TGScope for the channel search and the creation-date check, next to TGStat, Telemetr and Combot.

Additional notes

Disclosure: I run TGScope.

Courier-Britva and others added 2 commits October 11, 2026 10:47
Reorder the §38 line (and CHANGELOG) so the capability the list did not
already have — dating a Telegram channel from its numeric ID — reads first,
ahead of the semantic channel search.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@elementalsouls
elementalsouls merged commit c359ec1 into elementalsouls:main Oct 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants