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 Ancienttwo/repo-harness --skill repo-harness-archimapgit clone --depth 1 https://github.com/Ancienttwo/repo-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/ancienttwo/repo-harness/repo-harness-archimap)<a href="https://agentmods.dev/skills/ancienttwo/repo-harness/repo-harness-archimap"><img src="https://agentmods.dev/badge/skills/ancienttwo/repo-harness/repo-harness-archimap/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/ancienttwo/repo-harness/repo-harness-archimap"><img src="https://agentmods.dev/badge/skills/ancienttwo/repo-harness/repo-harness-archimap.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.00080 | $0.01683 |
| Opus 5.5 | $0.00032 | $0.00673 |
| Sonnet 5.5 | $0.00016 | $0.00337 |
| Haiku 4.5 | $0.00008 | $0.00168 |
Grade A, and why
repo-harness-archimap 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 2d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
repo-harness-archimap
Worker entrypoint. The archimap is the project's architecture map for people and for the
orchestrator agent. It is one static HTML file,
docs/architecture/archimap.html, made of fixed-size boards: the layered
overview, the measured dependency directions, the runtime topology, the
key sequences and the remarks. The orchestrator of
repo-harness-issue-flow splits work by its modules. Workers cite its
module IDs. A stale map therefore sends issues to the wrong boundaries.
What the map is a projection of
| Content | Authority | The map does |
|---|---|---|
| Modules, layers, responsibilities, relations, flows | Architecture model: .archcontext/model/ (nodes, relations, flows). A repository without an adopted model is adopted first (repo-harness-architecture, "Adopt ArchContext in a repository") |
Groups model nodes into map modules and draws them |
| Size and import direction | Code, measured by scripts/measure.ts |
Shows LOC and value-import counts |
| Observations and risks | The author's review, with file:line evidence | Lists them on the Remarks board |
The map never adds a module, relation or flow that the model does not
have. It does not group by package or directory layout: that layout is not
a model. If the model is wrong, fix the model first: use
repo-harness-architecture for an archctx model. Then refresh the map.
Mermaid diagrams that archctx generates stay as they are. They serve the
model's own docs. The archimap is the one hand-composed HTML view.
Modes
- Draw. No map exists, or the user asks for a redraw. Do every step.
- Refresh. A map exists. An
[Archimap]notice fired, or the model, the module layout or a public API changed. Change only the affected boards. Keep unchanged nodes at the same coordinates, so that a reviewer can compare the two versions by eye. When a new node needs room, move the fewest nodes, and name each moved node in the report.
Steps
- Read the model. List the model's nodes (id, kind, layer, summary,
source.include, entrypoints), its relations and its flows. For archctx, read the YAML under.archcontext/model/directly. In a refresh, read the meta block of the current map and rungit diff <meta.base>..HEAD --stat -- .archcontext/modelto find what moved. - Group into map modules. The overview holds at most 20 modules. A
small model gets one module per node. A larger model is grouped by
domain or layer. Each map module lists the
model node IDs it covers (
nodes) and the path globs it owns (include,exclude). The grouping is part of the map. It is stored in the meta block, so that a refresh reuses it. Change it only on purpose. - Measure. From the repository root, run:
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago Changed · +13 lines 954fb48c7c7c
- 3d ago First seen · 109 lines · 80 tokens per session scan A 6b347110048f
repo-harness-archimap is a skill published in the GitHub repository Ancienttwo/repo-harness (435 stars, last pushed today), licensed MIT. It adds 80 tokens to every session and 1,683 once invoked, about $0.0003 per session on Opus 5.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-10-31.
Other skills, from other repositories
agenticx-query-data-source
Use when the user asks about verifiable quantitative facts (stock prices, financial indicators, macro data, company registry, academic metrics, legal statutes) that must come from a live data source rather than training memory.
create-modal
Create declarative modals using the modal library API. Covers modal types (confirm, input, select, form), sections (Text, Buttons, Input, Textarea, Checkbox, Select, List, Combo, When, Custom), rendering with OverlayModal, and keyboard/mouse handling. Use when adding modals or dialogs to the application.
merge-strategy
Git merge strategies, conflict resolution approaches, merge vs rebase recommendations, and branch integration patterns in sidecar. Covers pull strategy menu, direct merge workflow, squash merge, commit message templates, configurable defaults, and protected branches. Use when working on git merge features or making…
openlore-brainstorm
Transform a feature idea into an annotated story using a Domain Sketch or Constrained Option Tree. Use when asked to brainstorm, explore, or shape a feature before implementation.
gemigo-cli
Use when the user wants to publish an already-built static website or front-end app through GemiGo, such as a Vite/React/Vue static build, plain HTML/CSS/JS page, landing page, demo, docs site, or small browser app, and get a hosted public URL.
clawhub-nextclaw
Use when the user wants to search external ClawHub skills or install a ClawHub skill into a NextClaw workspace's skills directory without treating ClawHub as the NextClaw marketplace.