najmanaaz

Opex Agent — DevOps skill for Claude Code

DevOps community

Turns a business goal into a resource plan on AWS: Lambda Function URL, Claude on Amazon Bedrock with schema-enforced tool output, DynamoDB quotas.

How to install Opex Agent

This entry records only its repository, not the path inside it, so there is no exact command to give. Open najmanaaz/opex-agent and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Opex Agent does

Turns a business goal into a resource plan on AWS: Lambda Function URL, Claude on Amazon Bedrock with schema-enforced tool output, DynamoDB quotas.

Alternatives in DevOps

  • Skill — Web extraction engine with antibot bypass 549 ★
  • Helm Conductor — Use the @helm-conductor agent to orchestrate the engineering cycle — sequence features, decide what to work on 523 ★
  • Check Schema Version — Check the Flyway schema version of the SQLite database on a Docker volume 205 ★

README

OpEx Agent

**Turns a business goal into a resource plan: sub-goals with dependencies, roles and capacity, skills and hiring gaps, cost factors, the P&L line it moves, and risks. A signed-in app on AWS with Claude on Amazon Bedrock.**

Live: **[opex.t4tangerine.com](https://opex.t4tangerine.com)** (free account) · Method: [Goal Decomposition article](https://www.t4tangerine.com/blog/goal-decomposition), Part 3 of *Goal Planning That Actually Works* · Built by [T4Tangerine](https://www.t4tangerine.com)


What it does

Input: a goal ("Cut Tier 1 first-response time from 4.2 to under 2 hours by the end of Q1"), the people you have (roles and headcount), a timeline in weeks, and the functions involved.

Output: a structured plan, saved to the user's account and downloadable as a PDF.

  • summary: the goal restated in actionable terms
  • subGoals: 3–6 steps, each with a duration and its dependencies
  • roles: who works on it, how many, at what capacity, and why
  • hiringNeeded: roles the team lacks, with priority
  • skills, estimatedDuration and costFactors (European salary benchmarks)
  • ppiLine: the P&L line it moves (Revenue, COGS, OpEx, CapEx) and in which direction
  • risks: severity and mitigation

Architecture

flowchart LR
    B[Browser] -->|HTTPS| CF[CloudFront + S3
opex.t4tangerine.com] B -->|auth code + PKCE| COG[Cognito managed login
shared T4Tangerine user pool] B -->|ID token| API[API Gateway HTTP API
Cognito JWT authorizer] API --> P[plans λ
validate · quotas · CRUD] P --> Q[(DynamoDB quotas
TTL counters)] P --> T[(DynamoDB plans
userId + planId)] P -->|async invoke| W[worker λ] W -->|Converse, forced tool call| BR[Claude Sonnet 4.6
Bedrock EU inference profile] W -->|conditional write| T B -.->|poll GET /plans/id| API

The app is four CDK stacks: `OpexIntelligence-Cert` (us-east-1, for CloudFront), `-Api`, `-Web`, and the legacy public e