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/harness-architecture-review/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/harness-architecture-review)<a href="https://agentmods.dev/skills/openclosed-org/axum-harness/harness-architecture-review"><img src="https://agentmods.dev/badge/skills/openclosed-org/axum-harness/harness-architecture-review/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/harness-architecture-review"><img src="https://agentmods.dev/badge/skills/openclosed-org/axum-harness/harness-architecture-review.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.00061 | $0.00376 |
| Opus 5 | $0.00030 | $0.00188 |
| Sonnet 5 | $0.00012 | $0.00075 |
| Haiku 4.5 | $0.00006 | $0.00038 |
Grade A, and why
harness-architecture-review 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 12d 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.
What it actually says
Harness Architecture Review
Use this skill to surface architecture friction before proposing refactors.
Workflow skills guide process. Ownership skills still decide writable boundaries.
Process
- Read
AGENTS.md,agent/codemap.yml,docs/architecture/north-star.md, and accepted ADRs in the area. - Explore code and tests before judging architecture.
- Identify where understanding requires bouncing across many shallow modules.
- Apply the deletion test to suspected pass-through modules.
- Check whether a seam has real variation, testing value, or topology-late value.
- Check ownership boundaries before recommending changes.
- Present candidates only. Do not edit first.
Candidate Format
For each candidate, report:
- files or owner areas involved
- problem and evidence
- why the current module or seam is shallow
- proposed deeper interface in plain English
- benefit in leverage, locality, and testability
- ADR or north-star conflict, if any
- risk and suggested verification
Ask which candidate to explore before designing interfaces or changing code.
Repository-Specific Rules
- A service library can be a semantic boundary without becoming a process boundary.
- A Rust trait is not automatically a useful seam.
- Platform metadata must not absorb service-local semantics.
- Server handlers adapt protocols; they do not own domain rules.
- Worker reliability claims require executable retry, checkpoint, dedupe, replay, and recovery evidence at the claimed level.
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.
- 12d ago First seen · 47 lines · 61 tokens per session scan A 3be196bf267f
harness-architecture-review is a skill published in the GitHub repository openclosed-org/axum-harness (49 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 61 tokens to every session and 376 once invoked, about $0.0003 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.
architecture-governance
Run Evolith architecture validation and report a coverage-honest verdict. Use when asked to validate architecture, check ADR compliance, run architecture or governance rules, check an SDLC phase gate, or answer "does this repo pass architecture review". Also before merging, releasing or promoting a phase. Reports…
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.