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.
npx skills add IgorGanapolsky/ThumbGate --skill configure-analyticsgit clone --depth 1 https://github.com/IgorGanapolsky/ThumbGateWrote 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/skills/igorganapolsky/thumbgate/configure-analytics)<a href="https://agentmods.dev/skills/igorganapolsky/thumbgate/configure-analytics"><img src="https://agentmods.dev/badge/skills/igorganapolsky/thumbgate/configure-analytics/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/skills/igorganapolsky/thumbgate/configure-analytics"><img src="https://agentmods.dev/badge/skills/igorganapolsky/thumbgate/configure-analytics.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 36 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00000 | $0.00678 |
| Opus 5 | $0.00000 | $0.00339 |
| Sonnet 5 | $0.00000 | $0.00136 |
| Haiku 4.5 | $0.00000 | $0.00068 |
Grade A, and why
configure-analytics scanned grade A with 1 finding 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 10d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsS https://thumbgate.ai/health How it starts
The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Configure Analytics
Repeatable skill for setting up Plausible, PostHog, and GA4 analytics keys
in both local .env and Railway production environment variables.
When to use
- New session notices analytics env vars are missing
- After rotating any analytics API key
- After creating a new GA4 property
Prerequisites
- Chrome logged into: plausible.io, us.posthog.com, analytics.google.com
- Railway MCP authenticated OR Chrome logged into railway.com
Steps
1. Gather keys from dashboards
Plausible API key:
- Navigate to https://plausible.io/settings/api-keys
- If no key exists, create one named "thumbgate-railway-prod"
- Copy the key value
PostHog project API key:
- Navigate to https://us.posthog.com/settings/project#variables
- Copy the "Project API Key" (starts with
phc_)
GA4 Measurement ID:
- Navigate to https://analytics.google.com
- Select the ThumbGate property (or create one: Admin → Create Property)
- Go to Data Streams → Web stream → copy Measurement ID (format: G-XXXXXXXXXX)
- If no ThumbGate property exists, skip — Plausible is primary
2. Set local .env
Write/update repo/.env with:
PLAUSIBLE_API_KEY=<key>
PLAUSIBLE_SITE_ID=thumbgate-production.up.railway.app
POSTHOG_API_KEY=<phc_key>
THUMBGATE_GA_MEASUREMENT_ID=<G-ID or leave commented>
3. Set Railway production vars
Option A — Railway CLI or GitHub deploy variables (preferred):
gh secret list --repo IgorGanapolsky/ThumbGate
gh variable list --repo IgorGanapolsky/ThumbGate
If Railway CLI auth works, set variables with railway variables set.
If Railway CLI reports invalid_grant, use the GitHub PR/deploy path and the
Railway dashboard in Chrome. Do not direct-push to main; use a focused branch,
PR, required checks, and branch-protected merge.
Option B — Chrome (if MCP not authenticated):
- Navigate to railway.com dashboard
- Click into the ThumbGate project → production service
- Go to Variables tab
- Add/update each key-value pair
- Railway auto-redeploys on variable change
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.
- 10d ago First seen · 82 lines · 0 tokens per session scan A 91ecdc58339f
configure-analytics is a skill published in the GitHub repository IgorGanapolsky/ThumbGate (26 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 678 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
agentguard
Runtime guardrails for AI coding agents. Stop loops, budget overruns, retry storms, and timeouts before they burn money. Zero dependencies, local-first, MIT licensed.
crm-pipeline-playbook
How to answer pipeline, renewal, and account-health questions using the CRM tools.
deciding-who-decides
Decides who holds authority for a change — the agent at the edge or a human gate — by matching decision rights to reversibility, evidence, and consequence, and names the escalation trigger. Use when an agent could act on something irreversible, trust-bearing, or thinly evidenced. Do not use for trivial reversible…
staying-on-mission
Tests the current work against a written, lasting mission anchor and forces one choice, re-anchor, escalate, or stop. Use when an agent keeps finishing tasks but the work drifts from the goal, scope creeps, the same action repeats in a loop, or standards slip one small step at a time. Do not use for a tiny edit with…
verifying-final-artifacts
Verifies the delivered artifact a consumer actually receives (a figure, chart, PDF, SVG, screenshot, compiled build, or deployed response) by regenerating it fresh and directly observing the output, not the source that produces it, and ends in one honest verdict. Use when the deliverable is a produced artifact and…
closing-stale-packets
Brings an abandoned or half-filled change packet to an honest terminal state by completing it, closing it with a recorded rationale, or deleting it. Use when ng status flags a scaffold or invalid packet, a long session left a draft behind, or work was abandoned mid-packet. Do not use for an actively in-progress…