component-inventory

A ledger that notices. One CSV per repo, one row per billable or load-bearing component, refreshed from live provider APIs rather than from memory, and audited on every run for the failure this skill exists to prevent:

A component that costs money, that nobody has decided about, whose figure was assumed rather than measured.

That is not hypothetical. In the james-brennan repo an Aurora Serverless v2 cluster was reported at "about $0/month" from its configured auto-pause while the measured floor was $43.80/month, and after its replacement went live it kept running beside it with nothing in the system saying so.

Read-only, always