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 Humblytics/humblytics-marketing-skills --skill revenue-attributorgit clone --depth 1 https://github.com/Humblytics/humblytics-marketing-skillsWrote 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/humblytics/humblytics-marketing-skills/revenue-attributor)<a href="https://agentmods.dev/skills/humblytics/humblytics-marketing-skills/revenue-attributor"><img src="https://agentmods.dev/badge/skills/humblytics/humblytics-marketing-skills/revenue-attributor/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/humblytics/humblytics-marketing-skills/revenue-attributor"><img src="https://agentmods.dev/badge/skills/humblytics/humblytics-marketing-skills/revenue-attributor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, 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 46 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.
- high Privilege Escalation · line 50 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.00087 | $0.03300 |
| Opus 5.5 | $0.00035 | $0.01320 |
| Sonnet 5.5 | $0.00017 | $0.00660 |
| Haiku 4.5 | $0.00009 | $0.00330 |
Grade A, and why
revenue-attributor 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 2mo 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.
Live data comes from the **Humblytics MCP** (server `humblytics`). This skill calls `mcp__humblytics__*` tools — `get_ads_attribution`, `list_meta_connections`, `get_meta_daily_insights`, `list_google_ads_connections`, a How it starts
The opening of the file, as written. The whole thing — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Revenue Attributor
Purpose
Connect ad spend to on-site conversion signals using Humblytics attribution, and rank campaigns by spend efficiency (sessions and ad_conversions per dollar). True revenue/ROAS, revenue_conversions, and trial_count are only populated when a Stripe/ChartMogul revenue connector is attached to the property — without one, those fields are 0. For true ROAS, join Humblytics spend + on-site conversion data to Stripe/ChartMogul revenue separately. This skill moves marketing teams from raw click counts to spend efficiency, and to revenue accountability once a revenue connector is in place.
When to Use
- Planning next month's ad budget and need data to reallocate
- Diagnosing why spend is up but revenue is flat
- Comparing paid vs organic vs direct revenue contribution
- Auditing campaign-level ROAS across Meta, Google, TikTok, LinkedIn
- Building a quarterly ad performance review for leadership
- Deciding whether to kill, scale, or hold a specific campaign
Connecting Humblytics
Live data comes from the Humblytics MCP (server humblytics). This skill calls mcp__humblytics__* tools — get_ads_attribution, list_meta_connections, get_meta_daily_insights, list_google_ads_connections, and friends — so there are no base URLs, curl calls, or API keys to wire up here. Connect the MCP once (see the repo README); the API key lives in the connection headers, set a single time.
- Never paste API keys into chat — they persist in transcripts and logs. The key belongs in the MCP connection config, never in
CLAUDE.md,.cursorrules, or any file committed to git. - Property: for a single-property key the MCP auto-resolves the property, so nothing to pass. For a multi-property key, call
list_propertiesand pass the chosenpropertyId. - Stripe/ChartMogul requirement: the Humblytics property must have a Stripe/ChartMogul revenue connector attached for revenue attribution to populate. No separate Stripe key is needed here — Humblytics handles ingestion internally. Without a revenue connector,
revenue,roas,revenue_conversions, andtrial_countcome back0.
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.
- 2mo ago First seen · 202 lines · 87 tokens per session scan A c08afe8cb670
revenue-attributor is a skill published in the GitHub repository Humblytics/humblytics-marketing-skills (85 stars, last pushed 1mo ago), licensed MIT. It adds 87 tokens to every session and 3,300 once invoked, about $0.0003 per session on Opus 5.5. 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.
revenue-attributor compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| revenue-attributorHumblytics/humblytics-marketing-skills | Skill | 85 | 1mo ago | MIT | A | 87 | Claude Code, Codex |
| ab-test-generatorAffitor/affiliate-skills | Skill | 767 | 18d ago | MIT | A | 87 | Claude Code |
| authoring-ci-workflowsPostHog/posthog | Skill | 41k | yesterday | none | A | 200 | Claude Code, Codex |
| isolating-product-facade-contractsPostHog/posthog | Skill | 41k | yesterday | none | A | 76 | Claude Code, Codex |
| triaging-merge-queue-failuresPostHog/posthog | Skill | 41k | yesterday | none | A | 180 | Claude Code, Codex |
| creating-online-evaluationsPostHog/posthog | Skill | 41k | yesterday | none | A | 203 | Claude Code, Codex |
| debugging-mcp-analyticsPostHog/posthog | Skill | 41k | yesterday | none | A | 211 | Claude Code, Codex |