I Found a Cost Blind Spot in an Open-Source Agent Framework

Description and use

Missing Bedrock model families in the Strands Agents SDK caused incorrect cost attribution. Adding the missing entries and tests fixed the issue.

Problem

Missing Bedrock model families in the Strands Agents SDK caused incorrect cost attribution and routing in cost‑governed AI agent deployments.

Outcome

The update resolved a cost‑governance blind spot, ensuring accurate cost attribution and preventing misleading dashboards.

Workflow

• 1. Traced SDK source to identify missing family lookups.
• 2. Documented missing families and downstream effects in issue #4852.
• 3. Added four new tests for the missing families.
• 4. Ran full test suite (152 passed).
• 5. Submitted PR #4853 to update the registry.

Evidence

The Strands harness SDK keeps a registry of model families for Bedrock — it uses the family to make decisions about capabilities and pricing behavior.

Source

I added four new tests, ran the full suite (152 passed), and confirmed the 13 pre-existing failures also failed on clean main, so they weren't mine.

Source

If you can't identify the model, you can't attribute its cost correctly, you can't route to or away from it intelligently, and your burn-rate dashboard has a hole in it.

Source