Buy Vs Build Gain
Use when summarizing Buy vs Build benchmark cases, behavior measurements, expected impact, release notes, or evidence that the ruleset reduces unnecessary code, dependencies, cost, or ownership risk.
Install
$ agentstack add skill-stdin-buy-vs-build-buy-vs-build-gain ✓ 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-stdin-buy-vs-build-buy-vs-build-gain) 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
Buy vs Build Gain
Summarize impact from benchmark data without overstating it. Distinguish measured local overhead from behavior benchmarks that still need agent runs.
Workflow
- Read
benchmarks/behavior-cases.jsonfor behavioral test cases. - Run
npm run benchmarkfor local instruction and hook overhead. - If agent-run results exist, report LOC, files changed, dependencies added, decision-note quality, time, token/cost data, and safety regressions.
- If only cases exist, call them a benchmark plan, not measured impact.
Output
Use this shape:
Measured
- :
Behavior cases
- : expected rung ; baseline risk
Limitations
- Never claim the ruleset reduces LOC, cost, or time until a baseline-vs-enabled agent run has actually been measured.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: stdin
- Source: stdin/buy-vs-build
- License: MIT
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.