attribution

DE//AGENT currently lists 4 resources under attribution: 2 tutorials, 1 skill, 1 plugin. Everything below is derived from the live registry — counts, capabilities, verification state and security posture come from the curated records, never from marketing copy.

Documented learning objectives across these resources:

• Attribute compute cost to a pipeline run — via Compute unit economics for a pipeline
• Define a unit metric that resists regressions — via Compute unit economics for a pipeline
• Set an alert on cost-per-run, not on total spend — via Compute unit economics for a pipeline
• Attribute warehouse/cluster spend with /cost-by-pipeline — via Attribute spend with the Cost Lens plugin
• Compute unit economics with /unit-cost — via Attribute spend with the Cost Lens plugin
• Guard cost-per-run regressions with /cost-guard — via Attribute spend with the Cost Lens plugin

These resources map to stage: Reliability (4). Follow the four-phase roadmap to place this topic inside a progression instead of learning it in isolation.

Every entry, its shape and its trust state — sorted by the registry's composite score. This table is the honest version of a marketing comparison: no sponsored placements, no unverifiable claims.

How scores are computed: source quality score.

Highest composite score first:

1. Compute unit economics for a pipeline score 34.15 — beginner
2. Attribute spend with the Cost Lens plugin score 34.15 — intermediate
3. Cost Unit-Economics Reporter score 30.4 — intermediate

Scores rank provenance, completeness and trust — read how verification works before adopting anything.

Start here if you're new: Compute unit economics for a pipeline.

Reach for these with production experience: Cost Lens.

Security-flagged entries: Cost Unit-Economics Reporter (4 flags), Cost Lens (5 flags). Flags mean the record declares capabilities like credential use or write access — read the security posture on each page before connecting.

• Compute unit economics for a pipeline — Turn cluster and warehouse billing into unit economics — cost per run, per 1M rows, per model build — so a regression shows up as a number, not a surprise invoice. The Cost Optimiz… details
• Attribute spend with the Cost Lens plugin — Install the Cost Lens plugin and use its three commands to attribute spend, compute unit economics, and guard cost-per-run. The plugin pairs the unit-economics skill with the Spark… details
• Cost Unit-Economics Reporter — Turns cluster/warehouse billing into unit economics (cost per 1M rows, per run, per model) so a 4x regression shows up as a number, not a surprise invoice. details
• Cost Lens — Attributes warehouse/cluster spend to pipelines, computes unit economics, and alerts on cost-per-run regressions rather than on total spend. details

Real install commands from the registry — read the source before running any of them:

npx de-agent-platform add cost-unit-economics-reporter

Cost Unit-Economics Reporter — review first

amp plugin add de-agent/cost-lens

Cost Lens — review first

Adjacent topics: cost (4 shared), finops (4 shared), tutorial (2 shared), plugin (2 shared), unit-economics (2 shared).

Study path: the roadmap places this topic in a progression · the scoring model explains the numbers · the trust rule catalog shows every security check these entries passed through.