1,681 件 ・ 関連度順
概要と使いどころ
Index local coding-agent sessions into a searchable SQLite-backed view so you can inspect usage, compare failures, and recover prior context quickly.
日本語の概要は準備中です。原文の説明を表示しています。
Run CodeBurn locally or as an MCP server so agents can inspect token usage, cost, model mix, project spend, and budget waste across coding tools.
日本語の概要は準備中です。原文の説明を表示しています。
Instruments Anthropic API calls to log token usage, latency, and cost per request using the Anthropic TypeScript SDK. Wraps the anthropic.messages.create method to capture usage.input_tokens, usage.output_tokens, and timing from the API response. Writes structured logs to CloudWatch Logs via the AWS SDK v3 CloudWatchLogsClient.
日本語の概要は準備中です。原文の説明を表示しています。
Use Caliper to run real agent tasks with and without a skill, MCP server, or rule change so reliability and token cost are measurable.
日本語の概要は準備中です。原文の説明を表示しています。
Model selection strategy and routing. Use when choosing between models for different task types, subagent configurations, or optimizing token cost vs quality tradeoffs.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user says 'run a sale', 'discount this category', 'set up a coupon', 'reprice these products', 'end the sale', or asks what a discount would cost them. Plans the price change, shows it as a preview before anything moves, writes it with a snapshot, and can put it back.
日本語の概要は準備中です。原文の説明を表示しています。
Display input/output args, return object and cost time of a Python method invocation in a live process. Use this to observe function behavior at runtime — see what arguments go in, what comes back, and how long it takes. This is the most frequently used diagnostic command.
日本語の概要は準備中です。原文の説明を表示しています。
Use when Codex must make a high-quality judgment on any complex problem, not only technical problems. Trigger when a question has high complexity, uncertainty, cost of being wrong, long-term impact, value tradeoffs, possible structural causes, or when the user asks for 全面思考, 深度理解, 系统性分析, 帮我想清楚, 从根上看, 这件事到底怎么看, 方法论, 复杂问题拆解, 系统方案, 架构判断, 策略判断, or 根因分析. Also trigger for project and engineering high-risk scenarios such as multi-module, multi-environment, multi-data-source, multi-state, financial truth, live trading, ledger, revenue, customer assets, order governance, broker interfaces, online availability, major solution selection, and system closure.
日本語の概要は準備中です。原文の説明を表示しています。
Designs rebalancing triggers with calendar-based, threshold-based, and hybrid approaches with tax and cost optimization. Use when designing rebalancing rules, optimizing rebalancing frequency, or modeling turnover impact.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes construction risk with EPC contract review, delay and cost overrun scenarios, and completion guarantee structures. Use when modeling construction risk, evaluating EPC terms, or stress testing project timelines.
日本語の概要は準備中です。原文の説明を表示しています。
Builds currency hedging models with rolling forward programs, option-based strategies, and cross-hedge analysis for international portfolios. Use when designing hedge programs, analyzing hedge ratios, or evaluating FX protection costs.
日本語の概要は準備中です。原文の説明を表示しています。
Builds carbon credit models with offset generation analysis, verification costs, and market pricing dynamics for carbon-linked investments. Use when modeling carbon credits, analyzing offset economics, or evaluating carbon market exposure.
日本語の概要は準備中です。原文の説明を表示しています。
Structures FX hedging strategies for international portfolios with natural hedge identification, instrument selection, and cost analysis. Use when managing currency risk, designing FX hedges, or analyzing translation exposure.
日本語の概要は準備中です。原文の説明を表示しています。
Structures customer diligence with interview guides, NPS analysis, switching cost assessment, and usage pattern evaluation. Use when conducting customer references, validating product-market fit, or assessing customer satisfaction.
日本語の概要は準備中です。原文の説明を表示しています。
Assesses operational improvement opportunities with cost rationalization, revenue stabilization, and management changes for distressed businesses. Use when evaluating turnaround plans, identifying operational improvements, or assessing management capability.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluates unitranche structures with first-out/last-out splits, blended pricing, and agreement among lenders provisions. Use when analyzing unitranche options, comparing unitranche vs traditional structures, or modeling blended costs.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluates assumption, rejection, and assignment decisions for executory contracts and unexpired leases in bankruptcy. Use when analyzing contract decisions, evaluating lease rejections, or modeling cure cost exposure.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluates geographic expansion strategies with market entry sequencing, localization requirements, and international unit economics. Use when analyzing expansion plans, assessing international readiness, or modeling geo-expansion costs.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluates competitive advantage sustainability with switching costs, network effects, data assets, and brand strength analysis. Use when assessing competitive moats, analyzing defensibility, or evaluating long-term positioning.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluates commodity swaps, options, and exotic structures with seasonality, convenience yield, and storage cost analysis. Use when pricing commodity derivatives, analyzing energy structures, or evaluating commodity hedging.
日本語の概要は準備中です。原文の説明を表示しています。
Parse Claude Code JSONL session logs from ~/.claude/projects/ for tool call inventory, token costs, error detection, subagent traces, and compaction detection
日本語の概要は準備中です。原文の説明を表示しています。
Estimate per-turn token attribution across 6 categories in Claude Code sessions to show where context budget is spent
日本語の概要は準備中です。原文の説明を表示しています。
Manage Backblaze B2 cloud storage. List files, audit usage, estimate cost, clean up stale data, review security posture, and manage lifecycle rules. Use when the user mentions B2, Backblaze, object storage buckets, or storage cleanup.
日本語の概要は準備中です。原文の説明を表示しています。
Policy for the cross-model council: when to hand off to an installed sibling plugin's own slash command (`/codex:*`) versus dispatching our `delegation-runner` (backend: codex|agy|…), which backend to pick, what permission posture to use, and the fan-out/cost discipline that applies regardless of backend — plus the council layer built on that substrate: which play to run, how a cast gets picked from the project roster, budget guardrails, and where project policy/commission config lives. Consult before delegating out to a peer agentic CLI, before choosing between a sibling plugin's command and our runner, before choosing a permission posture, before fanning out more than one external delegation concurrently, or before running a council play (`/…:council-run`).
日本語の概要は準備中です。原文の説明を表示しています。