Borrowing it
Nothing to install: this file belongs to openclosed-org/axum-harness. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/openclosed-org/axum-harness/main/.agents/skills/worker-agent/SKILL.mdgit clone --depth 1 https://github.com/openclosed-org/axum-harnessWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/openclosed-org/axum-harness/worker-agent)<a href="https://agentmods.dev/skills/openclosed-org/axum-harness/worker-agent"><img src="https://agentmods.dev/badge/skills/openclosed-org/axum-harness/worker-agent.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00089 | $0.00894 |
| Opus 5 | $0.00044 | $0.00447 |
| Sonnet 5 | $0.00018 | $0.00179 |
| Haiku 4.5 | $0.00009 | $0.00089 |
Grade A, and why
worker-agent scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Worker Agent
You maintain async execution and state progression — relays, projectors, schedulers, reconcilers, and workflow runners.
Responsibility
- Own all
workers/*/directories — async worker processes - Ensure every worker declares idempotency, retry, checkpoint/replay, and recovery behavior
- Implement outbox polling, event delivery, projection building, replay, job scheduling, sync reconciliation
- Coordinate with service-agent when workers consume service-owned events or projections
- Own
verification/resilience/**,verification/topology/**, andverification/replay/**scenarios
Read Before Editing
AGENTS.md → global protocol
agent/codemap.yml → module constraints (workers layer)
.agents/skills/backend-engineering/SKILL.md → backend quality kernel
platform/model/README.md → platform vs service boundary
platform/model/workflows/** → workflow definitions
services/<name>/model.yaml → event, query, and ownership context
Individual worker Cargo.toml and README.md
Writable Directories
| Directory | Scope |
|---|---|
workers/** |
All worker source code |
verification/resilience/** |
Resilience tests |
verification/topology/** |
Topology validation tests |
verification/replay/** |
Replay and rebuild validation |
Forbidden Directories
| Directory | Reason |
|---|---|
packages/sdk/** |
Generated from contracts (read-only) |
infra/** |
Owned by platform-ops-agent |
servers/** |
Owned by server-agent |
services/*/domain/** |
Core domain logic owned by service-agent |
Gate Candidates
Select gates from agent/manifests/gate-matrix.yml based on changed paths, risk, and evidence level. Common worker signals include:
| Gate | Command |
|---|---|
| Worker build check | cargo check -p <worker-package> |
| Worker tests | cargo test -p <worker-package> |
| Replay verification | just verify-replay |
| Boundary check | just boundary-check |
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 6d ago First seen · 117 lines · 89 tokens per session scan A 6bc4feccef45
worker-agent is a skill published in the GitHub repository openclosed-org/axum-harness (49 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 89 tokens to every session and 894 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
architecture-paradigm-microservices
Applies microservices for independent deployment and per-service scaling. Use when teams need autonomous release cycles with distinct capability scaling needs.
microservices-expert
Expert-level microservices architecture, patterns, service mesh, and distributed systems. Use when the user mentions distributed systems, service mesh, or architecture, or when the task involves Microservices Principles, Architecture Patterns, Communication, or Data Management.
microservices-patterns
Generate and review microservices code using patterns from Chris Richardson's "Microservices Patterns." Use this skill whenever the user asks about microservices architecture, wants to generate service code, design distributed systems, review microservices code, implement sagas, set up CQRS, configure API gateways…
distributed-feasibility-checker
Evaluate whether a system should adopt distributed architecture by systematically checking against the 8 Fallacies of Distributed Computing and assessing team/operational readiness. Use this skill whenever the user is considering microservices, debating monolith vs distributed, hearing "let's use microservices,"…
Contract Testing with Pact
Consumer-driven contract testing skill using Pact, covering consumer tests, provider verification, Pact Broker integration, and CI/CD workflows.
architecture-paradigm-client-server
Applies client-server architecture for web/mobile apps. Use when designing systems with centralized backend services, trust boundaries, or offline-first sync.