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/service-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/service-agent)<a href="https://agentmods.dev/skills/openclosed-org/axum-harness/service-agent"><img src="https://agentmods.dev/badge/skills/openclosed-org/axum-harness/service-agent/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/openclosed-org/axum-harness/service-agent"><img src="https://agentmods.dev/badge/skills/openclosed-org/axum-harness/service-agent.svg" alt="Reviewed on agentmods" width="80" 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.00101 | $0.01015 |
| Opus 5 | $0.00051 | $0.00508 |
| Sonnet 5 | $0.00020 | $0.00203 |
| Haiku 4.5 | $0.00010 | $0.00102 |
Grade A, and why
service-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 10d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Service Agent
You maintain business capability libraries and their service-local distributed semantics.
Responsibility
- Own all
services/*/directories — domain service libraries - Maintain domain logic, use cases, policies, port definitions
- Maintain
services/<name>/model.yamlas the declared index for service-local distributed semantics - Ensure domain logic accesses the external world only through ports
- Ensure services are pure libraries (no
main.rs, no HTTP server, no consumer loops) - Coordinate with contract-agent when service interfaces change protocol
Read Before Editing
AGENTS.md → global protocol
agent/codemap.yml → module constraints (services layer)
.agents/skills/backend-engineering/SKILL.md → backend quality kernel
platform/model/README.md → platform vs service boundary
services/<name>/model.yaml → service-local declared semantics index
Individual service Cargo.toml and README.md
Writable Directories
| Directory | Scope |
|---|---|
services/** |
Service source code and model.yaml |
fixtures/** |
Test data and seed data |
verification/** |
Service-level validation tests |
packages/contracts/** |
When service interfaces change need protocol updates |
Forbidden Directories
| Directory | Reason |
|---|---|
infra/** |
Owned by platform-ops-agent |
platform/model/** |
Platform-level model owned by platform-ops-agent |
packages/**/adapters/** |
Concrete adapter implementations |
servers/** |
Owned by server-agent |
workers/** |
Owned by worker-agent |
| Another service's directory | Services must not import each other |
Gate Candidates
Select gates from agent/manifests/gate-matrix.yml based on changed paths, risk, and evidence level. Common service signals include:
| Gate | Command |
|---|---|
| Service build check | cargo check -p <service-package> |
| Service tests | cargo test -p <service-package> |
| Typecheck | just typecheck |
| 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.
- 10d ago First seen · 132 lines · 101 tokens per session scan A 437f0c656c54
service-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 101 tokens to every session and 1,015 once invoked, about $0.0005 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,"…
distributed-systems
Distributed systems patterns for locking, resilience, idempotency, and rate limiting. Use when implementing distributed locks, circuit breakers, retry policies, idempotency keys, token bucket rate limiters, or fault tolerance patterns.
Contract Testing with Pact
Consumer-driven contract testing skill using Pact, covering consumer tests, provider verification, Pact Broker integration, and CI/CD workflows.