Create a starter structure for a custom AI agent harness, the setup that supports agent execution. Choose a template and host, preview the plan, then explicitly confirm generation in a new directory outside the current project.
Scaffold a custom AI agent harness via `metaharness new {name} --template {id} --host {id}`. Defaults to DRY-RUN (no writes) unless --confirm is passed. Refuses to write to the calling repo root or anywhere inside it. Honors ADR-150 architectural constraint + ruflo's "destructive-action confirmation" pattern.
Review the instructions the agent will receive before you install.
The one write-capable skill in the plugin. Every other skill is
pure-read. This one calls metaharness new, which writes a new
directory tree.
--confirm, the script prints what
it would do and exits 0 without touching disk.--target resolves to the current
working directory OR any path inside it, the script errors out with
exit 2. Target must be an absolute path OUTSIDE the calling repo
(default is a fresh /tmp/ruflo-mint-<ts>-<name>/ dir).Implementation: scripts/mint.mjs.
--name, --template. Default --host to claude-code.--target (default: temp dir).--confirm: emit dry-run plan, exit 0.--confirm: shell npx metaharness new <name> --template <id> --host <id> --target <abs> --yes.minimal, vertical:coding, vertical:devops, vertical:support,
vertical:legal, vertical:research, vertical:trading, vertical:health,
vertical:education, vertical:sales, vertical:business,
vertical:crm, vertical:marketing, vertical:advertising,
vertical:ai, vertical:agentics, vertical:ruview, vertical:gaming,
vertical:repo-maintainer, vertical:exotic.
claude-code, codex, pi-dev, hermes, openclaw, rvm,
copilot, opencode, github-actions.
$ node scripts/mint.mjs --name my-harness --template vertical:coding --host claude-code
# harness-mint (dry-run)
- action: metaharness new
- name: my-harness
- template: vertical:coding
- host: claude-code
- target: /tmp/ruflo-mint-1718560000-my-harness
- confirm: false
- willWrite: false
Re-run with `--confirm` to actually scaffold.
Ruflo's behavioral rules say "executing actions with care" — destructive
or repo-touching actions need confirmation. The dry-run output makes the
WHAT visible before the WHEN. A human sees target, decides, then
adds --confirm if happy.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Compare models available through the HuggingFace router with chat-ui configuration, research missing models, and write short English descriptions of their architecture and capabilities. Add entries to both production and development configuration files and commit the changes.
Create an Architecture Decision Record, a document for recording important design choices, with the next sequential number. It generates a Markdown template, registers the record in AgentDB, and links related decisions found through search.
Build a searchable index and relationship graph from ADRs, records of architectural decisions. Import two supported document formats, refresh existing metadata without duplicate relationships, and review summaries of statuses, missing references, and inconsistencies.
Rebuild the index of ADRs, records of architectural decisions, after files or relationship lines are deleted. It clears stored records and relationships, indexes the files still present, and checks that the final record count matches.
Review code changes against accepted Architecture Decision Records, documents that capture agreed design choices. Report violations, outdated references, compliant changes, and areas without ADR coverage, then suggest code fixes or a new decision record where appropriate.
Check saved architecture decision records (ADRs) for broken references, circular replacement relationships, and inconsistent statuses. Use the results to verify imported records or stop a CI check when selected integrity rules fail.