AgentStack
SKILL verified MIT Self-run

Ai Cost And Metering

skill-peterbamuhigire-skills-web-dev-ai-cost-and-metering · by peterbamuhigire

>-

No reviews yet
0 installs
12 views
0.0% view→install

Install

$ agentstack add skill-peterbamuhigire-skills-web-dev-ai-cost-and-metering

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Ai Cost And Metering? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

AI Cost And Metering

Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, +256 784 464178.

Use When

  • Design AI usage metering, cost attribution, quotas, chargeback, or billing controls.
  • Model AI cost by tenant, feature, provider, model, request, or agent task.
  • Connect cost evidence to plan limits, entitlement enforcement, and customer-facing billing.

Do Not Use When

  • The work is not AI-specific or agentic-AI-specific.
  • A narrower retained AI parent skill fits the request better.

Required Inputs

  • Product, tenant, user, data, risk, and operational context relevant to the AI workflow.
  • Target artifact: design, implementation plan, audit, test strategy, UX flow, commercial policy, or runbook.
  • Constraints from security, privacy, reliability, billing, support, and compliance stakeholders when relevant.

Workflow

  1. Read this SKILL.md first.
  2. Load [references/routing.md](references/routing.md) to select the absorbed child reference that matches the task.
  3. Load only the selected child reference files needed for the current request.
  4. Produce execution-oriented output with assumptions, risks, evidence, and next actions where relevant.

Quality Standards

  • Keep routing explicit: name which reference files were used when the work depends on absorbed material.
  • Preserve tenant isolation, auditability, cost controls, safety gates, and operational evidence when they matter.
  • Prefer concrete contracts, checklists, tables, schemas, runbooks, and decision records over broad summaries.

Anti-Patterns

  • Loading every absorbed reference by default.
  • Treating AI-specific billing, compliance, safety, or UX concerns as generic SaaS work without checking AI failure modes.
  • Hiding retired skill names; old slugs must remain discoverable through [references/routing.md](references/routing.md).

Outputs

  • A concrete deliverable matched to the request: architecture, implementation plan, audit, policy, runbook, UX flow, test strategy, or operating model.
  • The selected consolidated reference files and any assumptions, risks, evidence requirements, or follow-up actions that affect execution.

References

  • [references/routing.md](references/routing.md) maps retired child skill slugs to their consolidated reference folders.

Consolidated Child References

  • Load [references/routing.md](references/routing.md) to map retired AI child skill slugs to their reference modules.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.