@bluefly/openstandardagents 0.5.0 → 0.5.3

package/examples/pipeline-agent.ossa.yaml

@@ -1,196 +0,0 @@
-# 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:
-# ingest, transform, validate, and export. Each stage has specific tools
-# for its responsibility and hands off to the next stage upon completion.
-#
-# Key characteristics:
-#   - Pipeline pattern with sequential stages
-#   - Hub-spoke team model (coordinator manages stage transitions)
-#   - Each member represents one pipeline stage
-#   - Stage-specific tool sets
-#   - Assigned task coordination (coordinator assigns stage work)
-#   - Database-backed persistence for auditability
-
-apiVersion: ossa/v0.5.0
-kind: Agent
-metadata:
-  name: data-processing-pipeline
-  version: "1.0.0"
-  description: >-
-    A data processing pipeline with four sequential stages: ingest (fetch and
-    normalize raw data), transform (apply business rules and enrichment),
-    validate (quality checks and schema validation), and export (write to
-    destination systems). Each stage is an independent agent with its own
-    tools and model.
-
-  agentKind: coordinator
-  agentType: claude
-
-  agentArchitecture:
-    pattern: pipeline
-    capabilities:
-      - tools
-      - function-calling
-      - streaming
-    coordination:
-      handoffStrategy: conditional
-      leaderAgent: pipeline-controller
-      maxDepth: 1
-      teamModel: hub-spoke
-      communicationPattern: shared-file
-      taskCoordination: assigned
-      conflictResolution: leader-decides
-      taskPersistence: database
-      dependencyTracking: true
-
-  labels:
-    domain: data
-    pattern: pipeline
-    environment: production
-
-spec:
-  role: >-
-    You are the pipeline controller for a four-stage data processing workflow.
-    For each data batch:
-    1. Assign the batch to the ingest stage to fetch and normalize raw data.
-    2. Pass the normalized output to the transform stage for enrichment.
-    3. Send transformed data to the validate stage for quality checks.
-    4. Route validated data to the export stage for delivery.
-    Monitor each stage for errors. If a stage fails, log the error and skip
-    to the next batch. Maintain pipeline metrics (throughput, error rate,
-    latency per stage).
-
-  llm:
-    provider: anthropic
-    model: claude-sonnet-4-5-20250929
-    temperature: 0.1
-    maxTokens: 2048
-    profile: fast
-
-  team:
-    model: hub-spoke
-    lead: pipeline-controller
-    delegateMode: true
-
-    members:
-      - name: ingest-stage
-        kind: teammate
-        role: >-
-          Stage 1: Data Ingestion. Fetch raw data from configured sources
-          (APIs, S3 buckets, databases). Normalize into a common internal
-          format (JSON Lines). Handle pagination, rate limiting, and partial
-          failures. Output normalized records to the shared staging area.
-        model:
-          provider: anthropic
-          name: claude-haiku-4-5-20250514
-        tools:
-          - fetch_api
-          - read_s3
-          - query_database
-          - write_staging
-        contextIsolation: true
-        workingDirectory: /pipeline/ingest
-        handoffs:
-          - to: pipeline-controller
-            condition: "Ingestion complete or fatal error"
-
-      - name: transform-stage
-        kind: teammate
-        role: >-
-          Stage 2: Data Transformation. Read normalized records from staging.
-          Apply business rules: field mapping, currency conversion, date
-          normalization, and entity enrichment from reference tables. Output
-          enriched records to the transform output area.
-        model:
-          provider: anthropic
-          name: claude-haiku-4-5-20250514
-        tools:
-          - read_staging
-          - apply_mapping
-          - enrich_entity
-          - write_transform_output
-        contextIsolation: true
-        workingDirectory: /pipeline/transform
-        handoffs:
-          - to: pipeline-controller
-            condition: "Transformation complete or fatal error"
-
-      - name: validate-stage
-        kind: teammate
-        role: >-
-          Stage 3: Data Validation. Read transformed records and run quality
-          checks: schema validation, referential integrity, business rule
-          assertions, and anomaly detection. Flag invalid records and produce
-          a validation report. Output clean records to the validated area.
-        model:
-          provider: anthropic
-          name: claude-sonnet-4-5-20250929
-        tools:
-          - read_transform_output
-          - validate_schema
-          - check_integrity
-          - write_validated_output
-        contextIsolation: true
-        workingDirectory: /pipeline/validate
-        handoffs:
-          - to: pipeline-controller
-            condition: "Validation complete or fatal error"
-
-      - name: export-stage
-        kind: teammate
-        role: >-
-          Stage 4: Data Export. Read validated records and write to destination
-          systems: data warehouse, analytics database, or external APIs.
-          Handle batching, idempotency, and delivery confirmation. Produce
-          an export receipt with record counts and delivery timestamps.
-        model:
-          provider: anthropic
-          name: claude-haiku-4-5-20250514
-        tools:
-          - read_validated_output
-          - write_warehouse
-          - call_external_api
-          - write_export_receipt
-        contextIsolation: true
-        workingDirectory: /pipeline/export
-        handoffs:
-          - to: pipeline-controller
-            condition: "Export complete or fatal error"
-
-    taskList:
-      coordination: assigned
-      persistence: database
-      stateModel:
-        - pending
-        - in-progress
-        - completed
-        - failed
-        - skipped
-      dependencyTracking: true
-      waveExecution: false
-      lockingStrategy: optimistic
-
-    communication:
-      pattern: shared-file
-      broadcastEnabled: false
-
-    deployment:
-      backend: distributed
-      scaling: auto
-
-  constraints:
-    cost:
-      maxTokensPerDay: 1000000
-      maxCostPerDay: 40.00
-      currency: USD
-    performance:
-      maxLatencySeconds: 60
-      maxConcurrentRequests: 10
-      timeoutSeconds: 300
-
-  lifecycle:
-    max_turns: 100
-    turn_timeout: 60s
-    checkpoint_interval: 10

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

@@ -1,185 +0,0 @@
-apiVersion: ossa/v0.3.3
-kind: Agent
-metadata:
-  name: claude-code-explorer
-  version: 1.0.0
-  description: Specialized sub-agent for deep code exploration and codebase analysis
-  author: Agent Platform
-  tags:
-    - claude-code
-    - subagent
-    - code-analysis
-    - exploration
-  license: MIT
-
-spec:
-  role: |
-    You are a code exploration specialist sub-agent for Claude Code. Your expertise
-    is in deeply analyzing codebases, identifying patterns, and providing detailed
-    insights about code structure and dependencies.
-
-    Your responsibilities:
-    - Analyze code architecture and design patterns
-    - Map dependencies and identify coupling issues
-    - Detect code smells and potential issues
-    - Provide detailed insights about code organization
-    - Identify opportunities for refactoring and improvement
-
-    You use a systematic approach to explore code:
-    1. Start with high-level structure (directories, modules)
-    2. Analyze key files and entry points
-    3. Map dependencies and relationships
-    4. Identify patterns and anti-patterns
-    5. Provide actionable insights
-
-  capabilities:
-    - explore
-    - code-analysis
-    - pattern-detection
-    - dependency-mapping
-    - architecture-analysis
-
-  tools:
-    - type: function
-      name: analyze_codebase
-      description: Analyze codebase structure and patterns
-      inputSchema:
-        type: object
-        properties:
-          path:
-            type: string
-            description: Path to analyze (directory or file)
-          depth:
-            type: number
-            description: Analysis depth (directory levels)
-            default: 3
-          patterns:
-            type: array
-            items:
-              type: string
-            description: Specific patterns to look for
-          exclude:
-            type: array
-            items:
-              type: string
-            description: Paths to exclude
-            default: [node_modules, .git, dist, build]
-        required:
-          - path
-
-    - type: function
-      name: find_dependencies
-      description: Find and map code dependencies
-      inputSchema:
-        type: object
-        properties:
-          file:
-            type: string
-            description: File to analyze dependencies for
-          include_transitive:
-            type: boolean
-            description: Include transitive dependencies
-            default: false
-          visualize:
-            type: boolean
-            description: Generate dependency graph
-            default: true
-        required:
-          - file
-
-    - type: function
-      name: detect_patterns
-      description: Detect design patterns and anti-patterns in code
-      inputSchema:
-        type: object
-        properties:
-          path:
-            type: string
-            description: Path to analyze
-          pattern_types:
-            type: array
-            items:
-              type: string
-              enum:
-                - design-patterns
-                - anti-patterns
-                - code-smells
-                - architectural-patterns
-            description: Types of patterns to detect
-            default: [design-patterns, anti-patterns]
-        required:
-          - path
-
-    - type: function
-      name: analyze_complexity
-      description: Analyze code complexity metrics
-      inputSchema:
-        type: object
-        properties:
-          path:
-            type: string
-            description: Path to analyze
-          metrics:
-            type: array
-            items:
-              type: string
-              enum:
-                - cyclomatic
-                - cognitive
-                - halstead
-                - maintainability-index
-            description: Complexity metrics to calculate
-            default: [cyclomatic, cognitive]
-          threshold:
-            type: number
-            description: Complexity threshold for reporting
-            default: 10
-        required:
-          - path
-
-    - type: function
-      name: generate_insights
-      description: Generate insights and recommendations from analysis
-      inputSchema:
-        type: object
-        properties:
-          analysis_results:
-            type: object
-            description: Results from previous analysis tools
-          focus_areas:
-            type: array
-            items:
-              type: string
-              enum:
-                - architecture
-                - performance
-                - maintainability
-                - security
-                - testability
-            description: Areas to focus insights on
-            default: [architecture, maintainability]
-          include_examples:
-            type: boolean
-            description: Include code examples in insights
-            default: true
-        required:
-          - analysis_results
-
-  llm:
-    provider: anthropic
-    model: claude-sonnet-4
-    max_tokens: 4000
-    temperature: 0.2
-
-  max_iterations: 15
-
-  access:
-    tier: tier_1_read
-    scopes:
-      - read_api
-      - read_repository
-
-  deployment:
-    runtime: subagent
-    platform: claude-code
-    parent_agent: claude-code-cli

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

@@ -1,175 +0,0 @@
-apiVersion: ossa/v0.3.3
-kind: Agent
-metadata:
-  name: cursor-coding-assistant
-  version: 1.0.0
-  description: AI coding assistant for Cursor IDE with advanced code generation and refactoring
-  author: Agent Platform
-  tags:
-    - cursor
-    - coding-assistant
-    - ai
-    - ide
-    - code-generation
-  license: MIT
-
-spec:
-  role: |
-    You are an expert coding assistant that helps developers write clean, efficient,
-    and maintainable code. You specialize in:
-    - Generating high-quality code from natural language descriptions
-    - Refactoring existing code for better quality and performance
-    - Providing best practices guidance and code reviews
-    - Writing comprehensive tests for code
-    - Creating clear documentation
-
-    Always prioritize code quality, readability, and maintainability. Follow
-    language-specific conventions and best practices.
-
-  capabilities:
-    - code-generation
-    - code-review
-    - refactoring
-    - testing
-    - documentation
-
-  tools:
-    - type: function
-      name: generate_code
-      description: Generate code based on natural language description
-      inputSchema:
-        type: object
-        properties:
-          description:
-            type: string
-            description: Natural language description of desired functionality
-          language:
-            type: string
-            enum: [typescript, javascript, python, go, rust, java]
-            description: Target programming language
-          framework:
-            type: string
-            description: Framework to use (optional)
-          style:
-            type: string
-            enum: [functional, object-oriented, procedural]
-            description: Programming style preference
-            default: functional
-          include_tests:
-            type: boolean
-            description: Whether to include unit tests
-            default: true
-        required:
-          - description
-          - language
-
-    - type: function
-      name: refactor_code
-      description: Refactor existing code for better quality
-      inputSchema:
-        type: object
-        properties:
-          code:
-            type: string
-            description: Code to refactor
-          goals:
-            type: array
-            items:
-              type: string
-              enum: [readability, performance, maintainability, testability]
-            description: Refactoring goals
-            default: [readability, maintainability]
-          preserve_behavior:
-            type: boolean
-            description: Ensure behavior is preserved
-            default: true
-        required:
-          - code
-
-    - type: function
-      name: generate_tests
-      description: Generate comprehensive tests for code
-      inputSchema:
-        type: object
-        properties:
-          code:
-            type: string
-            description: Code to generate tests for
-          test_framework:
-            type: string
-            description: Test framework to use (e.g., jest, pytest, go test)
-          coverage_target:
-            type: number
-            description: Target code coverage percentage
-            default: 80
-          include_edge_cases:
-            type: boolean
-            description: Include edge case tests
-            default: true
-        required:
-          - code
-
-    - type: function
-      name: document_code
-      description: Generate documentation for code
-      inputSchema:
-        type: object
-        properties:
-          code:
-            type: string
-            description: Code to document
-          style:
-            type: string
-            enum: [jsdoc, docstring, rustdoc, javadoc]
-            description: Documentation style
-          include_examples:
-            type: boolean
-            description: Include usage examples
-            default: true
-        required:
-          - code
-
-    - type: function
-      name: code_review
-      description: Perform automated code review
-      inputSchema:
-        type: object
-        properties:
-          code:
-            type: string
-            description: Code to review
-          checks:
-            type: array
-            items:
-              type: string
-              enum:
-                - style
-                - security
-                - performance
-                - complexity
-                - best-practices
-            description: Types of checks to perform
-            default: [style, security, complexity]
-          severity_threshold:
-            type: string
-            enum: [info, warning, error, critical]
-            description: Minimum severity to report
-            default: warning
-        required:
-          - code
-
-  llm:
-    provider: anthropic
-    model: claude-opus-4
-    max_tokens: 8000
-    temperature: 0.3
-
-  access:
-    tier: tier_1_read
-    scopes:
-      - read_api
-      - read_repository
-
-  deployment:
-    runtime: ide
-    platform: cursor

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

@@ -1,122 +0,0 @@
-apiVersion: ossa/v0.3.3
-kind: Agent
-metadata:
-  name: warp-dev-agent
-  version: 1.0.0
-  description: Development workflow agent for Warp Terminal
-  author: Agent Platform
-  tags:
-    - warp
-    - terminal
-    - development
-    - workflow
-  license: MIT
-
-spec:
-  role: |
-    You are a development workflow assistant that helps developers with common
-    terminal tasks in Warp Terminal. You provide streamlined commands for git
-    operations, testing, deployment, and code review.
-
-  capabilities:
-    - git-operations
-    - testing
-    - deployment
-    - code-review
-    - project-setup
-
-  tools:
-    - type: command
-      name: git_commit
-      description: Create a git commit with conventional commit format
-      inputSchema:
-        type: object
-        properties:
-          type:
-            type: string
-            enum: [feat, fix, docs, style, refactor, test, chore]
-            description: Commit type (conventional commits)
-          scope:
-            type: string
-            description: Commit scope (optional)
-          message:
-            type: string
-            description: Commit message
-          breaking:
-            type: boolean
-            description: Whether this is a breaking change
-            default: false
-        required:
-          - type
-          - message
-
-    - type: command
-      name: run_tests
-      description: Run project tests and display results
-      inputSchema:
-        type: object
-        properties:
-          pattern:
-            type: string
-            description: Test file pattern (e.g., "**/*.test.ts")
-          watch:
-            type: boolean
-            description: Run tests in watch mode
-            default: false
-          coverage:
-            type: boolean
-            description: Generate coverage report
-            default: false
-
-    - type: command
-      name: deploy
-      description: Deploy project to specified environment
-      inputSchema:
-        type: object
-        properties:
-          environment:
-            type: string
-            enum: [dev, staging, production]
-            description: Deployment environment
-          branch:
-            type: string
-            description: Git branch to deploy
-          dry_run:
-            type: boolean
-            description: Perform dry run without actual deployment
-            default: false
-        required:
-          - environment
-
-    - type: command
-      name: code_review
-      description: Perform automated code review on changes
-      inputSchema:
-        type: object
-        properties:
-          target_branch:
-            type: string
-            description: Branch to compare against
-            default: main
-          files:
-            type: array
-            items:
-              type: string
-            description: Specific files to review (optional)
-          checks:
-            type: array
-            items:
-              type: string
-              enum: [style, security, performance, complexity]
-            description: Types of checks to perform
-            default: [style, security]
-
-  access:
-    tier: tier_3_full_access
-    scopes:
-      - read_api
-      - write_repository
-
-  deployment:
-    runtime: terminal
-    platform: warp