blades

Source#

• Repository: go-kratos/blades
• Last source update: 2026-04-04
• Last verified: 2026-04-05

Tags#

Integration notes#

Repository is workflow-oriented; map each workflow step to explicit worker contracts for predictability.

worker.md example#

Starter worker.md contract mapped from this registry entry. Copy this file and adapt schemas, constraints, and statuses for your task.

---
id: blades-repo-derived-worker
name: blades Repo-Derived Worker
version: 1.0.0
source_registry_url: https://worker.md/registry/blades/
source_repository: https://github.com/go-kratos/blades
repository_default_branch: main
repository_language: Go
repository_license: MIT
repository_updated_at: 2026-04-04
worker_mode: agent-orchestration-worker
derivation_method: github_repository_metadata_plus_raw_readme
derivation_confidence: 0.9
derived_on: 2026-04-05
tags:
  - agent
  - agent-framework
  - agent-kit
  - agent-sdk
  - agent-workflow
  - ai
---

# blades Repo-Derived Worker

## Repo-derived summary
- Registry summary: Blades is a Go-based multimodal AI Agent framework.
- Repository description: Blades is a Go-based multimodal AI Agent framework.
- Stars (snapshot): 749
- Primary language: Go
- Worker mode classification: agent-orchestration-worker

## Extracted from
- https://github.com/go-kratos/blades
- https://github.com/go-kratos/blades/blob/main/README.md

## Evidence notes (from repository text)
- README summary paragraph: ## Blades Blades is a multimodal AI Agent framework for the Go language, supporting custom models, tools, memory, middleware, etc. It is suitable for multi-turn conversations, chain-of-thought reasoning, and structured output, among other use cases. > The name originates from: The game *God of War*, set against the backdrop of Greek mythology, tells the adventure story of Kratos transforming from a mortal into the God of War and embarking on a god-slaying rampage. The Blades are Kratos's iconic weapons.
- - Simple to Use: Define AI Agents through concise code declarations, enabling rapid requirement delivery and making complex logic clear, easy to manage, and maintain.
- - Middleware Ecosystem: Drawing inspiration from Kratos's middleware design philosophy, features like Observability and Guardrails can be easily integrated into AI Agents.
- - Highly Extensible: Achieves a high degree of decoupling and extensibility through unified interfaces and pluggable components, facilitating the integration of different LLM models and external tools.
- The Blades framework realizes its powerful functionality and flexibility through a series of carefully designed core components. These components work together to build the intelligent behavior of the Agent:
- * Agent: The core unit that executes tasks, capable of invoking models and tools.

## Installation hints found in README
- No explicit package installation command detected in README text.

## worker.md contract (derived starter)
Purpose: Execute one orchestrated agent task as a bounded worker step.

### Input schema
```json
{
  "type": "object",
  "additionalProperties": false,
  "required": [
    "run_id",
    "task",
    "context"
  ],
  "properties": {
    "run_id": {
      "type": "string"
    },
    "task": {
      "type": "string"
    },
    "context": {
      "type": "object"
    }
  }
}
```

### Output schema
```json
{
  "type": "object",
  "additionalProperties": false,
  "required": [
    "run_id",
    "status",
    "result"
  ],
  "properties": {
    "run_id": {
      "type": "string"
    },
    "status": {
      "type": "string",
      "enum": [
        "ok",
        "retryable_error",
        "invalid_request",
        "invalid_output"
      ]
    },
    "result": {
      "type": "object"
    }
  }
}
```

### Constraints
- timeout_seconds: 30
- max_attempts: 2
- idempotency_key: run_id
- status_enum: [ok, retryable_error, invalid_request, invalid_output]
- notes: adapt to concrete APIs/classes documented in this repository before production use

## How this should be used
1. Treat this file as a repo-derived starter profile, not a claim of an official repository API contract.
2. Replace schemas with exact interfaces from code/docs you adopt.
3. Keep execution bounded and auditable using worker protocol constraints.

How to use#

• Save this as a worker spec file (for example: blades-my-task.worker.md).
• Replace the input/output schemas and purpose with your real bounded task.
• Enforce schema validation + timeout + retry policy in your runtime before production use.

Citation#

Reference URL: https://worker.md/registry/blades/

Source URL: https://github.com/go-kratos/blades