Cost Impact Review
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.
Install
$ agentstack add skill-motao123-dev-workflow-kit-cost-impact-review ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-motao123-dev-workflow-kit-cost-impact-review) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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
- Identify the change and the cost drivers it touches.
- Estimate cost direction: per-request, per-user, per-event, or per-deploy.
- Compare with cheaper alternatives (caching, batching, lazy paths).
- Flag risk hotspots that scale with traffic.
- Recommend smallest mitigations or a measurement plan.
- 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-guidanceif a structural change is the right mitigation - use
release-rollout-strategyto add cost-aware checkpoints - use
ship-readinessif 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."
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: motao123
- Source: motao123/dev-workflow-kit
- License: MIT
- Homepage: https://motao123.github.io/dev-workflow-kit/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.