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 agentmods add commands/fwornle/coding/semanticgit clone --depth 1 https://github.com/fwornle/codingWhat 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 | $0.00076 | $0.00945 |
| Opus 5 | $0.00038 | $0.00473 |
| Sonnet 5 | $0.00015 | $0.00189 |
| Haiku 4.5 | $0.00008 | $0.00094 |
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 yesterday.
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` How it starts
The opening of the file, as written. The whole thing — 83 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
ukbas 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.
Commands
semantic workflow run wave-analysis --team coding # production UKB pass
semantic workflow run wave-analysis --team coding --debug # mock LLM + single-step
semantic workflow run batch-analysis --param fullAnalysis=true
semantic workflow status # progress of the current run
semantic ontology status --team coding # config, paths, validation mode, registered teams
semantic ontology classes --team coding # available entity classes
semantic ontology suggest --team coding # propose new classes from unclassified entities
semantic ontology inject --team coding # hot-swap an ontology config
semantic refresh KnowledgePersistencePattern --team coding
semantic refresh '*' --team coding --dry-run # preview a batch refresh
semantic refresh '*' --team coding --parallel 8
semantic checkpoint reset --days-ago 7 # re-analyse from N days back
semantic insights notes.md --type architecture
semantic analyze code src/foo.ts --focus security
semantic analyze repo /Users/Q284340/Agentic/coding --max-files 200
semantic tools # names + descriptions of all 19 tools
semantic tool <name> '{"key":"value"}' # generic escape hatch for anything unmapped
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.
- yesterday First seen · 83 lines · 76 tokens per session scan A c2090173f061
semantic is a command published in the GitHub repository fwornle/coding (2 stars, last pushed yesterday), licensed MIT. It adds 76 tokens to every session and 945 once invoked, about $0.0004 per session on Opus 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.