@bluefly/openstandardagents 0.4.8 → 0.5.0

package/examples/roles/security-auditor.role.yaml

@@ -0,0 +1,27 @@
+apiVersion: ossa/v0.5
+kind: Role
+metadata:
+  name: security-auditor
+  version: 1.0.0
+  description: Security audit and compliance review role
+  labels:
+    platform: claude-code
+    domain: security
+spec:
+  role: |
+    You are a security auditor focused on OWASP, CVE analysis, and compliance.
+  instructions:
+    preamble: |
+      ## Security Rules
+      - Check all inputs for injection vulnerabilities
+      - Verify authentication on every endpoint
+      - Review secrets management
+    constraints:
+      - Never approve code with hardcoded credentials
+      - Never skip security tests
+  tools:
+    allowed: [Read, Grep, Glob, Bash]
+    denied: [Write, Edit]
+    skills: [security-scan, ossa-validate]
+  activation:
+    file_patterns: ["**/security/**", "**/*.policy"]

package/examples/swarm-agent.ossa.yaml

@@ -1,30 +1,11 @@
-# OSSA v0.4.5 Example: Swarm Agent — OpenAI-Style Support Swarm
-#
-# Demonstrates the swarm pattern with hub-spoke coordination. A triage
-# coordinator routes conversations to specialist agents via automatic
-# handoffs. Each member handles a specific domain and can hand back to
-# triage when the query falls outside its scope.
-#
-# Key characteristics:
-#   - Hub-spoke model: triage agent is the central hub
-#   - Direct communication: agents hand off control directly
-#   - Assigned task coordination: triage decides who handles what
-#   - In-memory persistence: no durable task list needed
-
-apiVersion: ossa/v0.4.7
+apiVersion: ossa/v0.5
 kind: Agent
 metadata:
   name: support-swarm
-  version: "1.0.0"
-  description: >-
-    An OpenAI Swarm-style customer support system. A triage coordinator
-    routes incoming queries to specialist agents (orders, returns, billing)
-    via automatic handoffs. Each specialist can hand back to triage when
-    it encounters an out-of-scope request.
-
+  version: 1.0.0
+  description: An OpenAI Swarm-style customer support system. A triage coordinator routes incoming queries to specialist agents (orders, returns, billing) via automatic handoffs. Each specialist can hand back to triage when it encounters an out-of-scope request.
   agentKind: coordinator
-  agentType: a2a
-
+  agentType: swarm
   agentArchitecture:
     pattern: swarm
     capabilities:
@@ -40,36 +21,25 @@ metadata:
       taskCoordination: assigned
       conflictResolution: leader-decides
       taskPersistence: in-memory
-
   labels:
     domain: customer-support
     pattern: swarm
     framework: openai-swarm
-
 spec:
-  role: >-
-    You are the triage coordinator for a customer support swarm. Analyze
-    incoming customer messages and route them to the appropriate specialist
-    agent. If a specialist hands back to you, re-evaluate and route to a
-    different specialist or handle the query directly.
-
+  role: You are the triage coordinator for a customer support swarm. Analyze incoming customer messages and route them to the appropriate specialist agent. If a specialist hands back to you, re-evaluate and route to a different specialist or handle the query directly.
   llm:
     provider: openai
     model: gpt-4o
     temperature: 0.2
     maxTokens: 1024
-
   team:
     model: hub-spoke
     lead: triage-agent
     delegateMode: false
-
     members:
       - name: order-agent
         kind: teammate
-        role: >-
-          Handle order-related queries: order status, shipment tracking,
-          order modifications, and cancellations.
+        role: 'Handle order-related queries: order status, shipment tracking, order modifications, and cancellations.'
         model:
           provider: openai
           name: gpt-4o-mini
@@ -80,15 +50,12 @@ spec:
         contextIsolation: true
         handoffs:
           - to: triage-agent
-            condition: "Query is not order-related"
+            condition: Query is not order-related
           - to: returns-agent
-            condition: "Customer wants to return an ordered item"
-
+            condition: Customer wants to return an ordered item
       - name: returns-agent
         kind: teammate
-        role: >-
-          Process returns and exchanges. Validate return eligibility, generate
-          return labels, and track return shipments.
+        role: Process returns and exchanges. Validate return eligibility, generate return labels, and track return shipments.
         model:
           provider: openai
           name: gpt-4o-mini
@@ -99,15 +66,12 @@ spec:
         contextIsolation: true
         handoffs:
           - to: triage-agent
-            condition: "Query is not returns-related"
+            condition: Query is not returns-related
           - to: billing-agent
-            condition: "Customer asks about refund timing or amount"
-
+            condition: Customer asks about refund timing or amount
       - name: billing-agent
         kind: teammate
-        role: >-
-          Handle billing and payment queries. Look up invoices, process
-          refunds, and answer payment-related questions.
+        role: Handle billing and payment queries. Look up invoices, process refunds, and answer payment-related questions.
         model:
           provider: openai
           name: gpt-4o-mini
@@ -118,8 +82,7 @@ spec:
         contextIsolation: true
         handoffs:
           - to: triage-agent
-            condition: "Query is not billing-related"
-
+            condition: Query is not billing-related
     taskList:
       coordination: assigned
       persistence: in-memory
@@ -130,7 +93,6 @@ spec:
       dependencyTracking: false
       waveExecution: false
       lockingStrategy: none
-
     communication:
       pattern: direct
       broadcastEnabled: false

package/examples/team-agent.ossa.yaml

@@ -1,34 +1,11 @@
-# OSSA v0.4.5 Example: Team Agent — Claude Code Lead-Teammate Team
-#
-# Demonstrates the lead-teammate pattern modeled after Claude Code Agent
-# Teams. An Opus lead orchestrates Sonnet workers and a Haiku explorer.
-# The lead operates in delegate mode (never implements directly), while
-# teammates self-claim tasks from a shared, file-backed task list with
-# dependency tracking and wave execution.
-#
-# Key characteristics:
-#   - Lead-teammate model with delegate mode
-#   - Shared task list with self-claim coordination
-#   - File-backed persistence with dependency tracking
-#   - Mailbox communication (async, inbox-based)
-#   - Mixed model tiers (Opus lead, Sonnet workers, Haiku explorer)
-#   - In-process deployment with fixed scaling
-
-apiVersion: ossa/v0.4.7
+apiVersion: ossa/v0.5
 kind: Agent
 metadata:
   name: fullstack-dev-team
-  version: "1.0.0"
-  description: >-
-    A Claude Code-style development team for fullstack feature implementation.
-    An Opus lead decomposes tasks and coordinates three teammates: a backend
-    worker (Sonnet), a frontend worker (Sonnet), and a codebase explorer
-    (Haiku). Teammates self-claim tasks from a shared list, communicate via
-    mailbox, and work in isolated directories.
-
-  agentKind: team-lead
-  agentType: a2a
-
+  version: 1.0.0
+  description: 'A Claude Code-style development team for fullstack feature implementation. An Opus lead decomposes tasks and coordinates three teammates: a backend worker (Sonnet), a frontend worker (Sonnet), and a codebase explorer (Haiku). Teammates self-claim tasks from a shared list, communicate via mailbox, and work in isolated directories.'
+  agentKind: supervisor
+  agentType: custom
   agentArchitecture:
     pattern: lead-teammate
     capabilities:
@@ -47,43 +24,29 @@ metadata:
       conflictResolution: leader-decides
       taskPersistence: file-backed
       dependencyTracking: true
-
   labels:
     domain: development
     pattern: lead-teammate
     framework: claude-code
-
 spec:
-  role: >-
-    You are the lead of a fullstack development team. Your job is to:
-    1. Analyze the user's feature request and decompose it into tasks.
-    2. Create tasks in the shared task list with clear descriptions and
+  role: |-
+    You are the lead of a fullstack development team. Your job is to: 1. Analyze the user's feature request and decompose it into tasks. 2. Create tasks in the shared task list with clear descriptions and
        dependency relationships.
-    3. Monitor teammate progress and resolve blockers.
-    4. Synthesize completed work into a final deliverable.
-    You operate in delegate mode — you NEVER write code directly. Instead,
-    you coordinate your teammates who do the implementation work.
-
+    3. Monitor teammate progress and resolve blockers. 4. Synthesize completed work into a final deliverable. You operate in delegate mode — you NEVER write code directly. Instead, you coordinate your teammates who do the implementation work.
   llm:
     provider: anthropic
     model: claude-opus-4-20250514
     temperature: 0.4
     maxTokens: 8192
     profile: deep
-
   team:
     model: lead-teammate
     lead: lead
     delegateMode: true
-
     members:
       - name: backend-worker
         kind: teammate
-        role: >-
-          Implement backend features: API endpoints, database schemas,
-          business logic, and server-side tests. Work in the backend/
-          directory. Claim tasks from the shared list and mark them
-          complete when done.
+        role: 'Implement backend features: API endpoints, database schemas, business logic, and server-side tests. Work in the backend/ directory. Claim tasks from the shared list and mark them complete when done.'
         model:
           provider: anthropic
           name: claude-sonnet-4-20250514
@@ -95,13 +58,9 @@ spec:
           - glob
         contextIsolation: true
         workingDirectory: /backend
-
       - name: frontend-worker
         kind: teammate
-        role: >-
-          Implement frontend features: React components, API integration,
-          styling, and UI tests. Work in the frontend/ directory. Claim
-          tasks from the shared list and mark them complete when done.
+        role: 'Implement frontend features: React components, API integration, styling, and UI tests. Work in the frontend/ directory. Claim tasks from the shared list and mark them complete when done.'
         model:
           provider: anthropic
           name: claude-sonnet-4-20250514
@@ -113,13 +72,9 @@ spec:
           - glob
         contextIsolation: true
         workingDirectory: /frontend
-
       - name: codebase-explorer
         kind: researcher
-        role: >-
-          Explore the codebase to answer questions from the lead and other
-          teammates. Search for patterns, find dependencies, and analyze
-          architecture. Read-only — never modify files.
+        role: Explore the codebase to answer questions from the lead and other teammates. Search for patterns, find dependencies, and analyze architecture. Read-only — never modify files.
         model:
           provider: anthropic
           name: claude-haiku-4-5-20250514
@@ -129,7 +84,6 @@ spec:
           - glob
         contextIsolation: true
         workingDirectory: /
-
     taskList:
       coordination: self-claim
       persistence: file-backed
@@ -141,19 +95,16 @@ spec:
       dependencyTracking: true
       waveExecution: true
       lockingStrategy: file-lock
-
     communication:
       pattern: mailbox
       broadcastEnabled: false
-
     deployment:
       backend: in-process
       scaling: fixed
-
   constraints:
     cost:
       maxTokensPerDay: 2000000
-      maxCostPerDay: 100.00
+      maxCostPerDay: 100
       currency: USD
     performance:
       timeoutSeconds: 300

package/examples/team-lead-teammate.ossa.yaml

@@ -1,11 +1,11 @@
-apiVersion: ossa/v0.4
+apiVersion: ossa/v0.5
 kind: Agent
 metadata:
   name: code-review-team
   version: 1.0.0
   description: Claude Code teams pattern - lead delegates to specialized reviewers
   agentType: claude
-  agentKind: team-lead
+  agentKind: supervisor
   agentArchitecture:
     pattern: lead-teammate
     capabilities:
@@ -21,9 +21,8 @@ metadata:
       taskPersistence: file-backed
       dependencyTracking: true
 spec:
-  role: >
-    You lead a code review team. Analyze pull requests and delegate
-    specific review tasks to specialized teammates.
+  role: |
+    You lead a code review team. Analyze pull requests and delegate specific review tasks to specialized teammates.
   llm:
     provider: anthropic
     model: claude-sonnet-4-5-20250514
@@ -34,9 +33,8 @@ spec:
     members:
       - name: lead-reviewer
         kind: team-lead
-        role: >
-          Senior code reviewer. Analyze PRs, break down review into tasks,
-          delegate to specialists, and synthesize final review.
+        role: |
+          Senior code reviewer. Analyze PRs, break down review into tasks, delegate to specialists, and synthesize final review.
         model: claude-sonnet-4-5-20250514
         tools:
           - read-file
@@ -44,9 +42,8 @@ spec:
           - git-diff
       - name: security-reviewer
         kind: specialist
-        role: >
-          Security vulnerability scanner. Check for OWASP top 10,
-          injection attacks, authentication flaws, and data exposure.
+        role: |
+          Security vulnerability scanner. Check for OWASP top 10, injection attacks, authentication flaws, and data exposure.
         tools:
           - sast-scan
           - dependency-check
@@ -54,18 +51,16 @@ spec:
         maxTokenBudget: 15000
       - name: style-checker
         kind: teammate
-        role: >
-          Code style and formatting reviewer. Verify adherence to
-          project conventions, naming, and documentation standards.
+        role: |
+          Code style and formatting reviewer. Verify adherence to project conventions, naming, and documentation standards.
         tools:
           - eslint
           - prettier
           - read-file
       - name: test-reviewer
         kind: teammate
-        role: >
-          Test coverage reviewer. Verify test adequacy, check edge cases,
-          and validate test assertions.
+        role: |
+          Test coverage reviewer. Verify test adequacy, check edge cases, and validate test assertions.
         tools:
           - run-tests
           - coverage-report