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 skills/outlinedriven/odin-claude-plugin/make-bot-uinpx skills add OutlineDriven/odin-claude-plugin --skill make-bot-uigit clone --depth 1 https://github.com/OutlineDriven/odin-claude-pluginWrote 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.
[](https://agentmods.dev/skills/outlinedriven/odin-claude-plugin/make-bot-ui)<a href="https://agentmods.dev/skills/outlinedriven/odin-claude-plugin/make-bot-ui"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-claude-plugin/make-bot-ui.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00059 | $0.01262 |
| Opus 5 | $0.00030 | $0.00631 |
| Sonnet 5 | $0.00012 | $0.00252 |
| Haiku 4.5 | $0.00006 | $0.00126 |
Grade A, and why
make-bot-ui 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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Make bot UI
Contract
| Field | Bound contract |
|---|---|
| Trigger | A human explicitly invokes this skill to build a webhook UI that wakes a bot. |
| Authority | Require explicit human invocation, then preview the exact files, server endpoint, credential storage, network exposure, and any host-level Tailscale installation before changing them. Do not perform an unpreviewed credential, data-at-rest, deployment, remote, paid, or irreversible action. |
| Side effect | Create or modify only the previewed webhook server and browser UI; optionally install and configure Tailscale node support only when the human explicitly requests that installation after seeing its host and network consequences. |
| Done | The UI is working and has been exercised through the real server-to-webhook path, the bot wake request succeeds, and neither browser-delivered code nor browser-visible traffic contains the webhook secret. |
Inputs
Required: the target project and run command; the bot webhook URL and its required request contract; the secret's approved server-side source, supplied without placing its value in browser code or chat output; and the UI action and fields that should wake the bot.
Optional: an existing server route to extend, UI constraints, the local or remote probe target, and a request to expose the server through Tailscale. A Tailscale request must identify the host and intended audience; installation or host configuration requires a separate preview of the exact host-level and network changes before execution.
Procedure
- Inspect the named project and identify its existing server, routing, configuration, and UI conventions. Bound the change to the files, endpoint, credential location, and network exposure needed for the requested wake action. Done when: the change boundary is stated and no out-of-scope file is queued.
- Present the bounded change set and consequences before mutation. Include every credential or data-at-rest change and, when requested, the exact Tailscale package, host, service, listener, and exposure change. Stop unless the human's explicit invocation covers the previewed external or irreversible work. Done when: the human confirms the preview or the run stops without mutation.
- Validate the webhook URL, required method, headers, payload fields, and expected success response at the server trust boundary. Validate and constrain every browser-supplied field before using it in the outbound request. Do not infer missing webhook semantics or secret values. Done when: every webhook contract field is validated or the run stops naming the missing field.
- Read the webhook secret only in server-side code from the approved server environment or credential store. Keep the secret out of HTML, browser JavaScript, serialized page state, URLs, logs, errors, and server responses. Make the server construct and authenticate the outbound webhook request. Done when: the secret is confined to server-side code and no browser-visible surface can contain it.
- Implement the smallest server route and UI needed for the wake action. The browser sends only validated non-secret inputs to the server; the server invokes the bot webhook and returns a bounded success or failure result that does not echo credentials or sensitive upstream content. Done when: the server route and UI exist and the browser sends only non-secret inputs.
- If Tailscale exposure was explicitly requested and approved after preview, install or configure only the named node support and expose only the approved listener to the approved audience. Otherwise, leave host packages and network configuration unchanged. Done when: the Tailscale configuration matches the approved preview or host state is unchanged.
- Launch the actual server and UI. Exercise the UI through the real browser-to-server-to-webhook path with an approved safe probe, and record the observed response and bot wake result. Inspect the browser-delivered assets, page state, URL, and browser-visible request and response data for the secret; treat any occurrence as failure and remove it before probing again. Done when: the end-to-end probe succeeds and the browser-side secret inspection is clean.
- Compare the observed state with the done predicate. Report success only when the wake request works and the browser-side secret inspection is clean; do not widen scope or invent probe evidence to obtain a passing result. Done when: the done predicate is confirmed or the failing observation is reported.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 46 lines · 59 tokens per session scan A b446b10dbe13
make-bot-ui is a skill published in the GitHub repository OutlineDriven/odin-claude-plugin (35 stars, last pushed today), licensed Apache-2.0. It adds 59 tokens to every session and 1,262 once invoked, about $0.0003 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-09-04.
Other skills, from other repositories
java-clean-arch
Reviews or implements Clean Architecture / Hexagonal Architecture (Ports & Adapters) and DDD tactical patterns for Java projects. Use when user asks to "apply clean architecture", "implement hexagonal architecture", "add ports and adapters", "apply DDD", "refactor to clean arch", "review architecture", or "add value…
java-adr
Creates, lists, and manages Architecture Decision Records for Java projects. Use when user asks to "create an ADR", "document this decision", "write an architecture decision", "add ADR", "list decisions", "show ADRs", or "record this architectural choice".
java-test
Generates JUnit 5 and Mockito unit tests or Testcontainers integration tests, auto-detecting project setup. Use when user asks to "write tests", "generate tests", "add unit tests", "create test class", "test this service", or "write integration tests".
java-jpa
Reviews Spring Data JPA for N+1 queries, fetch strategies, projections, and Specifications. Use when user asks to "review JPA", "check for N+1", "JPA performance", "review my entities", "check fetch strategy", or "review my repositories".
java-logging
Reviews Java logging for SLF4J best practices, MDC context, structured logging, and PII safety. Use when user asks to "review logging", "check my logs", "logging review", "is my logging correct", "MDC setup", or "check for PII in logs".
java-security
Reviews or implements Spring Security configuration — JWT authentication, OAuth2, method-level security, CORS, and CSRF. Use when user asks to "add authentication", "secure this API", "implement JWT", "configure Spring Security", "add OAuth2 login", "protect endpoints", or "review security config".