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/ch-bas/kibana-plugin-helper/ui-actiongit clone --depth 1 https://github.com/ch-bas/kibana-plugin-helperWrote 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/commands/ch-bas/kibana-plugin-helper/ui-action)<a href="https://agentmods.dev/commands/ch-bas/kibana-plugin-helper/ui-action"><img src="https://agentmods.dev/badge/commands/ch-bas/kibana-plugin-helper/ui-action.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.00025 | $0.01052 |
| Opus 5 | $0.00013 | $0.00526 |
| Sonnet 5 | $0.00005 | $0.00210 |
| Haiku 4.5 | $0.00003 | $0.00105 |
Grade A, and why
ui-action 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 5d 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.
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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Kibana UI Action
Create custom UI Actions and Triggers that enable inter-plugin communication and contextual user interactions (e.g. clicking a table row to open a flyout, drilldowns from dashboard panels, context menu items). Ask the user for:
- Action or Trigger? Are they creating a new action, a new trigger, or both?
- Action ID (UPPER_SNAKE_CASE, e.g.
MY_PLUGIN_OPEN_DETAIL_ACTION) - Action display name (human-readable, e.g. "Open detail view")
- Trigger ID (if creating a trigger — e.g.
MY_PLUGIN_ROW_CLICK_TRIGGER) - Context type — what data does the action receive when executed? (e.g. a saved object ID, an embeddable, a row of data, coordinates)
- Where does it appear? Context menu, panel header, custom trigger point, or programmatic execution
- What does it do? Opens a flyout, navigates to a page, applies a filter, opens a modal, calls an API
Generation Steps
-
Create the action/trigger files in
public/actions/and/orpublic/triggers/:public/ ├── actions/ │ ├── index.ts │ ├── my_action.ts # Action implementation │ └── my_action_context.ts # Context type definition ├── triggers/ │ ├── index.ts │ └── my_trigger.ts # Trigger definition -
For a Trigger:
- Define a trigger ID constant
- Create the trigger with
id,title,description - Register via
uiActions.registerTrigger()insetup()
-
For an Action:
- Define an action ID constant
- Create an action class extending
Action<Context>or usingcreateAction() - Implement
execute({ context })— the logic that runs when triggered - Implement
isCompatible({ context })— whether the action should appear for this context - Implement
getDisplayName(),getIconType()for menu rendering - Register via
uiActions.registerAction()insetup() - Attach to one or more triggers via
uiActions.attachAction(triggerId, actionId)insetup()
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.
- 5d ago First seen · 87 lines · 25 tokens per session scan A bc45fb1965c2
ui-action is a command published in the GitHub repository ch-bas/kibana-plugin-helper (3 stars, last pushed 6mo ago), licensed MIT. It adds 25 tokens to every session and 1,052 once invoked, about $0.0001 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-08-31.
Other commands, from other repositories
dead-code-clean
Actively find and remove dead code, unused imports, duplicates, and zombie code.
dead-code-scan
Scan for dead code, unused imports, duplicates, and zombie code across the project.
esp-teach
One-time project setup -- discover hardware, find datasheets, persist context to CLAUDE.md.
swift-critique
Critique SwiftUI code for patterns, design, clean code, accessibility, and performance.
dotnet-harden
Scan and harden .NET backend code against high-impact anti-patterns such as sync-over-async, lifetime bugs, fat endpoints, and fragile SignalR state.
dotnet-teach
One-time setup that scans a .NET backend project, learns its conventions and architecture, and writes them to CLAUDE.md for future sessions.