Results for “usage”

Deploys, queries, and debugs AWS Marketplace usage-based (PAYG) metering — the pipeline (ResolveCustomer, BatchMeterUsage, EventBridge via SAM) and querying/debugging metering records, statuses, failures, discrepancies. Covers Concurrent Agreements (CustomerAWSAccountId + LicenseArn), multi-product, CloudTrail Event History (90 days; never CloudTrail Lake), Seller Reports (Billed Revenue/Usage columns + CSV/SDDS parsing), existing-stack detection, metering region for BatchMeterUsage/MeterUsage (DisabledApiException), metered AMI/Container + IAM roles, where registration data lives (customer-profile table), legacy ProductCode + CustomerIdentifier, DuplicateRecord/CustomerNotSubscribed, bad LicenseArn. Also SCOPES adjacent asks — flat-rate/SaaS-Subscription "do I still meter", CCP included-units + overage, contract term/annual renewal, forecasting future bills/usage — with the right answer or a one-line redirect. Use for any BatchMeterUsage/ResolveCustomer or SaaS usage-billing question.

The English summary is being prepared. Showing the original description.

View recorded output tokens, cache-read tokens, response counts, and available mode attribution for a Claude Code session. In other agent environments, find the native usage report where supported, without treating observed usage as proof of savings.

• Checking recorded token usage for the current session
• Reviewing response counts and mode attribution
• Aggregating recorded output across sessions

Review AI call logs by provider, model, time range, status, and cost. Aggregate token usage, export logs, configure budgets, and inspect response times and prompt cache statistics to understand usage and performance.

• Investigate failed calls in filtered logs
• Aggregate token usage and costs across connections
• Configure budgets and token limits

Inspect AI costs, token usage—the units used to measure model input and output—and call logs from the OmniRoute command line. Filter records, review spending by connection, and export usage reports for further review.

• Review AI spending for a selected period
• Compare usage by provider or model
• Search and monitor API call logs

Turn local Claude Code session history into a personal activity report, cross-checked with local Git history. Generate Markdown and standalone HTML showing project activity, touched files, related commits, and each project's share of compute usage.

• Explaining Claude Code usage to a manager
• Reviewing monthly activity across projects
• Preparing evidence for a personal performance review

Retrieve GitHub Copilot usage for an organization or enterprise through the GitHub CLI and REST API. Summarize active users, suggestion acceptance, and chat activity, with aggregate results or per-user tables for selected dates.

• Check Copilot adoption across an organization
• Review suggestion acceptance rates and chat usage
• Compare usage across individual users

Arm proactive 5-hour usage protection for long Claude Code sessions (batch, subagents, high window % at start). Daemon reads account-level 5-hour window usage (not per-session). User types /usage-guard at session start. Re-arm every sitting. If user mentions usage-guard by name, read this file and run arm.sh.

The English summary is being prepared. Showing the original description.

Check AltLLM Portal credit, expiry dates, billing transactions, and usage through the local altllm CLI. Review activity by period, model, or API key, and redeem promo codes using a saved Portal session.

• Check credit, expiry dates, and available models
• Review billing transactions by type
• Compare usage by period, model, or API key

Check current Claude usage limits (session and weekly) with ASCII progress bars. Trigger when the user asks about usage, quota, limits, rate limits, how much Claude they've used, remaining capacity, or phrases like "check usage", "usage status", "how much quota left", "am I close to the limit", "用量", "额度", "配额".

The English summary is being prepared. Showing the original description.

Fix macOS app hard crashes (EXC_CRASH / SIGKILL) caused by accessing TCC-protected APIs without the matching Info.plist usage description key. Use when: (1) App crashes immediately when touching Photos, Contacts, Calendar, Reminders, Location, Microphone, Camera, Screen Recording, etc., (2) Crash report shows `Exception: EXC_CRASH (SIGKILL)` with `Termination namespace: TCC`, (3) Crash stack includes `TCC.__TCC_CRASHING_DUE_TO_PRIVACY_VIOLATION__`, (4) Termination details contain "This app has crashed because it attempted to access privacy-sensitive data without a usage description", (5) Flutter macOS publish / gallery-save flow crashes on Gal.putVideo, PHPhotoLibrary, CNContactStore, etc. Critical distinction: macOS does NOT return a deny error — it SIGKILLs the process. This skill also covers the NSPhotoLibraryUsageDescription vs NSPhotoLibraryAddUsageDescription distinction that trips many apps.

The English summary is being prepared. Showing the original description.

Create an SVG usage card from local Claude Code, Codex, Gemini CLI, and OpenCode logs. It summarizes token counts, equivalent API cost, consecutive activity days, and each agent's share for inclusion in a README or documentation.

• Displaying coding-agent usage in a README
• Sharing an activity summary across multiple agents
• Showing token counts and equivalent API cost

Summarize Claude Code token usage and estimated spending from the local ECC metrics log. Review costs by model, session, or date, compare spending with budgets, and export records to CSV while avoiding duplicate counting of session totals.

• Comparing today's spending with yesterday's
• Reviewing costs by model or session
• Checking spending against a budget

Look up Ant Design React components in official documentation to find available settings, default values, and usage examples. Check subcomponents and methods, and consult type definitions in the antd package when TypeScript details are needed.

• Checking component settings and default values
• Finding usage examples and demo code
• Looking up available subcomponents and methods

Look up a project's existing UI components in Storybook, including their props, or configuration inputs, and usage examples. Use the findings to answer questions and identify components to reuse before building duplicates.

• Find existing UI components
• Check component props and usage examples
• Answer questions about component usage

Capture token usage from Claude Code session logs, calculate USD costs using the supplied pricing reference, and save structured records to AgentDB. Review totals by model and tier, and provide data for cost reports.

• Record costs after a block of work
• Save final usage totals at session end
• Capture usage periodically during long sessions

Answer questions about a Muse subscription using retrieved account information. Check the current plan, usage allowance, reset timing, and credit availability, or explain available plans and prices while distinguishing confirmed details from information the tool cannot verify.

• Check the current Muse subscription plan
• Review usage allowance and credit availability
• Find out when the usage allowance resets

Analyze Claude Code session transcripts and create an interactive HTML usage report. Explore token consumption, cache performance, subagents, skills, and costly prompts, with findings and improvement suggestions tied to the actual usage data.

• Reviewing token usage over a chosen period
• Comparing consumption across projects and skills
• Investigating cache performance and breaks

Analyze proxy, DNS, and firewall traffic logs to uncover unapproved SaaS and cloud services. Group usage by domain, compare it with approved applications, and produce a report with traffic volumes, user counts, risk scores, and remediation recommendations.

• Finding unapproved SaaS and cloud services
• Measuring traffic volumes and users by service
• Prioritizing services by potential data leakage risk

Retrieve Google Workspace audit logs, which record account activity, and usage reports through gws. Review activity in applications such as the Admin console and Google Drive, or inspect statistics for the organization, users, and entities.

• Reviewing Admin console and Google Drive activity
• Checking organization usage statistics
• Retrieving usage reports for users

Integrate Stripe payments and subscriptions into web applications, including trials, prorated plan changes, usage billing, customer portals, and invoices. Follow implementation patterns and local testing steps, with webhook signature checks and duplicate event handling to support reliable billing updates.

• Add subscription checkout with a free trial
• Implement plan changes with a proration preview
• Add usage-based billing to a subscription product

Read provider usage, limits, credits, and installation or configuration health through CodexBar. Returns JSON for enabled providers or a selected provider, while hiding secrets and leaving configuration and authentication unchanged.

• Checking usage and limits across enabled providers
• Checking credits for a selected provider
• Diagnosing installation or configuration health

Inspect Mac performance to find processes using excessive CPU, GPU, memory, or energy. Combine measurements with explanations of known system processes to diagnose slowness, heat, and startup load, then recommend actions without changing system settings.

• Find the cause of a slow Mac
• Investigate loud fans and overheating
• Check memory pressure and swap activity

Draft an AI usage policy for a law firm or legal team using published policies and guidance. Adapt selected sections to the organization, cite sources, and flag decisions and open questions for attorney review.

• Creating a first AI usage policy draft
• Updating an existing policy for regulatory changes
• Drafting rules for confidential data and AI tool approval

Plan pricing for AI products by comparing charges based on usage, tasks, or results. Use customer value and computing costs to shape pricing tiers, usage limits, hybrid plans, and margin improvement strategies.

• Choosing how to charge for an AI product
• Designing pricing tiers and usage limits
• Reviewing low margins