skills/magnus919_agent-skills

Fork 0

mirror of https://github.com/magnus919/agent-skills.git synced 2026-09-11 19:47:12 +03:00

Files

T

a471888676 feat(capacity-and-cost-engineering): add capacity-and-cost-engineering skill (#199 ) (#224 )

Add a new skill connecting demand, performance, reliability, and spend
decisions. Covers capacity models, unit economics, budget/quota controls,
load/soak test evidence, and SLO-cost tradeoffs with structured templates.

Includes:
- SKILL.md with connected-dimensions framework, working method, four
  labeled scenarios (growth, peak, degraded, cost-constrained), and
  routing table to six adjacent skills
- README.md with five required human-facing sections
- references/discovery-brief.md comparing ownership boundaries across
  financial-modeling, platform-engineering, SRE, product-analytics,
  production-readiness, product-roadmapping, and resilience-and-recovery
- Five fillable templates: capacity-model, unit-economics-record,
  budget-quota-decision, load-soak-test-plan, slo-cost-tradeoff-record
- evals/evals.json with five output-quality cases: growth-forecast,
  peak-event, slo-cost-conflict, quota-decision, misleading-unit-cost
- Regenerated marketplace, Codex, and llms.txt catalogs (117 skills)
- Updated root README catalog section and skill-triggers index

Co-authored-by: username <username>
Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>

2026-08-02 18:41:03 -04:00

4.0 KiB

Raw Blame History

Budget / Quota Decision

Fill this template to define a budget threshold or quota/rate-limit enforcement decision with operational consequences.

Budget definition

Scope: [fill: service, team, project, or platform — what this budget covers]
Budget owner: [fill: name or role accountable for budget decisions]
Period: [fill: monthly / quarterly / annual]
Budget amount: [fill: $X per period]
Cost attribution method: [fill: how costs are attributed to this scope — tags, account structure, manual allocation]

Threshold configuration

Threshold	Type	Value	Trigger	Operational consequence	User-facing impact
[fill: 70%]	Alert	[fill: $Y]	[fill: notification to budget owner + cost channel]	[fill: review spending trend; no automated action]	[fill: none]
[fill: 90%]	Soft cap	[fill: $Z]	[fill: throttle non-critical workloads; reduce provisioning]	[fill: autoscaling ceiling lowered; batch jobs deferred]	[fill: degraded performance for non-core functions]
[fill: 100%]	Hard cap	[fill: $BUDGET]	[fill: deny new resource provisioning; rate-limit ingress]	[fill: requests above cap rejected with 429]	[fill: service unavailable for requests exceeding cap]

Quota / rate-limit enforcement

Enforcement mechanism: [fill: API gateway rate limiter, resource-quota admission controller, cloud budget action, or equivalent]
Rate-limit scope: [fill: per-user, per-IP, per-API-key, per-service, or global]
Rate-limit value: [fill: e.g., 1000 requests/second, 500 concurrent connections]
Quota period: [fill: per-second, per-minute, per-day, per-month]
Hard vs burst: [fill: is there a burst allowance above the steady rate? what multiplier and duration?]
Response when exceeded: [fill: HTTP 429 with Retry-After header, queued with backpressure, or denied]
Monitoring: [fill: how is enforcement measured? rate-limit hit counter, quota-usage dashboard, alert on near-exhaustion]

Cost attribution

Attribution method: [fill: resource tags, account/project structure, label-based allocation, or manual]
Shared cost allocation: [fill: how shared infrastructure costs are divided — proportional to usage, fixed split, or other]
Attribution review cadence: [fill: monthly / quarterly]

Anomaly detection

Anomaly trigger: [fill: e.g., spend increase >30% day-over-day, or >15% week-over-week]
Notification: [fill: who is notified and through what channel]
Response procedure: [fill: triage steps — is it legitimate demand, a bug, a misconfiguration, or an attack?]
Escalation: [fill: when does this become an incident? who is the incident commander?]

Assumptions

[fill: current spending pattern is representative of normal operation]
[fill: cost attribution is accurate and complete — state assumption or evidence]
[fill: budget amount is adequate for projected demand — or state what happens if not]
[fill: any other unverified assumption]

Evidence sources

Source	What it provides
[fill: cost dashboard / cloud bill]	[fill: current and historical spend data]
[fill: capacity model]	[fill: projected spend at demand forecast]
[fill: ...]	[fill: ...]

Ownership

Budget owner: [fill: name or role]
Quota/rate-limit config owner: [fill: name or team that configures enforcement]
Anomaly responder: [fill: name or on-call rotation]
Approver: [fill: name of person who approved this budget/quota decision]

Tradeoffs

[fill: e.g., tighter quotas → earlier denial but more predictable cost]
[fill: e.g., generous burst allowance → better user experience but cost-spike risk]
[fill: e.g., hard cap at 100% budget → service may be unavailable; soft cap preferred if core functions can degrade gracefully]

4.0 KiB Raw Blame History