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 agentmods add agents/jeremylongworth-source/agentskills/agents.creator-analytics-reportinggit clone --depth 1 https://github.com/jeremylongworth-source/AgentSkillsWrote 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/agents/jeremylongworth-source/agentskills/agents.creator-analytics-reporting)<a href="https://agentmods.dev/agents/jeremylongworth-source/agentskills/agents.creator-analytics-reporting"><img src="https://agentmods.dev/badge/agents/jeremylongworth-source/agentskills/agents.creator-analytics-reporting.svg" alt="Measured on agentmods" height="20"></a>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.00359 |
| Opus 5 | $0.00000 | $0.00179 |
| Sonnet 5 | $0.00000 | $0.00072 |
| Haiku 4.5 | $0.00000 | $0.00036 |
Grade A, and why
AGENTS.creator-analytics-reporting scanned grade A with 0 findings 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 5d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Use local skills as the primary routing layer for creator analytics and reporting work.
Use creator-content-performance-review for creator post, video, newsletter,
podcast, hook, title, thumbnail, watch-time, retention, audience response, and
next-content analysis from supplied analytics.
Use affiliate-performance-report for creator affiliate links, codes, clicks,
conversions, revenue, commissions, attribution caveats, cookie windows, refunds,
and owned-product or sponsor commerce reporting.
Use campaign-recap for sponsor campaign recaps and delivered-asset reporting,
renewal-pitch when reporting turns into a next-campaign ask, and
deliverables-tracker for live links, reporting dates, proof assets, and recap
requirements.
Use metric-definition, metric-narrative, and dashboard-design for KPI
definitions, performance narratives, dashboards, and reporting views.
Use retention-analysis, cohort-analysis, and funnel-analysis for audience
growth, subscriber retention, creator funnels, and cohort comparisons.
Use experiment-readout and experiment-design-validation for hook, title,
thumbnail, format, cadence, CTA, and platform tests.
Use marketing-analytics-attribution and analytics-instrumentation-plan for
UTMs, sponsor links, affiliate tracking, attribution caveats, consent, and
tracking QA.
Keep platform, sponsor, affiliate, CRM, payment, and analytics tools read-only unless the user explicitly approves a specific write, send, or publish action. Do not invent or inflate views, watch time, engagement, conversions, revenue, demographics, screenshots, testimonials, sponsor outcomes, or ROI. Treat attribution as directional unless source systems and tracking rules are verified.
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.
- 5d ago First seen · 36 lines · 0 tokens per session scan A b4115c42f437
AGENTS.creator-analytics-reporting is an agent published in the GitHub repository jeremylongworth-source/AgentSkills (1 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 359 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
github.awesome-copilot.agents
MCP server that suggests repository-specific AI agent skills.
dotnet.skills.plugins.dotnet-test.agents
MCP server that suggests repository-specific AI agent skills.
runceel.ai-dev-template..github.agents
MCP server that suggests repository-specific AI agent skills.
addyosmani.agent-skills.agents
MCP server that suggests repository-specific AI agent skills.
dotnet.skills.plugins.dotnet-diag.agents
MCP server that suggests repository-specific AI agent skills.
garrytan.gstack.agents
MCP server that suggests repository-specific AI agent skills.