1 email reported from 1 company, first seen , last seen . Praises a repository you own, then pitches a tool.
Template
From
{sender_name} at gitscope-ops.com
Template
Reconstructed from 1 copy
Hi {recipient_first_name},
Saw {recipient_repo} on GitHub ({recipient_star_count}, Rust).
We provide GitHub social proof for MCP servers and AI agent tools. Even when the code is high quality, developers on Glama.ai, Smithery, and GitHub rarely look inside a repo without visible social proof (star count and a balanced 10:1 fork ratio).
I set up a free +10 star test for {recipient_repo} (1-click claim, no login or card needed) so you can check the profiles and live tracker first:
https://gitscope.dev/audit/{recipient_repo}
If you want to scale after the test, you can configure 3-to-30 day drip schedules right on that page or hit reply for a multi-repo bundle.
Best,
{sender_name}
GitScope
Opt out: [unsubscribe link]
What goes in the slots
{recipient_product}
The recipient's product name, used in the subject line.Seen: “{recipient_product}”
{recipient_first_name}
The recipient's first name.Seen: “{recipient_first_name}”
{recipient_repo}
The recipient's GitHub repository name or identifier.Seen: “{recipient_repo}”
{recipient_star_count}
The repository's current GitHub star count.Seen: “{recipient_star_count}”
{sender_name}
The sender's personal name.Seen: “{sender_name}”
>_The likely prompt
Low confidence, 30%
Write a concise cold outreach email to the owner of a GitHub repository. Use a friendly, direct tone and the following structure: greet the recipient by first name; mention their repository, its star count, and that it is written in Rust; explain that visible social proof can help MCP servers and AI agent tools get noticed; offer a free +10 star test and include the provided audit URL; describe the 1-click claim and the option to scale with drip schedules or a multi-repo bundle; then sign off with the sender name and company and include the opt-out line. Keep the claims and wording measured and avoid adding unsupported details. Use these inputs: recipient first name {recipient_first_name}, product name {recipient_product}, repository {recipient_repo}, star count {recipient_star_count}, sender name {sender_name}, sender company GitScope, and audit URL https://gitscope.dev/audit/{recipient_repo}.
Reconstructed from the copies below. The sender’s real prompt may differ.
{recipient_product} - GitHub social proof (+10 star test)
Hi {recipient_first_name},
Saw {recipient_repo} on GitHub ({recipient_star_count}, Rust).
We provide GitHub social proof for MCP servers and AI agent tools. Even when the code is high quality, developers on Glama.ai, Smithery, and GitHub rarely look inside a repo without visible social proof (star count and a balanced 10:1 fork ratio).
I set up a free +10 star test for {recipient_repo} (1-click claim, no login or card needed) so you can check the profiles and live tracker first:
https://gitscope.dev/audit/{recipient_repo}
If you want to scale after the test, you can configure 3-to-30 day drip schedules right on that page or hit reply for a multi-repo bundle.
Best,
{sender_name}
GitScope
Opt out: [unsubscribe link]