Add plugin: treg.to

[JayZeeDesign]

What this adds

treg.to — plugin. One MCP connection that gives a Grok Bot 2,745 ready-to-call external API endpoints (SEO, enrichment, social listening, ads, e-commerce, scraping) on treg.to's own keys, metered at the provider's rate with $0 markup.

Checklist

• This PR adds exactly ONE new file under content/ (plus assets for this entry, if any).
• It follows CONTRIBUTING.md — required fields + the golden rules (G1–G8).
• npm run validate passes locally (schema, slug, vocabularies).
• slug is kebab-case and exactly matches the filename.
• I ran / used this myself end to end — it works today.
• Every URL in the frontmatter resolves to real, relevant content.
• The prompt body is the real, complete prompt — not a summary or a teaser.
• The entry body is plain markdown — no raw HTML (<script>, <iframe>, <style>, <form>, inline event handlers). CI rejects it (§8.5).
• I did NOT set verified_at or status: live — a maintainer sets those during verification (§10.1).
• This is not an ad. A listing that exists to funnel traffic to your product gets closed. Sponsor slots will exist for that — this isn't one.
• If this is someone else's work: author is the original creator, the origin is linked (source_url for a plugin, source_tweets[] for a use case), and scouted_by is me.
• If the source is a YouTube video: n/a — the source is the product itself and its public repo.
• I license this contribution under CC BY 4.0 (attribution: entry author + grokbot.dev).

Where it came from

I'm the maker (disclosed: author is me, and the entry links the public repo). Product: https://treg.to/agents/grok-bot · repo: https://github.com/superdesigndev/treg. The prompt is the real prompt we ship to Grok Bot users; install steps match the live Grok Bot plugin listing ("Treg", MCP category). Happy to adjust anything a reviewer flags.