agentsclimarketplace

Cost impact review

Skill motao123/dev-workflow-kit/cost-impact-review

21 markdown-first software delivery workflow skills for Claude Code, Codex, and compatible agents. Standalone skill kit covering planning, debugging, CI, review, security, rollout, performance, data quality, and post-incident workflows.

Install
npx -y skills add motao123/dev-workflow-kit --skill cost-impact-review

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when a change may increase infrastructure or runtime cost (compute, storage, network egress, third-party API calls, observability volume) and the team needs a focused cost-impact review before merge or rollout.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.9 KB, as published. Nobody here has run it

Cost Impact Review

Use this skill when the main risk is unit economics or infra cost regression, not correctness.

Trigger Conditions

Use this skill when:

  • a change adds new database queries, API calls, or background work that may scale per-request
  • caching, batching, or pagination behavior is changing
  • third-party SaaS or paid API usage may grow
  • log, trace, or metric volume may increase noticeably
  • the team wants a cost regression check before release

Do not use this skill for license/compliance review or for performance investigation of an existing slowdown.

Workflow

  1. Identify the change and the cost drivers it touches.
  2. Estimate cost direction: per-request, per-user, per-event, or per-deploy.
  3. Compare with cheaper alternatives (caching, batching, lazy paths).
  4. Flag risk hotspots that scale with traffic.
  5. Recommend smallest mitigations or a measurement plan.
  6. Suggest verification once rollout begins.

Output

For non-trivial work, provide:

  • affected cost drivers
  • likely cost direction and rough magnitude
  • risk hotspots
  • recommended optimizations or guards
  • verification plan

Coordination

After cost review:

  • use architecture-refactor-guidance if a structural change is the right mitigation
  • use release-rollout-strategy to add cost-aware checkpoints
  • use ship-readiness if cost risk is the last release blocker

Invocation Examples

  • "Use cost-impact-review from dev-workflow-kit to check whether this change increases infra or per-request cost."
  • "Use cost-impact-review to estimate whether this new third-party call will materially raise our bill."
  • "Use cost-impact-review before release because the new query might run on every page load."

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.