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 jxoesneon/Ciel --skill billing-and-monitoringgit clone --depth 1 https://github.com/jxoesneon/CielWrote 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/jxoesneon/ciel/billing-and-monitoring)<a href="https://agentmods.dev/skills/jxoesneon/ciel/billing-and-monitoring"><img src="https://agentmods.dev/badge/skills/jxoesneon/ciel/billing-and-monitoring/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/jxoesneon/ciel/billing-and-monitoring"><img src="https://agentmods.dev/badge/skills/jxoesneon/ciel/billing-and-monitoring.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.00017 | $0.00511 |
| Opus 5 | $0.00009 | $0.00255 |
| Sonnet 5 | $0.00003 | $0.00102 |
| Haiku 4.5 | $0.00002 | $0.00051 |
Grade A, and why
billing-and-monitoring 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 8d 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
CIEL ADAPTATION: Billing & Monitoring (The Revenue Layer)
This skill formalizes the intersection of customer health and system observability. it prioritizes reversible remediation and question-driven dashboards.
Customer Billing Ops
- Identify: Resolve the customer via email or Stripe ID. Map all active/canceled subscriptions and invoices.
- Classify: Distinguish among Duplicate Purchase, Multi-seat Intent, Failed Checkout, or Product Failure.
- Remediate: Perform the safest reversible action first (e.g., Restore self-serve portal access).
- Document: Produce an "Operator Handoff" with the action taken, revenue impact, and follow-up message.
Dashboard Engineering
- Operator Questions: Start with "Is it healthy?", "Where is the bottleneck?", "What changed?".
- Structure: Group by Overview -> Performance -> Resources -> Service-Specific.
- Mandate: Every panel MUST have units, a title, and meaningful threshold colors (Red/Yellow/Green).
- Curation: Remove any panel that doesn't drive a specific operator action.
Deployment Readiness
- Canary Check: Pair billing remediation with a post-fix Canary watch to ensure no regressions.
- Impact Audit: Measure the revenue impact of any proposed changes to subscription tiers.
Anti-Patterns
- Blind Refund: Refunding a charge without identifying if it was a deliberate team purchase.
- Vanity Panels: Creating a dashboard with 50 CPU graphs but no "Error Rate" or "Latency" metrics.
- Secrets in Dashboards: Hardcoding API tokens or DB credentials in Grafana JSON exports.
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.
- 8d ago First seen · 51 lines · 17 tokens per session scan A f88843ff8b56
billing-and-monitoring is a skill published in the GitHub repository jxoesneon/Ciel (1 stars, last pushed 5d ago), licensed Apache-2.0. It adds 17 tokens to every session and 511 once invoked, about $0.0001 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
gumroad-support-refund-request
Handle buyer refund requests on Gumroad — standard, subscription, and duplicate-charge cases. Use when a ticket asks for money back, reports a double charge, or a seller is unresponsive to a refund. Decides eligibility, executes, and replies.
api-usage-biller
Usage-based pricing is hard to track. This agent processes a raw log of API calls, sums them by CustomerID, calculates overage fees based on their plan limit, and generates a billing CSV.
stock-analyzer
A comprehensive stock deep analysis tool that combines real-time quotes, fundamental metrics, technical indicators, and growth analysis into a single professional report. Supports A-share, US stocks, HK stocks. Generates detailed investment recommendations with risk assessment and actionable trading strategies.
Coinbase Automation
Coinbase Automation: list and manage cryptocurrency wallets, accounts, and portfolio data via Coinbase CDP SDK.
lov-skill-pricing
A pricing workflow for creating an explanation-backed pricing card for an AI agent skill. It considers creation and maintenance effort, user value, scarcity, buyer confidence, and distribution potential.
market-research
A guide for conducting market research, including research standards, research modes, and checks on investors or investment funds. The description does not specify its exact outputs or workflow.