@bluefly/openstandardagents 0.5.0 → 0.5.3

package/examples/ossa-templates/02-security-scanner.ossa.yaml

@@ -1,103 +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:
-  - name: security.scan
-    description: Scan codebase for security vulnerabilities
-  - name: security.audit
-    description: Audit dependencies for known CVEs
-  - name: security.secrets
-    description: Detect exposed secrets and credentials
-  - 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: ${OSSA_LLM_PROVIDER:-anthropic}
-    model: ${OSSA_LLM_MODEL:-claude-sonnet-4}
-    temperature: 0.1
-    maxTokens: ${OSSA_LLM_MAX_TOKENS:-16384}
-  tools:
-  - name: scan.sast
-    description: Run static application security testing
-    handler:
-      runtime: docker
-      image: returntocorp/semgrep:latest
-      command:
-      - semgrep
-      - --config=auto
-    type: function
-  - name: scan.dependencies
-    description: Scan dependencies for vulnerabilities
-    handler:
-      runtime: docker
-      image: aquasec/trivy:latest
-      command:
-      - trivy
-      - fs
-      - .
-    type: function
-  - name: scan.secrets
-    description: Detect secrets in codebase
-    handler:
-      runtime: docker
-      image: trufflesecurity/trufflehog:latest
-      command:
-      - filesystem
-      - .
-    type: function
-  - name: report.generate
-    description: Generate security report
-    handler:
-      runtime: local
-      capability: report.generate
-    type: function
-  safety:
-    constraints:
-    - Never expose actual secret values in reports
-    - Redact sensitive information before logging
-    - Rate limit external vulnerability database queries
-    policies:
-    - policy: no-secret-exposure
-      description: All detected secrets must be redacted in output
-    - policy: audit-logging
-      description: All scans must be logged for compliance

package/examples/ossa-templates/03-ci-pipeline.ossa.yaml

@@ -1,100 +0,0 @@
-apiVersion: ossa/v0.4.7
-kind: Agent
-metadata:
-  name: ci-pipeline
-  version: 1.0.0
-  description: CI/CD automation agent for pipeline management
-  labels:
-    ossa.dev/category: devops
-    ossa.dev/tier: standard-example
-    ossa.dev/runtime: gitlab-ci
-  annotations:
-    ossa.dev/documentation: https://openstandardagents.org/agents/ci-pipeline
-spec:
-  capabilities:
-  - name: ci.trigger
-    description: Trigger CI/CD pipeline runs
-  - name: ci.monitor
-    description: Monitor pipeline status and jobs
-  - name: ci.fix
-    description: Analyze and fix pipeline failures
-  - name: ci.optimize
-    description: Optimize pipeline performance
-  role: 'You are a CI/CD automation specialist responsible for managing build, test,
-
-    and deployment pipelines. You can trigger pipelines, monitor their status,
-
-    diagnose failures, and optimize performance.
-
-
-    Pipeline management:
-
-    1. Trigger appropriate pipelines based on changes
-
-    2. Monitor job status and detect failures early
-
-    3. Analyze failure logs and suggest fixes
-
-    4. Optimize pipeline DAGs for faster execution
-
-    5. Manage deployment approvals and rollbacks
-
-    '
-  llm:
-    provider: ${OSSA_LLM_PROVIDER:-anthropic}
-    model: ${OSSA_LLM_MODEL:-claude-sonnet-4}
-    temperature: 0.2
-    maxTokens: ${OSSA_LLM_MAX_TOKENS:-8192}
-  tools:
-  - name: gitlab.pipeline.trigger
-    description: Trigger a GitLab CI pipeline
-    handler:
-      runtime: api
-      endpoint: ${GITLAB_API_URL}/projects/${CI_PROJECT_ID}/pipeline
-      method: POST
-    type: function
-  - name: gitlab.pipeline.status
-    description: Get pipeline status
-    handler:
-      runtime: api
-      endpoint: ${GITLAB_API_URL}/projects/${CI_PROJECT_ID}/pipelines/${PIPELINE_ID}
-      method: GET
-    type: function
-  - name: gitlab.job.log
-    description: Get job logs for analysis
-    handler:
-      runtime: api
-      endpoint: ${GITLAB_API_URL}/projects/${CI_PROJECT_ID}/jobs/${JOB_ID}/trace
-      method: GET
-    type: function
-  - name: gitlab.mr.create
-    description: Create merge request with fixes
-    handler:
-      runtime: api
-      endpoint: ${GITLAB_API_URL}/projects/${CI_PROJECT_ID}/merge_requests
-      method: POST
-    type: function
-  messaging:
-    transport: redis
-    queues:
-    - name: ci-events
-      description: CI/CD event notifications
-    - name: ci-commands
-      description: Pipeline commands
-    events:
-      publish:
-      - pipeline.triggered
-      - pipeline.completed
-      - pipeline.failed
-      subscribe:
-      - merge_request.created
-      - push.received
-extensions:
-  gitlab:
-    project_access_token: ${CI_JOB_TOKEN}
-    api_version: v4
-    webhooks:
-    - event: pipeline_events
-      url: ${OSSA_WEBHOOK_URL}/ci-pipeline
-    - event: merge_request_events
-      url: ${OSSA_WEBHOOK_URL}/ci-pipeline

package/examples/ossa-templates/04-code-reviewer.ossa.yaml

@@ -1,116 +0,0 @@
-apiVersion: ossa/v0.4.7
-kind: Agent
-metadata:
-  name: code-reviewer
-  version: 1.0.0
-  description: Automated code review agent with quality analysis
-  labels:
-    ossa.dev/category: development
-    ossa.dev/tier: standard-example
-    ossa.dev/access-tier: standard
-  annotations:
-    ossa.dev/documentation: https://openstandardagents.org/agents/code-reviewer
-spec:
-  capabilities:
-  - name: review.analyze
-    description: Analyze code changes for issues
-  - name: review.comment
-    description: Add review comments on specific lines
-  - name: review.approve
-    description: Approve merge requests (requires elevated access)
-  - name: review.request-changes
-    description: Request changes with specific feedback
-  role: 'You are a code reviewer responsible for maintaining code quality standards.
-
-    Review merge requests for:
-
-
-    1. Code correctness and potential bugs
-
-    2. Security vulnerabilities
-
-    3. Performance implications
-
-    4. Code style and conventions
-
-    5. Test coverage
-
-    6. Documentation completeness
-
-
-    Provide constructive, actionable feedback. Be specific about issues and
-
-    suggest concrete improvements. Acknowledge good patterns and practices.
-
-    '
-  llm:
-    provider: ${OSSA_LLM_PROVIDER:-anthropic}
-    model: ${OSSA_LLM_MODEL:-claude-sonnet-4}
-    temperature: 0.3
-    maxTokens: ${OSSA_LLM_MAX_TOKENS:-16384}
-  tools:
-  - name: mr.diff
-    description: Get merge request diff
-    handler:
-      runtime: api
-      endpoint: ${GITLAB_API_URL}/projects/${CI_PROJECT_ID}/merge_requests/${MR_IID}/diffs
-      method: GET
-    type: function
-  - name: mr.comment
-    description: Add comment to merge request
-    handler:
-      runtime: api
-      endpoint: ${GITLAB_API_URL}/projects/${CI_PROJECT_ID}/merge_requests/${MR_IID}/discussions
-      method: POST
-    type: function
-  - name: mr.approve
-    description: Approve merge request
-    handler:
-      runtime: api
-      endpoint: ${GITLAB_API_URL}/projects/${CI_PROJECT_ID}/merge_requests/${MR_IID}/approve
-      method: POST
-    type: function
-  - name: lint.check
-    description: Run linting tools
-    handler:
-      runtime: docker
-      image: node:20-alpine
-      command:
-      - npx
-      - eslint
-      - --format=json
-    type: function
-  contracts:
-    provides:
-    - name: code-review
-      version: '1.0'
-      schema:
-        input:
-          type: object
-          properties:
-            mr_iid:
-              type: integer
-              description: Merge request IID
-            project_id:
-              type: integer
-              description: GitLab project ID
-        output:
-          type: object
-          properties:
-            status:
-              type: string
-              enum:
-              - approved
-              - changes_requested
-              - commented
-            comments:
-              type: array
-              items:
-                type: object
-                properties:
-                  file:
-                    type: string
-                  line:
-                    type: integer
-                  comment:
-                    type: string

package/examples/ossa-templates/05-doc-generator.ossa.yaml

@@ -1,102 +0,0 @@
-apiVersion: ossa/v0.4.7
-kind: Agent
-metadata:
-  name: doc-generator
-  version: 1.0.0
-  description: Automated documentation generation agent
-  labels:
-    ossa.dev/category: documentation
-    ossa.dev/tier: standard-example
-  annotations:
-    ossa.dev/documentation: https://openstandardagents.org/agents/doc-generator
-spec:
-  capabilities:
-  - name: docs.api
-    description: Generate API documentation from code
-  - name: docs.readme
-    description: Generate or update README files
-  - name: docs.changelog
-    description: Generate changelog from commits
-  - name: docs.technical
-    description: Generate technical documentation
-  role: 'You are a technical documentation specialist responsible for generating
-
-    and maintaining project documentation.
-
-
-    Documentation types:
-
-    1. API Documentation - Generate from code, OpenAPI specs, or schemas
-
-    2. README - Project overview, installation, usage, examples
-
-    3. Changelog - Semantic versioning, conventional commits
-
-    4. Technical Docs - Architecture, design decisions, guides
-
-
-    Always:
-
-    - Use clear, concise language
-
-    - Include code examples where appropriate
-
-    - Follow project documentation conventions
-
-    - Keep documentation in sync with code
-
-    '
-  llm:
-    provider: ${OSSA_LLM_PROVIDER:-anthropic}
-    model: ${OSSA_LLM_MODEL:-claude-sonnet-4}
-    temperature: 0.5
-    maxTokens: ${OSSA_LLM_MAX_TOKENS:-16384}
-    fallback:
-    - provider: openai
-      model: gpt-4o
-    - provider: google
-      model: gemini-2.0-flash
-  tools:
-  - name: code.analyze
-    description: Analyze code structure for documentation
-    handler:
-      runtime: local
-      capability: ast.parse
-    type: function
-  - name: openapi.parse
-    description: Parse OpenAPI specification
-    handler:
-      runtime: local
-      capability: openapi.parse
-    type: function
-  - name: git.log
-    description: Get git commit history
-    handler:
-      runtime: local
-      capability: git.log
-    type: function
-  - name: markdown.write
-    description: Write markdown documentation
-    handler:
-      runtime: local
-      capability: fs.write
-    type: function
-  - name: wiki.publish
-    description: Publish to GitLab wiki
-    handler:
-      runtime: api
-      endpoint: ${GITLAB_API_URL}/projects/${CI_PROJECT_ID}/wikis
-      method: POST
-    type: function
-  templates:
-    readme:
-      path: .ossa/templates/readme.md.template
-      variables:
-      - project_name
-      - description
-      - installation
-      - usage
-      - contributing
-    changelog:
-      path: .ossa/templates/changelog.md.template
-      format: conventional-commits

package/examples/ossa-templates/06-compliance-validator.ossa.yaml

@@ -1,132 +0,0 @@
-apiVersion: ossa/v0.4.7
-kind: Agent
-metadata:
-  name: compliance-validator
-  version: 1.0.0
-  description: OSSA compliance validation and policy enforcement agent
-  labels:
-    ossa.dev/category: compliance
-    ossa.dev/tier: standard-example
-  annotations:
-    ossa.dev/documentation: https://openstandardagents.org/agents/compliance-validator
-spec:
-  capabilities:
-  - name: validate.manifest
-    description: Validate OSSA manifest against schema
-  - name: validate.contract
-    description: Validate agent contracts
-  - name: validate.policy
-    description: Enforce organizational policies
-  - name: validate.migration
-    description: Validate migration compatibility
-  role: 'You are the OSSA compliance validator responsible for ensuring all agent
-
-    manifests comply with the OSSA specification and organizational policies.
-
-
-    Validation scope:
-
-    1. Schema Compliance - Validate against OSSA JSON Schema
-
-    2. Contract Validation - Verify input/output contracts
-
-    3. Policy Enforcement - Apply organizational policies
-
-    4. Migration Checks - Ensure backward compatibility
-
-
-    Report all violations with:
-
-    - Severity level (error, warning, info)
-
-    - Location in manifest
-
-    - Specific violation description
-
-    - Remediation guidance
-
-    '
-  llm:
-    provider: ${OSSA_LLM_PROVIDER:-anthropic}
-    model: ${OSSA_LLM_MODEL:-claude-sonnet-4}
-    temperature: 0.1
-    maxTokens: ${OSSA_LLM_MAX_TOKENS:-8192}
-  tools:
-  - name: schema.validate
-    description: Validate manifest against JSON Schema
-    handler:
-      runtime: local
-      capability: jsonschema.validate
-    type: function
-  - name: manifest.parse
-    description: Parse OSSA manifest (YAML/JSON)
-    handler:
-      runtime: local
-      capability: manifest.parse
-    type: function
-  - name: policy.evaluate
-    description: Evaluate against policy rules
-    handler:
-      runtime: local
-      capability: policy.evaluate
-    type: function
-  - name: report.generate
-    description: Generate validation report
-    handler:
-      runtime: local
-      capability: report.generate
-    type: function
-  policies:
-    rules:
-    - id: require-metadata-version
-      description: All manifests must specify metadata.version
-      severity: error
-      check: metadata.version != null
-    - id: require-role-definition
-      description: Agents must have role definition
-      severity: error
-      check: spec.role != null && spec.role.length > 50
-    - id: require-capabilities
-      description: Agents should declare capabilities
-      severity: warning
-      check: spec.capabilities != null && spec.capabilities.length > 0
-    - id: require-llm-config
-      description: Agents should specify LLM configuration
-      severity: warning
-      check: spec.llm != null
-    - id: no-hardcoded-secrets
-      description: No hardcoded secrets in manifest
-      severity: error
-      check: '!contains(toString(.), ''sk-'') && !contains(toString(.), ''glpat-'')'
-  contracts:
-    provides:
-    - name: ossa-validation
-      version: '1.0'
-      schema:
-        input:
-          type: object
-          properties:
-            manifest_path:
-              type: string
-              description: Path to manifest file
-            policy_set:
-              type: string
-              description: Policy set to apply (default, strict, permissive)
-        output:
-          type: object
-          properties:
-            valid:
-              type: boolean
-            errors:
-              type: array
-              items:
-                type: object
-                properties:
-                  severity:
-                    type: string
-                  path:
-                    type: string
-                  message:
-                    type: string
-            warnings:
-              type: array

package/examples/ossa-templates/07-workflow-orchestrator.ossa.yaml

@@ -1,110 +0,0 @@
-apiVersion: ossa/v0.4.7
-kind: Workflow
-metadata:
-  name: workflow-orchestrator
-  version: 1.0.0
-  description: Multi-agent workflow orchestration and coordination
-  labels:
-    ossa.dev/category: orchestration
-    ossa.dev/tier: standard-example
-  annotations:
-    ossa.dev/documentation: https://openstandardagents.org/agents/workflow-orchestrator
-spec:
-  execution:
-    type: orchestrated
-    parallelism: 5
-    timeout: 3600s
-  capabilities:
-  - name: workflow.create
-    description: Create and configure workflows
-  - name: workflow.execute
-    description: Execute multi-agent workflows
-  - name: workflow.monitor
-    description: Monitor workflow execution status
-  - name: workflow.route
-    description: Route tasks to appropriate agents
-  role: 'You are the workflow orchestrator responsible for coordinating complex
-
-    multi-agent workflows. You manage task routing, state persistence,
-
-    and agent-to-agent communication.
-
-
-    Orchestration patterns:
-
-    1. Sequential - Execute agents in order
-
-    2. Parallel - Execute multiple agents concurrently
-
-    3. Conditional - Route based on conditions
-
-    4. Fan-out/Fan-in - Distribute and aggregate
-
-    5. Human-in-the-loop - Pause for human approval
-
-    '
-  llm:
-    provider: ${OSSA_LLM_PROVIDER:-anthropic}
-    model: ${OSSA_LLM_MODEL:-claude-sonnet-4}
-    temperature: 0.2
-    maxTokens: ${OSSA_LLM_MAX_TOKENS:-8192}
-  agents:
-  - ref: code-reviewer
-    alias: reviewer
-    on_complete: security-scanner
-  - ref: security-scanner
-    alias: security
-    on_complete: ci-pipeline
-  - ref: ci-pipeline
-    alias: pipeline
-    condition: security.result.passed == true
-  steps:
-  - id: review
-    agent: reviewer
-    input:
-      mr_iid: ${input.mr_iid}
-      project_id: ${input.project_id}
-  - id: security
-    agent: security
-    depends_on:
-    - review
-    condition: review.status == "approved"
-    input:
-      paths: ${input.changed_files}
-  - id: deploy
-    agent: pipeline
-    depends_on:
-    - security
-    condition: security.passed == true
-    input:
-      action: deploy
-      environment: ${input.environment}
-  state:
-    persistence: redis
-    ttl: 86400
-    schema:
-      type: object
-      properties:
-        current_step:
-          type: string
-        completed_steps:
-          type: array
-        results:
-          type: object
-  messaging:
-    transport: redis
-    queues:
-    - name: workflow-events
-      description: Workflow lifecycle events
-    - name: agent-results
-      description: Agent execution results
-    events:
-      publish:
-      - workflow.started
-      - workflow.completed
-      - workflow.failed
-      - step.completed
-      subscribe:
-      - agent.completed
-      - agent.failed
-      - human.approved