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 getsimba-ai/simba-mcp --skill simba-data-reportinggit clone --depth 1 https://github.com/getsimba-ai/simba-mcpWrote 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/getsimba-ai/simba-mcp/simba-data-reporting)<a href="https://agentmods.dev/skills/getsimba-ai/simba-mcp/simba-data-reporting"><img src="https://agentmods.dev/badge/skills/getsimba-ai/simba-mcp/simba-data-reporting/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/getsimba-ai/simba-mcp/simba-data-reporting"><img src="https://agentmods.dev/badge/skills/getsimba-ai/simba-mcp/simba-data-reporting.svg" alt="Reviewed on agentmods" width="80" 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.00024 | $0.00229 |
| Opus 5.5 | $0.00010 | $0.00092 |
| Sonnet 5.5 | $0.00005 | $0.00046 |
| Haiku 4.5 | $0.00002 | $0.00023 |
Grade A, and why
simba-data-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 14d 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
Report actual data
Use for actual sales/KPI and spend by window or grouping, including pipeline-ingested datasets already stored as uploads. All four profiles expose the required reads.
- Use a supplied dataset ID directly. If unknown, use
list_uploads, thenget_upload. - Inspect schema/declared roles when needed; never infer KPI meaning from a column name.
- Read reporting and recovery before
get_data_report. - Retain source/version/digest, units, aggregation and data_through. Actual data totals are separate from MMM attribution, platform conversions and forecast results.
- Narrow oversized reads. Missing roles or unavailable data require a clarification or owner handoff, never an upload, pipeline refresh or model fit.
Follow executable examples for complete synthetic discovery/reporting and refusal/recovery paths.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 14d ago First seen · 23 lines · 24 tokens per session scan A 159b4b361cdd
simba-data-reporting is a skill published in the GitHub repository getsimba-ai/simba-mcp (3 stars, last pushed 3d ago), licensed MIT. It adds 24 tokens to every session and 229 once invoked, about $0.0001 per session on Opus 5.5. 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-10-03.
Other skills, from other repositories
mmm-api-reference
Exact pymc-marketing API reference for MMM code, verified against v1.1.0. Use when writing or reviewing pymc-marketing code, checking constructor signatures, method names, return types, import paths, or plotting/evaluation/optimisation calls. Also use when migrating 0.x code to 1.x, debugging ImportError or…
mmm-channel-semantics
How each type of marketing channel should be represented in an MMM — its role (paid media, reach-and-frequency, organic, non-media treatment, control), whether it is driven by spend or exposure, its carryover and saturation behaviour, and whether a ROAS is even defined for it. Use when deciding what a column means…
mmm-data-engineering
Building the MMM dataset: sourcing, joining, aggregating, handling missing data, currency and inflation, fiscal calendars, taxonomy mapping, outliers and reproducible pipelines. Use when assembling data from platform exports and finance systems, deciding how to fill gaps, choosing daily vs weekly, aligning spend to…
mmm-experimentation-calibration
Designing incrementality experiments and folding their results into an MMM. Use when planning a geo holdout, matched-market test, ghost-ads or conversion-lift study, sizing an experiment, converting a lift result into a model constraint, calibrating with pymc-marketing addlifttestmeasurements, Meridian ROI priors, or…
mmm-meridian
Google Meridian reference and practice guide, verified against google-meridian 1.8.0. Use when building, reviewing or debugging a Meridian model, wiring InputData and CoordToColumns, setting ROI/mROI/contribution priors, configuring knots and adstock/saturation specs, handling reach-and-frequency channels, running the…
mmm-model-building
Constructing an MMM with pymc-marketing 1.x — model architecture, adstock and saturation choice, prior specification, likelihood and link function, seasonality and trend, panel dimensions, and the fitting strategy. Use when building a new model, choosing transformations, writing modelconfig, setting priors from…