@bluefly/openstandardagents 0.5.0 → 0.5.3

package/examples/showcase/full-power-agent.ossa.yaml

@@ -1,350 +0,0 @@
-# ─────────────────────────────────────────────────────────────────────────────
-# OSSA Showcase: Full-Power Agent Card
-# ─────────────────────────────────────────────────────────────────────────────
-# This manifest demonstrates EVERY feature OSSA supports.
-# Run: ossa agent-card generate examples/showcase/full-power-agent.ossa.yaml --stdout
-#
-# "Every Agent Needs a Contract" — this IS that contract.
-# One manifest. One standard. Every platform.
-# MCP connects tools. A2A connects agents. OSSA defines the contract.
-# ─────────────────────────────────────────────────────────────────────────────
-
-apiVersion: ossa/v0.4.7
-kind: Agent
-metadata:
-  name: enterprise-support-orchestrator
-  version: 2.1.0
-  description: >
-    Enterprise-grade multi-agent orchestrator with full MCP tool integration,
-    A2A agent-to-agent communication, autonomous escalation, cost governance,
-    and production observability. The definitive OSSA showcase.
-
-  # ── Agent Taxonomy ──
-  agentType: claude                       # Runtime: claude, kagent, openai, langchain, crewai
-  agentKind: orchestrator                 # Role: orchestrator, worker, reviewer, analyzer
-
-  agentArchitecture:
-    pattern: swarm                        # Pattern: swarm, pipeline, tree, graph
-    capabilities:
-      - handoff                           # Can transfer to other agents
-      - streaming                         # Supports streaming responses
-      - context                           # Maintains conversation context
-      - tools                             # Can call external tools
-      - vision                            # Can process images/screenshots
-      - code-execution                    # Can execute code safely
-    coordination:
-      handoffStrategy: automatic          # automatic, manual, hybrid
-      maxDepth: 5                         # Max orchestration depth
-    runtime:
-      scalability: horizontal             # horizontal, vertical, none
-      executionModel: streaming           # streaming, batch, request-response
-      preferredRegion: us-east-1
-
-  labels:
-    domain: enterprise-support
-    team: platform-engineering
-    environment: production
-    capability: support,escalation,routing,analysis
-    framework: a2a
-    tier: tier-3
-    compliance: soc2,gdpr
-
-  annotations:
-    documentation: https://docs.example.com/agents/enterprise-support
-    runbook: https://runbooks.example.com/enterprise-support
-    support: platform-eng@example.com
-    sla: "99.9%"
-
-spec:
-  # ── LLM Configuration ──
-  model:
-    provider: anthropic
-    name: claude-sonnet-4-5-20250929
-    temperature: 0.7
-    max_tokens: 8192
-
-  # ── System Prompt ──
-  system: |
-    You are an enterprise support orchestrator managing a team of specialist agents.
-    Route requests to the right specialist, maintain context across handoffs,
-    and ensure every customer interaction meets SLA requirements.
-
-    Specialist Team:
-    - @technical-support: Deep technical troubleshooting
-    - @billing-support: Billing, invoicing, subscription management
-    - @security-ops: Security incidents and access reviews
-    - @product-specialist: Feature requests and product guidance
-
-  # ── Tools ──
-  tools:
-    - name: route_to_specialist
-      description: Route customer request to appropriate specialist agent
-      input_schema:
-        type: object
-        required: [agentId, reason, priority]
-        properties:
-          agentId:
-            type: string
-            description: Target specialist agent ID
-          reason:
-            type: string
-            description: Why this specialist is appropriate
-          priority:
-            type: string
-            enum: [low, medium, high, critical]
-          context:
-            type: object
-            description: Conversation context to pass along
-
-    - name: search_knowledge_base
-      description: Search enterprise knowledge base for relevant articles
-      input_schema:
-        type: object
-        required: [query]
-        properties:
-          query:
-            type: string
-          category:
-            type: string
-            enum: [technical, billing, security, product, general]
-          limit:
-            type: integer
-            default: 5
-
-    - name: create_ticket
-      description: Create a support ticket in the ticketing system
-      input_schema:
-        type: object
-        required: [title, description, priority]
-        properties:
-          title:
-            type: string
-          description:
-            type: string
-          priority:
-            type: string
-            enum: [low, medium, high, critical]
-          assignee:
-            type: string
-
-    - name: check_sla_status
-      description: Check SLA compliance for current interaction
-      input_schema:
-        type: object
-        required: [ticketId]
-        properties:
-          ticketId:
-            type: string
-          includeHistory:
-            type: boolean
-            default: false
-
-  # ── Handoffs ──
-  handoffs:
-    - to: technical-support
-      condition: "user reports bugs, errors, or system issues"
-    - to: billing-support
-      condition: "user has billing, payment, or subscription questions"
-    - to: security-ops
-      condition: "user reports security incidents or needs access reviews"
-    - to: product-specialist
-      condition: "user requests features or needs product guidance"
-
-  # ── Autonomy ──
-  autonomy:
-    level: semi-autonomous
-    approval_required: false
-    allowed_actions:
-      - route_to_specialist
-      - search_knowledge_base
-      - create_ticket
-      - check_sla_status
-    blocked_actions:
-      - delete_account
-      - modify_billing
-      - grant_admin_access
-
-  # ── Constraints ──
-  constraints:
-    cost:
-      maxTokensPerDay: 500000
-      maxTokensPerRequest: 16384
-      maxCostPerDay: 50.00
-      currency: USD
-    performance:
-      maxLatencySeconds: 3.0
-      maxConcurrentRequests: 50
-      timeoutSeconds: 60
-    resources:
-      cpu: 500m
-      memory: 1Gi
-
-  # ── Observability ──
-  observability:
-    tracing:
-      enabled: true
-      exporter: otlp
-      endpoint: https://otel.example.com:4318
-      samplingRate: 1.0
-    metrics:
-      enabled: true
-      exporter: prometheus
-      endpoint: https://metrics.example.com/push
-    logging:
-      level: info
-      format: json
-
-  # ── Extensions ──
-  extensions:
-    # ── MCP Tool Servers ──
-    mcp:
-      servers:
-        - name: knowledge-base
-          description: Enterprise knowledge base search via MCP
-          transport:
-            type: stdio
-            command: npx
-            args: ["-y", "@example/mcp-knowledge-base", "--index", "support"]
-          version: "1.2.0"
-          capabilities:
-            resources:
-              subscribe: true
-              listChanged: true
-            tools:
-              listChanged: true
-            logging:
-              enabled: true
-              level: info
-
-        - name: ticketing-system
-          description: Jira/ServiceNow integration via MCP
-          transport:
-            type: sse
-            url: https://mcp.example.com/ticketing
-          version: "2.0.0"
-          capabilities:
-            tools:
-              listChanged: true
-
-      resources:
-        - uri: "kb://support/faq"
-          name: "Support FAQ"
-          description: "Frequently asked questions for customer support"
-          mimeType: "application/json"
-        - uri: "kb://support/runbooks"
-          name: "Runbooks"
-          description: "Operational runbooks for common issues"
-          mimeType: "text/markdown"
-
-    # ── A2A Agent Protocol ──
-    a2a:
-      enabled: true
-
-      protocol:
-        type: json-rpc
-        version: "2.0"
-        messageFormat: json
-        timeout: 60
-
-      endpoints:
-        - agentId: "@technical-support"
-          url: "https://agents.example.com/technical-support/a2a"
-          capabilities: ["debugging", "troubleshooting", "log-analysis"]
-          priority: 10
-
-        - agentId: "@billing-support"
-          url: "https://agents.example.com/billing-support/a2a"
-          capabilities: ["billing", "payments", "subscriptions"]
-          priority: 8
-
-        - agentId: "@security-ops"
-          url: "https://agents.example.com/security-ops/a2a"
-          capabilities: ["incident-response", "access-review", "threat-analysis"]
-          priority: 15
-
-        - agentId: "@product-specialist"
-          url: "https://agents.example.com/product-specialist/a2a"
-          capabilities: ["features", "roadmap", "product-guidance"]
-          priority: 5
-
-      routing:
-        strategy: priority-based
-        routingRules:
-          - name: "security-critical"
-            condition: "message.category == 'security' || message.priority == 'critical'"
-            target: "@security-ops"
-            priority: 20
-
-          - name: "technical-escalation"
-            condition: "message.category == 'technical' && message.complexity > 3"
-            target: "@technical-support"
-            priority: 10
-
-          - name: "billing-routing"
-            condition: "message.category == 'billing'"
-            target: "@billing-support"
-            priority: 8
-
-      delegation:
-        enabled: true
-        maxDepth: 3
-        timeout: 300
-        handoff:
-          enabled: true
-          preserveContext: true
-          handoffRules:
-            - name: "confidence-handoff"
-              condition: "confidence < 0.4"
-              target: "@technical-support"
-              message: "Low confidence — escalating to specialist"
-
-            - name: "vip-handoff"
-              condition: "customer.tier == 'enterprise'"
-              target: "@product-specialist"
-              message: "Enterprise customer requiring priority handling"
-
-      completionSignals:
-        enabled: true
-        signals: ["continue", "complete", "blocked", "escalate"]
-        handlers:
-          - signal: escalate
-            action: handoff
-            target: "@security-ops"
-          - signal: blocked
-            action: handoff
-            target: "@technical-support"
-          - signal: complete
-            action: notify
-
-      authentication:
-        type: jwt
-        jwt:
-          algorithm: RS256
-          issuer: agents.example.com
-
-      retryPolicy:
-        enabled: true
-        maxRetries: 3
-        backoff: exponential
-        retryableErrors:
-          - "UNAVAILABLE"
-          - "TIMEOUT"
-          - "RATE_LIMITED"
-
-      circuitBreaker:
-        enabled: true
-        failureThreshold: 5
-        successThreshold: 2
-        timeout: 120
-
-      observability:
-        tracing:
-          enabled: true
-          provider: opentelemetry
-          samplingRate: 1.0
-        metrics:
-          enabled: true
-          endpoint: "/metrics"
-        logging:
-          level: info
-          format: json

package/examples/showcase/security-scanner-enhanced.ossa.yaml

@@ -1,304 +0,0 @@
-apiVersion: ossa/v0.4.7
-kind: Agent
-metadata:
-  name: security-scanner-enhanced
-  version: 1.0.0
-  description: Advanced security scanner with vulnerability scanning, penetration testing, and compliance checking using nmap, OWASP ZAP, and custom scanners
-  labels:
-    ossa.dev/category: security
-    ossa.dev/tier: production-example
-    ossa.dev/autonomy: medium
-    ossa.dev/domain: security-operations
-    ossa.dev/execution: event-driven
-  annotations:
-    ossa.dev/documentation: https://openstandardagents.org/agents/security-scanner-enhanced
-    ossa.dev/tools: nmap,owasp-zap,custom-scanners
-    ossa.dev/triggers: khook,webhook,schedule
-spec:
-  capabilities:
-  - type: function
-    name: vulnerability.scan
-    description: Scan systems and applications for vulnerabilities
-    parameters:
-      type: object
-      properties:
-        target:
-          type: string
-          description: Target host, IP range, or application URL
-        scan_type:
-          type: string
-          enum: [network, web_app, container, cloud, api]
-          description: Type of vulnerability scan
-        depth:
-          type: string
-          enum: [quick, standard, deep, comprehensive]
-          default: standard
-        tools:
-          type: array
-          items:
-            type: string
-            enum: [nmap, zap, nikto, sqlmap, custom]
-          default: [nmap, zap]
-      required: [target, scan_type]
-  - type: function
-    name: penetration.test
-    description: Execute penetration testing procedures
-    parameters:
-      type: object
-      properties:
-        target:
-          type: string
-        test_scope:
-          type: array
-          items:
-            type: string
-            enum: [network, web, wireless, social_engineering, physical]
-        methodology:
-          type: string
-          enum: [owasp, ptes, osstmm, nist]
-          default: owasp
-        authorization:
-          type: object
-          properties:
-            authorized_by:
-              type: string
-            scope_document:
-              type: string
-            valid_until:
-              type: string
-              format: date-time
-          required: [authorized_by, valid_until]
-      required: [target, test_scope, authorization]
-  - type: function
-    name: compliance.check
-    description: Verify compliance with security policies and standards
-    parameters:
-      type: object
-      properties:
-        standards:
-          type: array
-          items:
-            type: string
-            enum: [PCI-DSS, ISO27001, NIST, CIS, OWASP-Top10]
-        scope:
-          type: string
-        baseline:
-          type: string
-          description: Baseline configuration for comparison
-      required: [standards, scope]
-  role: |
-    You are an advanced security scanning specialist responsible for identifying
-    vulnerabilities, executing penetration tests, and ensuring security compliance.
-
-    Your core responsibilities:
-    1. Vulnerability Scanning - Identify security weaknesses using multiple tools
-    2. Penetration Testing - Execute authorized security testing
-    3. Compliance Checking - Verify adherence to security standards
-    4. Threat Analysis - Analyze and classify security threats
-    5. Remediation Guidance - Provide actionable security fixes
-
-    Tools and methodologies:
-    - nmap: Network discovery and security scanning
-    - OWASP ZAP: Web application security scanner
-    - Custom scanners: Specialized security tools
-    - OWASP Top 10: Web application security risks
-    - CVE database: Known vulnerability tracking
-
-    Security scanning principles:
-    - Always operate within authorized scope
-    - Minimize impact on production systems
-    - Follow responsible disclosure practices
-    - Document all findings with evidence
-    - Provide risk-based prioritization
-
-    Always provide:
-    - Severity classification (Critical, High, Medium, Low, Info)
-    - CVE/CWE identifiers when applicable
-    - Affected components and versions
-    - Exploit availability and complexity
-    - Detailed remediation steps with references
-    - Evidence (screenshots, logs, payloads)
-  llm:
-    provider: anthropic
-    model: claude-sonnet-4
-    temperature: 0.1
-    maxTokens: 32768
-    features:
-      promptCaching: true
-      tokenEfficiency: false
-      batchProcessing: false
-  tools:
-  - type: function
-    name: nmap.scan
-    description: Network scanning and discovery tool
-  - type: function
-    name: zap.scan
-    description: Web application security scanner
-  - type: function
-    name: cve.lookup
-    description: Query CVE database for vulnerability details
-  - type: function
-    name: exploit.check
-    description: Check exploit availability for vulnerabilities
-  - type: function
-    name: report.generate
-    description: Generate security scan reports
-  autonomy:
-    mode: semi-autonomous
-    humanApproval: true
-    approvalRequired:
-      - before_penetration_test
-      - before_production_scan
-      - on_critical_finding
-    escalation:
-      enabled: true
-      triggers:
-        - critical_vulnerability
-        - active_exploit
-        - compliance_violation
-        - scan_blocked
-      contacts:
-        - role: security_team
-          method: slack
-          priority: high
-        - role: ciso
-          method: email
-          priority: critical
-        - role: soc
-          method: pagerduty
-          priority: critical
-  triggers:
-    khook:
-      enabled: true
-      events:
-        - type: deployment
-          action: trigger_scan
-          filter:
-            environment: [production, staging]
-        - type: code_commit
-          action: trigger_scan
-          filter:
-            branch: [main, master]
-        - type: configuration_change
-          action: trigger_scan
-    webhook:
-      enabled: true
-      endpoints:
-        - path: /scan/trigger
-          method: POST
-          authentication: bearer
-    schedule:
-      enabled: true
-      cron: "0 0 * * 0"  # Weekly on Sunday midnight
-      timezone: UTC
-  observability:
-    metrics:
-      enabled: true
-      provider: prometheus
-      port: 9093
-      custom:
-        - name: vulnerabilities_found
-          type: counter
-          labels: [severity, type]
-        - name: scans_completed
-          type: counter
-          labels: [scan_type, status]
-        - name: scan_duration
-          type: histogram
-          labels: [scan_type]
-        - name: critical_findings
-          type: gauge
-    logging:
-      level: info
-      format: json
-      destination: stdout
-      sensitive_data_filtering: true
-    tracing:
-      enabled: true
-      provider: opentelemetry
-      samplingRate: 1.0
-    alerts:
-      - name: critical_vulnerability_found
-        condition: vulnerabilities_found{severity="critical"} > 0
-        notification: pagerduty
-      - name: scan_failure
-        condition: scans_completed{status="failed"} > 3
-        notification: slack
-  resources:
-    memory: 4Gi
-    cpu: 2000m
-    storage: 20Gi
-    networkPolicy:
-      egress:
-        - to: internet
-          ports: [80, 443, 8080, 8443]
-      ingress:
-        - from: webhook_sources
-          ports: [8080]
-  state:
-    persistence: postgresql
-    ttl: 7776000  # 90 days
-    schema:
-      type: object
-      properties:
-        scan_history:
-          type: array
-        vulnerability_database:
-          type: object
-        baseline_configurations:
-          type: object
-        findings:
-          type: array
-          items:
-            type: object
-            properties:
-              id:
-                type: string
-              severity:
-                type: string
-              status:
-                type: string
-                enum: [open, in_progress, remediated, false_positive]
-              found_date:
-                type: string
-                format: date-time
-  retry:
-    enabled: true
-    maxAttempts: 2
-    backoff:
-      type: linear
-      initialDelay: 10s
-  security:
-    authentication:
-      required: true
-      methods:
-        - mutual_tls
-        - api_key
-    authorization:
-      rbac:
-        enabled: true
-        roles:
-          - security_admin
-          - security_analyst
-          - penetration_tester
-      policies:
-        - resource: scan
-          action: execute
-          conditions:
-            - authorized_scope
-            - valid_authorization
-    dataClassification:
-      - security_findings
-      - vulnerability_data
-      - confidential
-    encryption:
-      at_rest: true
-      in_transit: true
-    audit:
-      enabled: true
-      events:
-        - scan_initiated
-        - scan_completed
-        - critical_finding
-        - penetration_test_started
-        - compliance_check_failed

package/examples/showcase/security-scanner.ossa.yaml

@@ -1,66 +0,0 @@
-apiVersion: ossa/v0.4.7
-kind: Agent
-metadata:
-  name: security-scanner
-  version: 1.0.0
-  description: Security analysis agent with vulnerability and compliance scanning
-  labels:
-    ossa.dev/category: security
-    ossa.dev/tier: standard-example
-    ossa.dev/access-tier: elevated
-  annotations:
-    ossa.dev/documentation: https://openstandardagents.org/agents/security-scanner
-spec:
-  capabilities:
-  - type: function
-    name: security.scan
-    description: Scan codebase for security vulnerabilities
-  - type: function
-    name: security.audit
-    description: Audit dependencies for known CVEs
-  - type: function
-    name: security.secrets
-    description: Detect exposed secrets and credentials
-  - type: function
-    name: security.compliance
-    description: Check compliance against security policies
-  role: 'You are a security specialist agent responsible for identifying vulnerabilities,
-
-    auditing dependencies, detecting secrets, and ensuring compliance with security
-
-    policies.
-
-
-    Security scanning process:
-
-    1. Static analysis for common vulnerability patterns (OWASP Top 10)
-
-    2. Dependency vulnerability scanning (CVE database)
-
-    3. Secret detection (API keys, tokens, credentials)
-
-    4. Configuration security review
-
-    5. Compliance policy validation
-
-
-    Always provide:
-
-    - Severity classification (Critical, High, Medium, Low)
-
-    - Affected file and line number
-
-    - Remediation guidance
-
-    - References to CVEs or security advisories
-
-    '
-  llm:
-    provider: anthropic
-    model: claude-sonnet-4
-    temperature: 0.1
-    maxTokens: 16384
-  tools:
-  - type: function
-    name: scan.sast
-    description: Run static application security testing