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 Snowflake-Labs/cocoplus --skill meter-chargebackgit clone --depth 1 https://github.com/Snowflake-Labs/cocoplusWrote 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/snowflake-labs/cocoplus/meter-chargeback)<a href="https://agentmods.dev/skills/snowflake-labs/cocoplus/meter-chargeback"><img src="https://agentmods.dev/badge/skills/snowflake-labs/cocoplus/meter-chargeback/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/snowflake-labs/cocoplus/meter-chargeback"><img src="https://agentmods.dev/badge/skills/snowflake-labs/cocoplus/meter-chargeback.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.00033 | $0.00734 |
| Opus 5 | $0.00016 | $0.00367 |
| Sonnet 5 | $0.00007 | $0.00147 |
| Haiku 4.5 | $0.00003 | $0.00073 |
Grade A, and why
meter-chargeback 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.
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CocoMeter Chargeback
Use this skill for $meter chargeback refresh, $meter chargeback invoice, and $meter chargeback onboarding.
Before proceeding, verify that .cocoplus/ exists. If not, output: "CocoPlus not initialized. Run $pod init first." Then stop.
Source Rules
CocoMeter chargeback reads token/inference usage from Snowflake's Cortex Code usage history surfaces and, when enabled, warehouse compute from query attribution history. Treat the chargeback fact table as governance evidence, not a cosmetic dashboard:
- Token credits come from the Cortex Code CLI, Desktop, and Snowsight usage history surfaces.
- Warehouse credits join through
query_tag.appandQUERY_ATTRIBUTION_HISTORY.CREDITS_ATTRIBUTED_COMPUTE. includeWarehouseincocoplus.tomlcontrols whether warehouse credits are included.SNOWFLAKE.LOCAL.AI_OBSERVABILITY_EVENTSCodingAgent.Step-0spans are used for near-real-time observability when present.- Exclude
SYSTEM, sandbox runs, and background metadata-query traffic.
$meter chargeback refresh
Run a 35-day trailing delete/insert refresh. On first setup, load 60 days. Schedule the Snowflake task for 06:00 UTC daily.
For local validation or dry-run fixtures, use:
invoke cocometer/chargeback-refresh --input <fixture.json>
The applies the same deterministic rules used by the warehouse implementation:
- Strip
<system-reminder>...</system-reminder>blocks before prompt persistence. - Extract SQL from tool argument arrays.
- Resolve cost centers in this order: explicit user map, user object tag, role map,
UNMAPPED. - Produce invoice-ready per-user totals.
$meter chargeback invoice
Generate one HTML and one CSV invoice package per user from the refreshed chargeback facts. Each invoice must include token credits, warehouse credits when included, total credits, credit-rate amount, cost center, and unmapped status.
$meter chargeback onboarding
Report setup readiness:
schemaReadyfactHasDatacostCentersMappedunmappedUsersspansPresent
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 · 78 lines · 33 tokens per session scan A abb8ebda8855
meter-chargeback is a skill published in the GitHub repository Snowflake-Labs/cocoplus (720 stars, last pushed 6d ago), licensed MIT. It adds 33 tokens to every session and 734 once invoked, about $0.0002 per session on Opus 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-09-03.
Other skills, from other repositories
comparable-company-analysis
A workflow for comparing a publicly listed company with similar listed companies. It examines their businesses, financial results, competitors, and recent developments.
财经分析工具包
A set of finance analysis tools for stocks, markets, portfolios, and financial news. It includes data retrieval, technical indicators such as moving averages and RSI, trend analysis, risk assessment, and allocation suggestions.
stripe
Read Stripe account state from a terminal or agent: balance, payment intents, and subscriptions — and perform guarded mutations like canceling a subscription — backed by a bundled stripe-cli script that is read-only first and gates every state-changing command behind a --dry-run/--yes confirmation. Use when an agent…
yc-default-alive-calculator
Evaluate startup runway, burn, revenue, and profitability trajectory using the Default Alive / Default Dead framework. Do not use this skill for weekly growth experiments or operating growth decisions; use yc-weekly-growth-compass for those decisions.
finops-expert
Expert-level cloud financial operations, cost optimization, and cloud economics. Use when the user mentions cloud cost, optimization, cloud economics, or AWS cost, or when the task involves FinOps Fundamentals, Cost Management, FinOps Practices, or Cost Visibility.
actuarial-risk-modeling
Use when analyzing, selecting, validating, or communicating models for insurance, actuarial, financial-risk, or other consequential uncertain outcomes. Covers regression, generalized linear models, frequency-severity, panel and longitudinal data, survival, time series, credibility, reserving, tail risk, calibration…