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 larsboes/Axon --skill harness-syncgit clone --depth 1 https://github.com/larsboes/AxonWrote 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/larsboes/axon/harness-sync)<a href="https://agentmods.dev/skills/larsboes/axon/harness-sync"><img src="https://agentmods.dev/badge/skills/larsboes/axon/harness-sync/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/larsboes/axon/harness-sync"><img src="https://agentmods.dev/badge/skills/larsboes/axon/harness-sync.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.00182 | $0.01419 |
| Opus 5 | $0.00091 | $0.00709 |
| Sonnet 5 | $0.00036 | $0.00284 |
| Haiku 4.5 | $0.00018 | $0.00142 |
Grade A, and why
harness-sync 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 7d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
harness-sync
Axon is the source. Every harness holds a copy or a pointer, and the two drift.
One tool answers all of it: tools/harnesses in the Axon repository. This skill is the judgment
around it — which direction a change should travel, and when the answer is not sync.
The direction rule
Axon Packs ──(sync, routine, one-way, overwrites)──▶ harness
Axon Packs ◀──(promote / accept, manual, human decides)── harness
Sync is the normal move and it is destructive at the destination by design. The reverse moves are manual because an edit made inside a harness is a decision, and a tool that guessed would either lose good work or import junk into the source of truth.
| Situation | Move |
|---|---|
| The Pack changed; the harness is behind | sync |
| A deployed copy was edited in place and the edit is worth keeping | accept |
| A deployed copy was edited in place and the edit is not worth keeping | sync (discards it) |
| A skill exists in a harness, no Pack owns it, and it should be shared | promote |
| A skill exists in a harness and belongs to that harness alone | leave it; it shows as unowned every run, which is the honest state |
Procedure
- [ ] 1. Ask which harnesses are installed
- [ ] 2. Read the matrix
- [ ] 3. Resolve drift before deploying anything
- [ ] 4. Move in one direction at a time
- [ ] 5. Re-read the matrix
1 — Installed, not merely supported. tools/harnesses list. A harness with an adapter is not a
harness on this machine, and deploying to an absent one leaves skills in a directory nothing reads.
Every verb defaults to installed harnesses only; --all-harnesses overrides it and needs a reason.
2 — Read the matrix. tools/harnesses status [<pack>]. One row per Pack skill, one column per
harness: · current, o outdated, D drifted, M missing, blank not deployed. Under it, each
harness lists what sits at its destination that no Pack owns:
| Kind | What it means | What to do |
|---|---|---|
copy |
An ordinary directory nobody claims | A promote candidate. Read it first. |
external |
Carries .git, .graphify_version or similar |
Never promote. Another installer owns it and re-syncs from its own remote; a copy in Axon is a fork that will silently pin it. Record it in upstreams.toml instead. |
symlink |
Points into a product install | Never promote. The target is the install; an upgrade updates it. |
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.
- 7d ago First seen · 97 lines · 182 tokens per session scan A 9379ba001c7c
harness-sync is a skill published in the GitHub repository larsboes/Axon (1 stars, last pushed yesterday), licensed MIT. It adds 182 tokens to every session and 1,419 once invoked, about $0.0009 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-09-08.
Other skills, from other repositories
od-contribute
One-click contribution flow for OpenDesign (nexu-io/open-design) — even for non-coders. Pick one of four cards (ship a Skill or Design System you made with OD; translate docs; fix a typo / write a blog; report a bug), the agent validates and opens a PR (or issue) for you. Trigger words contribute to open design, ship…
orbit-github
Open Orbit briefing skill — selected by the Orbit pipeline when GitHub is the user's only connected connector, or when the user explicitly scopes their daily digest to GitHub. Pulls the past 24 hours of PRs, review requests, issues, CI runs, and merges from the user's authenticated GitHub connection and renders them…
diff-review
Render the patch-edit run's accumulated changes as a reviewable diff, surface it through a GenUI choice surface, and persist the user's accept / reject decision into the artifact manifest.
od-plugin-contribute-open-design
Open a pull request adding a local OpenDesign plugin to the OpenDesign community catalog using gh CLI.
od-plugin-publish-github
Publish a local OpenDesign plugin to a new public GitHub repository using gh CLI.
usecase-dev-task-queue
Create and run an agent-ready development queue from issues/PRs with progress checkpoints.