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 skills add akka/ai-marketplace --skill harnessesgit clone --depth 1 https://github.com/akka/ai-marketplaceWrote 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/akka/ai-marketplace/harnesses)<a href="https://agentmods.dev/skills/akka/ai-marketplace/harnesses"><img src="https://agentmods.dev/badge/skills/akka/ai-marketplace/harnesses/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/akka/ai-marketplace/harnesses"><img src="https://agentmods.dev/badge/skills/akka/ai-marketplace/harnesses.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.00048 | $0.02037 |
| Opus 5 | $0.00024 | $0.01019 |
| Sonnet 5 | $0.00010 | $0.00407 |
| Haiku 4.5 | $0.00005 | $0.00204 |
Grade A, and why
harnesses 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.
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.
User Input
You MUST consider the user input before proceeding (if not empty).
Purpose
/akka:harnesses is a generator. It writes the enterprise-configuration assets a
project needs — CI workflows, scanner configs, supply-chain steps, content style
packages — into /harnesses/<surface>/, records what it generated in
.akka/harnesses.lock, and surfaces each asset for approval. The engine does not
generate anything and does not call a model: generation lives here in the
assistant; the engine detects surfaces, verifies the generated assets
deterministically, and records attestations you submit. This command is paired
with the harness exit-condition family (activated / configured / attested), the
same way /akka:specify is paired with the functional and data-integrity family.
The three auditor kinds
Every required surface resolves as one of three kinds. Which one it is decides whether you generate an asset and how the engine verifies it.
| Kind | Where the check runs | Asset generated | How it resolves |
|---|---|---|---|
| Introspective | the project's own tree (a compiler, test runner, linter, prose linter over docs/) |
none | verified locally — green or red |
| Provisioned | a generated asset (a CI workflow, scanner config, IaC module, style package) wired to an external system | yes — one per surface under /harnesses/<surface>/ |
verified where inspectable — present, correct, and enforcing — otherwise open with the tool or environment gap named |
| Delegated | a check that runs only in an external system, or needs a judgment the engine cannot make | a config stub, optional | resolved by an attestation you submit; otherwise stays open with needs-user-action until the receipt is recorded |
Outline
- Detect the required surfaces. Read the policy's
required_surfaces(the enterprise-mandated set: SAST, secret scanning, SBOM, signing, identity, and so on). Detect the project's own surfaces from tree markers (a GitHub directory,pom.xml,package.json,go.mod). The gap is the set of required surfaces with no covering harness. Introspective surfaces (a coverage gate a local tool already runs) need no asset — note them and move on.
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 · 132 lines · 48 tokens per session scan A dac54615510c
harnesses is a skill published in the GitHub repository akka/ai-marketplace (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 48 tokens to every session and 2,037 once invoked, about $0.0002 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-31.
Other skills, from other repositories
github-workflows
Work with GitHub Actions CI/CD workflows - read live syntax, monitor runs, and debug failures. Use when writing, running, or debugging GitHub Actions workflows.
aif-ci
Generate CI/CD pipeline (GitHub Actions / GitLab CI) with linting, static analysis, tests, security. Use when user says "ci", "setup ci", "github actions", "gitlab ci", "pipeline".
shipping-and-launch
Pre-deploy hygiene for a Spring Boot 4 feature — verify gates, capture rollback plan, sign off observability, generate release notes, and stage the rollout. Used by /ship after /review approves the diff. The agent never deploys; it produces the plan a human executes.
setup-repo
Bootstrap the GitHub repo for a forge project — repo creation, branch protection, GitHub Environments, CI workflows, secrets configuration.
post-deploy-verifier
Senior reliability engineer producing a per-slice post-deploy verification plan mapping each acceptance criterion to a concrete live signal (exact log query, dashboard panel, smoke-test walkthrough, flag check, DB invariant query) plus negative checks and rollback trigger checklist. Activates when TASKSTATE.md ##…
devops
Provides comprehensive DevOps guidance including CI/CD pipeline design, infrastructure as code (Terraform, CloudFormation, Bicep), container orchestration (Docker, Kubernetes), deployment strategies (blue-green, canary, rolling), monitoring and observability, configuration management (Ansible, Chef, Puppet), and cloud…