workflow-authoring

workflow-authoring is a skill for Claude Code from burin-labs/harn. It costs 73 tokens per session (3,257 once invoked), scanned B, original, Apache-2.0.

A guide for creating Harn workflow bundles: JSON files that describe event-driven engineering tasks such as monitoring pull requests, deployments, or logs. The bundles can be validated, previewed, and run locally or imported by supported hosts.

In plain words
What is it for?
Use it to author, validate, preview, and run Harn workflows, then provide the required commands and connector details for verification.
Why use it?
It gives a structured way to create portable workflows and catch invalid fields through a validation-and-retry process, including when using smaller language models.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions subagents.

Good fit Use it to author, validate, preview, and run Harn workflows, then provide the required commands and connector details for verification.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/burin-labs/harn/workflow-authoring
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.

Any agent
npx skills add burin-labs/harn --skill workflow-authoring
Clone the repo
git clone --depth 1 https://github.com/burin-labs/harn

Made for: Claude Code.

Wrote 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.

agentmods badge for workflow-authoring

README.md
[![agentmods](https://agentmods.dev/badge/skills/burin-labs/harn/workflow-authoring.svg)](https://agentmods.dev/skills/burin-labs/harn/workflow-authoring)
Your own site
<a href="https://agentmods.dev/skills/burin-labs/harn/workflow-authoring"><img src="https://agentmods.dev/badge/skills/burin-labs/harn/workflow-authoring.svg" alt="Measured on agentmods" height="20"></a>
Per session 73 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,257 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00073 $0.03257
Opus 5 $0.00036 $0.01629
Sonnet 5 $0.00015 $0.00651
Haiku 4.5 $0.00007 $0.00326

Measured 8d ago against content hash c88df1f0958c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade B, and why

workflow-authoring scanned grade B with 1 finding 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 8d 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.

Unrestricted tool accessmediumExcessive agency

A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.

- "Bash(harn workflow function-tools:*)"
examples/skill-packs/workflow-authoring/SKILL.md · 283 lines

How it starts

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

Workflow authoring (Harn workflow bundles)

You are authoring a portable workflow bundle — a JSON file Harn validates, previews, and runs locally. Hosts (IDE TUI/GUI, cloud-platform importers) consume the same bundle without rewriting.

Read prompting.md in this directory before composing a response. It defines the response sections, JSON envelope, and small-model rules. Every recipe under recipes/ is a worked, validated example you can crib from.

What good output looks like

  1. A single <bundle> block containing valid JSON for a WorkflowBundle.

  2. A short <rationale> block (≤ 5 bullets) explaining the trigger, the waitpoints, and the connector requirements.

  3. A <verify> block listing the exact commands the user should run:

    harn workflow validate --bundle out.bundle.json --json
    harn workflow preview  --bundle out.bundle.json --json
    harn workflow run      --bundle out.bundle.json --json
    

If validation fails, read the diagnostic, edit the bundle, and re-validate. Do not invent fields or kinds — the validator's enum lists are the source of truth.

Bundle skeleton

{
  "schema_version": 2,
  "entrypoint": "workflows/<kebab-case-id>.harn",
  "transitive_modules": [
    {
      "path": "workflows/<kebab-case-id>.harn",
      "source_hash_blake3": "blake3:<64 lowercase hex digits>",
      "harnbc_hash_blake3": "blake3:<64 lowercase hex digits>"
    }
  ],
  "stdlib_version": "<harn stdlib version>",
  "harn_version": "<harn version>",
  "provider_catalog_hash": "blake3:<64 lowercase hex digits>",
  "tool_manifest": [],
  "sbom": {
    "format": "spdx-lite",
    "version": "2.3",
    "packages": [],
    "relationships": []
  },
  "signature": null,
  "parent_trust_record_id": null,
  "id": "<kebab-case-id>",
  "name": "<human label>",
  "version": "1.0.0",
  "triggers": [
    { "id": "<trigger-id>", "kind": "github|cron|delay|webhook|mcp|manual",
      "provider": "github", "events": ["pull_request.opened"],
      "node_id": "<entry-node-id>" }
  ],
  "workflow": {
    "_type": "workflow_graph",
    "id": "<graph-id>",
    "version": 1,
    "entry": "<entry-node-id>",
    "nodes": {
      "<node-id>": { "id": "<node-id>", "kind": "action|waitpoint|notification",
                     "task_label": "<short label>" }
    },
    "edges": [ { "from": "<from-node-id>", "to": "<to-node-id>" } ]
  },
  "prompt_capsules": {
    "<capsule-id>": { "id": "<capsule-id>", "node_id": "<node-id>",
                      "trigger_id": "<trigger-id>",
                      "prompt": "<self-contained continuation prompt>" }
  },
  "policy": {
    "autonomy_tier": "shadow|suggest|act_with_approval|act_auto",
    "retry":   { "max_attempts": 2, "backoff": "exponential" },
    "catchup": { "mode": "none|latest|all", "max_events": 1 }
  },
  "connectors": [
    { "id": "github", "provider_id": "github",
      "scopes": ["pull_requests:read", "checks:read"],
      "setup_required": true, "status_required": true }
  ],
  "environment": {
    "repo_setup_profile": "default",
    "worktree_policy": "reuse_current|new_worktree|host_managed",
    "command_gates": ["make test"]
  }
}

Read the full file on GitHub · 283 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. 8d ago First seen · 283 lines · 73 tokens per session scan B c88df1f0958c

Subscribe to this mod's changes

workflow-authoring is a skill published in the GitHub repository burin-labs/harn (20 stars, last pushed today), licensed Apache-2.0. It adds 73 tokens to every session and 3,257 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.