Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/openclosed-org/axum-harness/server-agentnpx skills add openclosed-org/axum-harness --skill server-agentgit 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/server-agent)<a href="https://agentmods.dev/skills/openclosed-org/axum-harness/server-agent"><img src="https://agentmods.dev/badge/skills/openclosed-org/axum-harness/server-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 | $0.00081 | $0.00680 |
| Opus 5 | $0.00041 | $0.00340 |
| Sonnet 5 | $0.00016 | $0.00136 |
| Haiku 4.5 | $0.00008 | $0.00068 |
Grade A, and why
server-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 5d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Server Agent
You maintain server entrypoints — HTTP handlers, routes, middleware, and API composition.
Responsibility
- Own
servers/bff/web-bff/**— Web Backend-for-Frontend - Own
servers/gateway/**— Edge gateway - Own
servers/internal-rpc/**— Internal RPC server - Handle request/response adaptation, authn/z integration, API composition
- Keep domain rules in
services/**, not in servers
Read Before Editing
AGENTS.md → global protocol
agent/codemap.yml → module constraints (servers layer)
.agents/skills/backend-engineering/SKILL.md → backend quality kernel
services/<name>/model.yaml → service commands / queries / consistency expectations
packages/contracts/** → shared protocol definitions
Writable Directories
| Directory | Scope |
|---|---|
servers/bff/web-bff/** |
Web BFF handlers, routes, middleware |
servers/gateway/** |
Gateway configuration, routes |
servers/internal-rpc/** |
Internal RPC definitions |
packages/contracts/** |
When protocol changes are needed |
Forbidden Directories
| Directory | Reason |
|---|---|
services/*/domain/** |
Core domain logic owned by service-agent |
infra/** |
Owned by platform-ops-agent |
workers/** |
Owned by worker-agent |
packages/**/adapters/** |
Concrete adapter implementations |
Gate Candidates
Select gates from agent/manifests/gate-matrix.yml based on changed paths, risk, and evidence level. Common server signals include:
| Gate | Command |
|---|---|
| Server build check | cargo check -p <server-package> |
| Typecheck | just typecheck |
| Boundary check | just boundary-check |
Hard Rules
Workflow skills, including backend-engineering, may guide process; this skill's ownership boundaries still apply.
- Servers may import
services/**andpackages/** - Server handlers must align with
packages/contracts/** - Protocol changes: update contracts first, then handlers
- Servers must NOT implement domain logic
- Servers must NOT implement long transactions — those belong in workflow models
- Servers must respect service-declared consistency expectations when exposing query endpoints
- Servers must NOT import
infra/**
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.
- 5d ago First seen · 94 lines · 81 tokens per session scan A 6bab192b7bfe
server-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 81 tokens to every session and 680 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,"…
docker-local-build
Build and test Kurtosis from source on local Docker. Compiles all components (engine, core, files-artifacts-expander), builds Docker images, installs the CLI, and restarts the engine. Use when developing Kurtosis and testing changes locally with Docker.
starlark-dev
Develop and debug Kurtosis Starlark packages. Create packages from scratch, understand the plan-based execution model, use print() debugging, handle future references, and test packages locally. Use when writing or troubleshooting .star files.