@bluefly/openstandardagents 0.4.9 → 0.5.1

package/examples/gitlab-agents/gitlab-ci-agent.ossa.yaml

@@ -0,0 +1,221 @@
+apiVersion: ossa/v0.5
+kind: Agent
+metadata:
+  name: gitlab-ci-agent
+  version: 1.0.0
+  description: Pipeline fixer agent. Detects broken CI/CD pipelines, inspects job logs, diagnoses failures, and applies fixes. Uses BuildKit CLI and GitLab API.
+  labels:
+    use-case: ci-cd-automation
+    production-ready: 'false'
+    ossa-native: 'true'
+  agentType: custom
+  agentKind: worker
+  identity:
+    namespace: blueflyio/ossa
+    agent_id: gitlab-ci-agent
+    version: 1.0.0
+    publisher:
+      name: BlueFly.io
+      email: agents@bluefly.io
+      website: https://openstandardagents.org
+    created_at: 2026-03-10T12:00:00Z
+    updated_at: 2026-03-10T12:00:00Z
+  catalog:
+    published: true
+    visibility: public
+    categories:
+      - devops
+      - ci-cd
+      - gitlab
+    tags:
+      - gitlab
+      - ci
+      - pipeline
+      - buildkit
+      - ossa-native
+spec:
+  role: |
+    You are an autonomous GitLab CI/CD pipeline fixer agent.
+
+    Your mission:
+    1. Monitor pipelines across GitLab projects
+    2. Detect failed jobs and inspect their logs
+    3. Diagnose root causes (dependency issues, test failures, config errors)
+    4. Apply fixes (update CI config, fix tests, update dependencies)
+    5. Push fixes and verify the pipeline turns green
+
+    Guidelines:
+    - Never force-push to shared branches
+    - Always create fix branches, never commit directly to main/release
+    - Explain your diagnosis clearly in commit messages
+    - Escalate to humans for infrastructure-level issues
+  llm:
+    provider: anthropic
+    model: claude-sonnet-4-20250514
+    temperature: 0.1
+    max_tokens: 8192
+  tools:
+    - type: command
+      name: pipeline_list
+      description: List recent pipelines for a project
+      operation: read
+      command: buildkit gitlab pipelines list
+      parameters:
+        project:
+          type: string
+          description: GitLab project path (e.g. blueflyio/agent-platform/tools/agent-buildkit)
+        ref:
+          type: string
+          description: Branch to check (e.g. release/v0.1.x)
+    - type: command
+      name: pipeline_jobs
+      description: List jobs in a pipeline with status
+      operation: read
+      command: buildkit gitlab pipelines jobs
+      parameters:
+        pipeline_id:
+          type: number
+          description: Pipeline ID to inspect
+    - type: command
+      name: job_log
+      description: Fetch the log output of a failed job
+      operation: read
+      command: buildkit gitlab pipelines job-log
+      parameters:
+        job_id:
+          type: number
+          description: Job ID to get log for
+    - type: command
+      name: deploy_service
+      description: Deploy a service to Oracle via BuildKit
+      operation: write
+      command: buildkit deploy oracle
+      parameters:
+        service:
+          type: string
+          description: Service name to deploy (e.g. mcp, mesh, router)
+    - type: api
+      name: gitlab_api
+      description: Direct GitLab API calls for MR management
+      operation: write
+      parameters:
+        method:
+          type: string
+          enum:
+            - GET
+            - POST
+            - PUT
+        endpoint:
+          type: string
+          description: GitLab API endpoint path
+  capabilities:
+    - name: pipeline-monitoring
+      description: Monitor CI/CD pipeline status across projects
+    - name: failure-diagnosis
+      description: Analyze job logs to identify root causes
+    - name: automated-fix
+      description: Apply fixes for common CI failures
+    - name: deployment
+      description: Deploy services via BuildKit
+  safety:
+    guardrails:
+      - no_force_push
+      - no_direct_main_commits
+      - human_escalation_for_infra
+      - audit_all_actions
+    pii_handling: none
+    audit_all_actions: true
+    max_cost_per_execution: 0.3
+security:
+  tier: tier_2_write_limited
+  threat_model:
+    - category: privilege-escalation
+      severity: high
+      mitigations:
+        - scoped-tokens
+        - least-privilege
+      description: CI tokens must be scoped to minimum required permissions
+  capabilities:
+    required:
+      - network-outbound
+      - process-spawn
+      - tool-execution
+    optional:
+      - filesystem-read
+      - filesystem-write
+  sandboxing:
+    required: true
+    type: container
+    resource_limits:
+      max_memory_mb: 1024
+      max_cpu_cores: 1
+      max_execution_seconds: 300
+  network_access:
+    allowed_domains:
+      - gitlab.com
+      - '*.gitlab.com'
+      - api.anthropic.com
+    protocols:
+      - https
+    egress_policy: allow-list
+  data_classification: internal
+protocols:
+  mcp:
+    version: 1.0.0
+    role: client
+    capabilities:
+      tools: true
+      resources: false
+      prompts: false
+      sampling: false
+    servers:
+      - name: buildkit
+        transport: stdio
+        command: buildkit
+        tools:
+          - pipeline_list
+          - pipeline_jobs
+          - job_log
+          - deploy_service
+          - gitlab_api
+  a2a:
+    version: 0.2.0
+    endpoint: https://openstandardagents.org/agents/gitlab-ci-agent
+    agent_card:
+      name: GitLab CI Agent
+      description: Diagnose and repair GitLab CI/CD pipelines
+      skills:
+        - id: fix-pipeline
+          name: Fix Pipeline
+          description: Diagnose and fix a broken CI pipeline
+    capabilities:
+      streaming: true
+      pushNotifications: false
+      stateTransitionHistory: true
+    authentication:
+      schemes:
+        - bearer
+governance:
+  authorization:
+    clearance_level: 2
+    policy_references:
+      - blueflyio/cedar-policies
+    tool_permissions:
+      - tool: pipeline_list
+        risk_level: low
+      - tool: pipeline_jobs
+        risk_level: low
+      - tool: job_log
+        risk_level: low
+      - tool: deploy_service
+        risk_level: high
+        requires_approval: true
+      - tool: gitlab_api
+        risk_level: high
+        requires_approval: true
+  quality_requirements:
+    confidence_threshold: 0.85
+    security_score_threshold: 80
+  compliance:
+    data_classification: internal
+    audit_logging_required: true

package/examples/hierarchical-agent.ossa.yaml

@@ -1,31 +1,11 @@
-# OSSA v0.4.5 Example: Hierarchical Agent — Code Review Pipeline with Subagents
-#
-# Demonstrates the parent-child subagent pattern for a code review pipeline.
-# A coordinator agent spawns isolated subagents to perform specific review
-# tasks (exploration, security scanning, test validation). Subagents report
-# results only to the parent — there is no peer communication.
-#
-# Key characteristics:
-#   - Coordinator with subagents (not team members)
-#   - Parent-child delegation, no peer communication
-#   - Each subagent has a token budget to control costs
-#   - Context isolation enforced for all subagents
-#   - Results flow up: subagent -> parent -> user
-
-apiVersion: ossa/v0.4.7
+apiVersion: ossa/v0.5
 kind: Agent
 metadata:
   name: code-review-pipeline
-  version: "1.0.0"
-  description: >-
-    A code review coordinator that spawns specialized subagents to analyze
-    code changes. A researcher explores the codebase for context, a debugger
-    scans for security vulnerabilities, and a generic subagent validates test
-    coverage. The coordinator synthesizes all findings into a review report.
-
+  version: 1.0.0
+  description: A code review coordinator that spawns specialized subagents to analyze code changes. A researcher explores the codebase for context, a debugger scans for security vulnerabilities, and a generic subagent validates test coverage. The coordinator synthesizes all findings into a review report.
   agentKind: coordinator
-  agentType: a2a
-
+  agentType: custom
   agentArchitecture:
     pattern: hierarchical
     capabilities:
@@ -39,36 +19,24 @@ metadata:
       teamModel: parent-child
       communicationPattern: direct
       taskCoordination: assigned
-
   labels:
     domain: development
     subdomain: code-review
     pattern: hierarchical
-
 spec:
-  role: >-
-    You are a code review coordinator. When given a merge request or set of
-    file changes, you:
-    1. Spawn the code-explorer subagent to gather codebase context.
-    2. Spawn the security-scanner subagent to identify vulnerabilities.
-    3. Spawn the test-validator subagent to check test coverage.
-    4. Collect all subagent reports and synthesize a comprehensive review
+  role: |-
+    You are a code review coordinator. When given a merge request or set of file changes, you: 1. Spawn the code-explorer subagent to gather codebase context. 2. Spawn the security-scanner subagent to identify vulnerabilities. 3. Spawn the test-validator subagent to check test coverage. 4. Collect all subagent reports and synthesize a comprehensive review
        with actionable feedback, severity ratings, and suggested fixes.
-
   llm:
     provider: anthropic
     model: claude-sonnet-4-5-20250929
     temperature: 0.2
     maxTokens: 4096
     profile: deep
-
   subagents:
     - name: code-explorer
       kind: researcher
-      role: >-
-        Fast codebase search and structural analysis. Find relevant files,
-        trace dependencies, identify architecture patterns, and summarize
-        the context around changed files. Read-only — never modify anything.
+      role: Fast codebase search and structural analysis. Find relevant files, trace dependencies, identify architecture patterns, and summarize the context around changed files. Read-only — never modify anything.
       model:
         provider: anthropic
         name: claude-haiku-4-5-20250514
@@ -79,14 +47,9 @@ spec:
       contextIsolation: true
       reportTo: parent
       maxTokenBudget: 50000
-
     - name: security-scanner
       kind: debugger
-      role: >-
-        Identify security vulnerabilities, code smells, and potential attack
-        vectors in the changed files. Check for injection risks, auth bypass,
-        secrets in code, unsafe deserialization, and OWASP Top 10 issues.
-        Generate a severity-rated findings list.
+      role: Identify security vulnerabilities, code smells, and potential attack vectors in the changed files. Check for injection risks, auth bypass, secrets in code, unsafe deserialization, and OWASP Top 10 issues. Generate a severity-rated findings list.
       model:
         provider: anthropic
         name: claude-sonnet-4-5-20250929
@@ -97,14 +60,9 @@ spec:
       contextIsolation: true
       reportTo: parent
       maxTokenBudget: 80000
-
     - name: test-validator
       kind: subagent
-      role: >-
-        Run the test suite and validate coverage for changed files. Check
-        that new code has corresponding tests, coverage thresholds are met,
-        and no existing tests are broken. Report coverage percentages and
-        any failures.
+      role: Run the test suite and validate coverage for changed files. Check that new code has corresponding tests, coverage thresholds are met, and no existing tests are broken. Report coverage percentages and any failures.
       model:
         provider: anthropic
         name: claude-sonnet-4-5-20250929
@@ -115,11 +73,10 @@ spec:
       contextIsolation: true
       reportTo: parent
       maxTokenBudget: 60000
-
   constraints:
     cost:
       maxTokensPerRequest: 200000
-      maxCostPerDay: 50.00
+      maxCostPerDay: 50
       currency: USD
     performance:
       timeoutSeconds: 120

package/examples/kagent/ossa-kagent-anthropic.ossa.yaml

@@ -1,8 +1,4 @@
-# OSSA kagent export: Anthropic provider with RemoteMCPServer
-# Run: ossa export examples/kagent/ossa-kagent-anthropic.ossa.yaml --platform kagent -o ./anthropic-out
-# Deploy: kubectl apply -f anthropic-out/
-# Or: ossa export examples/kagent/ossa-kagent-anthropic.ossa.yaml --platform kagent --apply
-apiVersion: ossa/v0.4
+apiVersion: ossa/v0.5
 kind: Agent
 metadata:
   name: ossa-kagent-anthropic
@@ -36,24 +32,5 @@ extensions:
       resourceLimits:
         cpu: 500m
         memory: 512Mi
-    mcpServers:
-      gitlab-mcp:
-        url: https://your-mcp-server.example.com/api/mcp/sse
-        transport: sse
-        headers:
-          - name: Authorization
-            valueFrom:
-              type: Secret
-              name: gitlab-mcp-token
-              key: token
-      code-analysis:
-        url: http://code-analysis.kagent.svc.cluster.local/sse
-        transport: sse
     a2aConfig:
-      skills:
-        - id: code-review
-          name: Code Review
-          description: Review merge requests for bugs, security issues, and best practices
-          inputModes: [text]
-          outputModes: [text]
-          tags: [code-review, security, gitlab]
+      enabled: true

package/examples/kagent/ossa-kagent-mcp-tools.ossa.yaml

@@ -1,8 +1,4 @@
-# OSSA v1alpha2 export example: Agent with RemoteMCPServer tools and Anthropic provider
-# Run: ossa export examples/kagent/ossa-kagent-mcp-tools.ossa.yaml --platform kagent -o ./mcp-tools-out
-# Deploy: ossa export examples/kagent/ossa-kagent-mcp-tools.ossa.yaml --platform kagent --apply
-# Result: ModelConfig + 2x RemoteMCPServer + Agent applied in APPLY_ORDER
-apiVersion: ossa/v0.4
+apiVersion: ossa/v0.5
 kind: Agent
 metadata:
   name: fleet-ops-agent
@@ -40,29 +36,5 @@ extensions:
       resourceLimits:
         cpu: 1000m
         memory: 1Gi
-    mcpServers:
-      kagent-tool-server:
-        url: http://kagent-tool-server.kagent.svc.cluster.local/sse
-        transport: sse
-      # GitLab tools live in agent-protocol (no separate gitlab-mcp-server)
-      agent-protocol-gitlab:
-        url: http://agent-protocol.agent-platform.svc.cluster.local:4005/api/mcp/sse
-        transport: sse
-        headers:
-          - name: Authorization
-            valueFrom:
-              type: Secret
-              name: gitlab-token
-              key: token
     a2aConfig:
-      skills:
-        - id: fleet-management
-          name: Fleet Management
-          description: Manage Kubernetes resources and GitLab repositories across the fleet
-          inputModes: [text]
-          outputModes: [text]
-          tags: [k8s, gitlab, fleet, ossa]
-          examples:
-            - "List all deployments in the kagent namespace"
-            - "Show recent merge requests for agent-buildkit"
-            - "Get logs from the failing pod"
+      enabled: true

package/examples/kagent/ossa-kagent-multi-tool.ossa.yaml

@@ -1,7 +1,4 @@
-# OSSA kagent export: Multi-tool agent with multiple RemoteMCPServers
-# Run: ossa export examples/kagent/ossa-kagent-multi-tool.ossa.yaml --platform kagent -o ./multi-out
-# Deploy: kubectl apply -f multi-out/ (files are in APPLY_ORDER)
-apiVersion: ossa/v0.4
+apiVersion: ossa/v0.5
 kind: Agent
 metadata:
   name: ossa-kagent-devops
@@ -40,18 +37,5 @@ extensions:
   kagent:
     kubernetes:
       namespace: kagent
-    mcpServers:
-      gitlab-mcp:
-        url: https://your-mcp-server.example.com/api/mcp/sse
-        transport: sse
-      grafana-mcp:
-        url: http://grafana-mcp.kagent.svc.cluster.local/sse
-        transport: sse
     a2aConfig:
-      skills:
-        - id: devops-automation
-          name: DevOps Automation
-          description: CI/CD management, deployment monitoring, and incident response
-          inputModes: [text]
-          outputModes: [text]
-          tags: [devops, cicd, k8s, monitoring]
+      enabled: true

package/examples/kagent/ossa-kagent-poc.ossa.yaml

@@ -1,8 +1,4 @@
-# OSSA-first POC: one manifest, export to kagent.dev (v1alpha2 Declarative)
-# Run: ossa export examples/kagent/ossa-kagent-poc.ossa.yaml --platform kagent --crd-version v1alpha2 -o ./poc-out
-# Deploy: kubectl apply -f poc-out/model-config.yaml; kubectl apply -f poc-out/agent.yaml
-# Invoke: kagent invoke --agent ossa-kagent-poc --task "List pods in kagent namespace"
-apiVersion: ossa/v0.4
+apiVersion: ossa/v0.5
 kind: Agent
 metadata:
   name: ossa-kagent-poc
@@ -33,14 +29,4 @@ extensions:
         cpu: 500m
         memory: 512Mi
     a2aConfig:
-      skills:
-        - id: cluster-inspection
-          name: Cluster Inspection
-          description: List and inspect Kubernetes resources (pods, deployments, services)
-          inputModes: [text]
-          outputModes: [text]
-          tags: [k8s, ossa, poc]
-          examples:
-            - "List all pods in the kagent namespace"
-            - "What API resources are available in the cluster?"
-            - "Describe the kagent-controller deployment"
+      enabled: true

package/examples/pipeline-agent.ossa.yaml

@@ -1,4 +1,4 @@
-# OSSA v0.4.5 Example: Pipeline Agent — Data Processing Pipeline
+# OSSA v0.5.0 Example: Pipeline Agent — Data Processing Pipeline
 #
 # Demonstrates the pipeline pattern for sequential data processing. A
 # coordinator manages four team members arranged as sequential stages:
@@ -13,7 +13,7 @@
 #   - Assigned task coordination (coordinator assigns stage work)
 #   - Database-backed persistence for auditability
 
-apiVersion: ossa/v0.4.7
+apiVersion: ossa/v0.5.0
 kind: Agent
 metadata:
   name: data-processing-pipeline
@@ -26,7 +26,7 @@ metadata:
     tools and model.
 
   agentKind: coordinator
-  agentType: workflow
+  agentType: claude
 
   agentArchitecture:
     pattern: pipeline

package/examples/platform-specific/claude-code-subagent.yaml

@@ -4,7 +4,7 @@ metadata:
   name: claude-code-explorer
   version: 1.0.0
   description: Specialized sub-agent for deep code exploration and codebase analysis
-  author: Bluefly Platform
+  author: Agent Platform
   tags:
     - claude-code
     - subagent

package/examples/platform-specific/cursor-coding-agent.yaml

@@ -4,7 +4,7 @@ metadata:
   name: cursor-coding-assistant
   version: 1.0.0
   description: AI coding assistant for Cursor IDE with advanced code generation and refactoring
-  author: Bluefly Platform
+  author: Agent Platform
   tags:
     - cursor
     - coding-assistant

package/examples/platform-specific/warp-terminal-agent.yaml

@@ -4,7 +4,7 @@ metadata:
   name: warp-dev-agent
   version: 1.0.0
   description: Development workflow agent for Warp Terminal
-  author: Bluefly Platform
+  author: Agent Platform
   tags:
     - warp
     - terminal

package/examples/production-ready/01-customer-support-bot/agent.ossa.yaml

@@ -1,4 +1,4 @@
-apiVersion: ossa/v0.4.7
+apiVersion: ossa/v0.5
 kind: Agent
 metadata:
   name: customer-support-bot
@@ -26,19 +26,16 @@ spec:
     - Clear and concise explanations
     - Proactive in offering solutions
     - Transparent about limitations
-
   llm:
     provider: openai
     model: gpt-4o
     temperature: 0.7
     maxTokens: 1500
-
   capabilities:
     - search_documentation
     - create_ticket
     - send_email
     - conversation_memory
-
   tools:
     - type: function
       name: search_docs
@@ -55,7 +52,6 @@ spec:
             default: 5
         required:
           - query
-
     - type: function
       name: create_ticket
       description: Create a support ticket for issues requiring human attention
@@ -70,7 +66,11 @@ spec:
             description: Detailed description of the issue
           priority:
             type: string
-            enum: [low, medium, high, urgent]
+            enum:
+              - low
+              - medium
+              - high
+              - urgent
             description: Priority level of the ticket
           category:
             type: string
@@ -79,7 +79,6 @@ spec:
           - title
           - description
           - priority
-
     - type: function
       name: send_email
       description: Send follow-up email to customer
@@ -98,12 +97,14 @@ spec:
           template:
             type: string
             description: Email template to use
-            enum: [follow_up, resolution, escalation]
+            enum:
+              - follow_up
+              - resolution
+              - escalation
         required:
           - to
           - subject
           - body
-
   autonomy:
     level: supervised
     approval_required: false
@@ -112,7 +113,6 @@ spec:
         action: notify_human
       - condition: ticket_count > 3
         action: escalate
-
   memory:
     enabled: true
     type: conversation_buffer
@@ -121,7 +121,6 @@ spec:
       enabled: true
       backend: redis
       ttl: 86400
-
   safety:
     input_filters:
       - type: pii_detection
@@ -132,8 +131,9 @@ spec:
       - type: hallucination_check
         threshold: 0.8
       - type: tone_analysis
-        required_sentiment: [positive, neutral]
-
+        required_sentiment:
+          - positive
+          - neutral
   observability:
     logging:
       level: info
@@ -150,23 +150,16 @@ spec:
     tracing:
       enabled: true
       provider: opentelemetry
-
 extensions:
   langchain:
-    agent_type: react
-    memory_type: conversation_buffer
-    chain_type: conversation
-    tools_mapping:
-      - ossa_capability: search_documentation
-        langchain_tool: search_docs
-        tool_class: CustomSearchTool
-      - ossa_capability: create_ticket
-        langchain_tool: create_ticket
-        tool_class: TicketingTool
-      - ossa_capability: send_email
-        langchain_tool: send_email
-        tool_class: EmailTool
-    export_config:
-      format: python
-      include_dependencies: true
-      output_file: customer_support_agent.py
+    enabled: true
+    chain_type: agent
+    memory:
+      type: buffer
+    tools:
+      - name: search_docs
+        description: Search the knowledge base for relevant documentation
+      - name: create_ticket
+        description: Create a support ticket for issues requiring human attention
+      - name: send_email
+        description: Send follow-up email to customer