A command-line tool for running UKB knowledge-base workflows and managing their ontology, which is the system used to organize types of entities and their relationships. It sends workflow runs to a local service so the dashboard can display their progress.

Running wave-analysis workflows, checking service health, listing available semantic tools, inspecting ontology classes, and refreshing outdated knowledge entities.

It provides one place to start, debug, inspect, and monitor knowledge-base analysis instead of running workflow code in a way the dashboard cannot see. Different commands distinguish real language-model runs from mock debugging runs.

How fwornle/coding configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to fwornle/coding. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/fwornle/coding/main/.claude/commands/semantic.md

Clone the repo

git clone --depth 1 https://github.com/fwornle/coding

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/fwornle/coding/semantic/github.svg)](https://agentmods.dev/commands/fwornle/coding/semantic)

Your own site

<a href="https://agentmods.dev/commands/fwornle/coding/semantic"><img src="https://agentmods.dev/badge/commands/fwornle/coding/semantic/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/fwornle/coding/semantic"><img src="https://agentmods.dev/badge/commands/fwornle/coding/semantic.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 76 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,224 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 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.

Model	Per session	Once invoked
Fable 5.1	$0.00076	$0.01224
Opus 5.5	$0.00030	$0.00490
Sonnet 5.5	$0.00015	$0.00245
Haiku 4.5	$0.00008	$0.00122

Measured 23d ago against content hash 98846996b34a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

semantic scanned grade A 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 23d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- **Service health:** `curl -s localhost:3848/health`

.claude/commands/semantic.md · 99 lines

How it starts

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

/semantic

The semantic CLI (bin/semantic) is the entry point to the semantic-analysis tools. It POSTs to /tool/<name> on the SSE server the coding-services container already runs at :3848.

That transport is deliberate, not incidental: execute_workflow dispatches into an in-process workflow state machine, and the broadcaster subscribed to it is what feeds the dashboard's /workflow-events view. Running the same handler in a one-shot process would start the workflow and leave the UI blind to it.

Dashboard: http://localhost:3032 → Performance → UKB
Service health: curl -s localhost:3848/health
Every available tool: semantic tools

🚨 UKB Workflow Control — match the flags to what the user actually said

User says	Mode	Command
"ukb", "full ukb", "ukb full"	PRODUCTION — real LLM calls, runs for 10–20 min	`semantic workflow run wave-analysis --team coding`
"ukb full debug", "ukb debug"	DEBUG — mock LLM, single-step, step-into-substeps	`semantic workflow run wave-analysis --team coding --debug`

NEVER default to debug unless the user explicitly said "debug".
NEVER run bare ukb as a shell command — that is the retired legacy script, not this CLI.
Long workflows are async by default: the command returns a workflow id and leaves the run going. Watch it on the dashboard or poll semantic workflow status. Do not wait on it.

Workflow names: wave-analysis (the UKB pass), batch-analysis, incremental-analysis, complete-analysis.

All four run inside obs-api (:12436), one at a time

km-core's LevelDB is single-owner and obs-api holds it, so the container hands every one of these to obs-api over HTTP (POST /api/workflows/<name>/run) instead of spawning a runner — a spawned child cannot open the store. Consequences worth knowing:

One run at a time, across all four. Asking for the workflow already running attaches to it; asking for a different one is refused with 409 and "Workflow NOT started: is running". That is the lock working, not a failure — wait, or cancel, then retry.
Cancel with the dashboard's Cancel button or curl -X POST localhost:12436/api/workflows/cancel. It is cooperative: the run stops at its next step boundary, which can take as long as the step in flight. GET /api/workflows/<name>/status → activeWorkflow says who still holds the lock.
obs-api down = "Workflow NOT started … Could not reach obs-api". There is deliberately no spawn fallback. launchctl kickstart -k gui/$(id -u)/com.coding.obs-api.
Restarting obs-api kills an in-flight run (the progress file then still says running).

Read the full file on GitHub · 99 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.

23d ago Changed · +16 lines 98846996b34a
1mo ago Changed 693f6e0f2599
1mo ago Changed 6dc3c218cf7c
1mo ago First seen · 83 lines · 76 tokens per session scan A c2090173f061

Subscribe to this mod's changes

semantic is a command published in the GitHub repository fwornle/coding (2 stars, last pushed today), licensed MIT. It adds 76 tokens to every session and 1,224 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Data and AI

coding: Command for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Makes network callslowCapability

How it starts

/semantic

🚨 UKB Workflow Control — match the flags to what the user actually said

All four run inside obs-api (:12436), one at a time

What this file has done since we first saw it

Other commands, from other repositories

boot

music-suno-prompt

audit-prompt

laravel-ai-sdk

vlm-ocr-evaluation

dare-llm-integration