harmont-cli CLAUDE.md

A set of development instructions for Harmont CLI, a Rust command-line tool organized as a Cargo workspace, which is a project containing several related Rust packages.

In plain words
What is it for?
It guides Rust builds and tests, changes across the CLI's packages, event-stream output, configuration, execution backends, and plugin protocol.
Why use it?
It reduces confusion about where shared code belongs and helps keep the CLI, software development kit, templates, and documentation consistent.

Instructions file

Install

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.

agentmods
npx agentmods add instructions/harmont-dev/harmont-cli/claude-md
Clone the repo
git clone --depth 1 https://github.com/harmont-dev/harmont-cli
Per session 980 This file is loaded in full into every session.
When invoked 980 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00980 $0.00980
Opus 5 $0.00490 $0.00490
Sonnet 5 $0.00196 $0.00196
Haiku 4.5 $0.00098 $0.00098

Measured 2d ago against content hash b0a1f7242ee9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

harmont-cli CLAUDE.md 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.

CLAUDE.md · 60 lines

How it starts

The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.

The cli/ directory is a Cargo workspace.

  • crates/hm/ — the hm binary (today's CLI body).
  • crates/hm-core/ — the shared core: config (layered project/user/env config + credential storage), exec (the ExecutionBackend trait + LocalBackend in-process Docker DAG scheduler + CloudBackend submit+watch over the SDK), and sys_runtime (the process-wide git/python/dirs/cwd runtime). The hm binary renders the emitted BuildEvent stream (via hm-render) and owns Ctrl-C; auth is injected (the backends take a built HarmontClient).
  • crates/hm-render/drive_stream: consumes an EventStream and writes terminal/JSON output. No I/O beyond stdout.
  • crates/hm-pipeline-ir/ — pipeline IR schema (serde structs only, no runtime).
  • crates/hm-common/ — shared utilities (OS/filesystem, formatting, and other cross-crate helpers). This is the source of truth for common code; prefer adding shared helpers here.
  • crates/hm-plugin-protocol/ — wire types (serde structs only). Run cargo build from the workspace root.

For cross-cutting doctrine see PRINCIPLES.md.

Testing

When writing or running any Rust test, follow the writing-rust-tests skill: #[rstest] over bare #[test], parametrized #[case] over duplicated test functions and hand-rolled loops, proptest for domain-wide properties. Run with plain cargo test -p <crate> (no nextest/just wrapper).

Documentation

When writing or editing any docblock, doc comment, or module header (///, //!) — including on code you just changed — follow the writing-interface-docblocks skill: a docblock is a contract, not a changelog. Terse, present-tense, no prompt or diff leakage (rather than, now returns, as requested); document the when of errors/panics, not the why; module docs name the domain, not the one item currently inside them.

DSL

The harmont Python package (pipeline DSL) lives inside crates/hm-dsl-engine/harmont-py/ so it ships with the crate.

Read the full file on GitHub · 60 lines

Changes

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.

  1. 2d ago First seen · 60 lines · 980 tokens per session scan A b0a1f7242ee9

Subscribe to this mod's changes

harmont-cli CLAUDE.md is an instructions file published in the GitHub repository harmont-dev/harmont-cli (21 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 980 tokens to every session, about $0.0049 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.