[FRWEBINT-1677] Add Claude Code Costs widget group to Anthropic dashboard

[BoyangHuang]

Summary

Surfaces the new cost_type:session_usage CCM tag (added in DataDog/dogweb#166424) so customers can see Claude Code spend separately from API token spend.

The new "Claude Code Costs" group on the overview dashboard contains:

• Claude Code Spend (past 30d) — query_value summing all.cost{providername:Anthropic,cost_type:session_usage,...}.
• Daily Claude Code Costs by Workspace (30 Days) — timeseries broken down by workspace_name.
• A note explaining how this differs from the token-based widgets and pointing to claude_code.estimated_cost for per-user attribution.

Customer context

Digital Asset filed FRWEBINT-1677.

Companion PR

Pairs with DataDog/dogweb#166424. The dashboard widget will only have data once that change ships.

Test plan

• Verify widget renders correctly in the integration tile preview.
• Once dogweb#166424 ships, confirm sum:all.cost{cost_type:session_usage} returns data for tenants with Claude Code seats.

Context

Generated as part of the FR Viability Assessment — 2026-05-07.

[dd-octo-sts]

Validation Report

All 20 validations passed.

Show details

Validation	Description	Status
agent-reqs	Verify check versions match the Agent requirements file	✅
ci	Validate CI configuration and Codecov settings	✅
codeowners	Validate every integration has a CODEOWNERS entry	✅
config	Validate default configuration files against spec.yaml	✅
dep	Verify dependency pins are consistent and Agent-compatible	✅
http	Validate integrations use the HTTP wrapper correctly	✅
imports	Validate check imports do not use deprecated modules	✅
integration-style	Validate check code style conventions	✅
jmx-metrics	Validate JMX metrics definition files and config	✅
labeler	Validate PR labeler config matches integration directories	✅
legacy-signature	Validate no integration uses the legacy Agent check signature	✅
license-headers	Validate Python files have proper license headers	✅
licenses	Validate third-party license attribution list	✅
metadata	Validate metadata.csv metric definitions	✅
models	Validate configuration data models match spec.yaml	✅
openmetrics	Validate OpenMetrics integrations disable the metric limit	✅
package	Validate Python package metadata and naming	✅
readmes	Validate README files have required sections	✅
saved-views	Validate saved view JSON file structure and fields	✅
version	Validate version consistency between package and changelog	✅

View full run