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/saved-objectgit 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/saved-object)<a href="https://agentmods.dev/commands/ch-bas/kibana-plugin-helper/saved-object"><img src="https://agentmods.dev/badge/commands/ch-bas/kibana-plugin-helper/saved-object.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.00024 | $0.00992 |
| Opus 5 | $0.00012 | $0.00496 |
| Sonnet 5 | $0.00005 | $0.00198 |
| Haiku 4.5 | $0.00002 | $0.00099 |
Grade A, and why
saved-object 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 4d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Kibana Saved Object Type
Create a complete custom Saved Object type for a Kibana plugin. Ask the user for:
- Saved Object type name (snake_case, e.g.
my_plugin_dashboard) - Attributes/fields (name, type, required/optional for each)
- Namespace type:
single(space-scoped),multiple(shareable across spaces), oragnostic(global) - Hidden? (default: false — hidden types are only accessible via the internal API)
- Needs migrations? (if upgrading from a previous version, describe schema changes)
- Needs management integration? (visible in Kibana's Saved Objects management page)
- Needs references to other saved objects? (e.g. references to dashboards, index patterns)
- Needs import/export support? (default: yes for non-hidden types)
Generation Steps
- Create the saved object type definition in
server/saved_objects/directory - Generate the type registration file with:
- Type name constant in
common/index.ts - Attribute mappings (keyword, text, boolean, integer, long, date, object, nested, etc.)
namespaceTypesettinghiddenflagmanagementsection (importableAndExportable, icon, defaultSearchField, getTitle, getInAppUrl)mappingswith all properties correctly typed
- Type name constant in
- Generate migrations if needed:
- Create
server/saved_objects/migrations/directory - Create versioned migration functions (e.g.
7.14.0,8.0.0) - Each migration transforms the document from one version to the next
- Use
SavedObjectMigrationFntype signature
- Create
- Generate a CRUD service class in
server/services/:create()— creates a new saved objectget()— retrieves by IDfind()— searches with filters, pagination, sortingupdate()— partial updatedelete()— removes the saved objectbulkCreate()/bulkGet()— batch operations- Proper error handling with
SavedObjectsErrorHelpers
- Register the type in the server plugin's
setup()method usingcore.savedObjects.registerType() - Generate server routes that use the CRUD service
- If management integration is needed, configure
managementproperties in the type definition
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.
- 4d ago First seen · 92 lines · 24 tokens per session scan A 1732a6a9e7cd
saved-object is a command published in the GitHub repository ch-bas/kibana-plugin-helper (3 stars, last pushed 6mo ago), licensed MIT. It adds 24 tokens to every session and 992 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-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.
dead-code-clean
Actively find and remove dead code, unused imports, duplicates, and zombie code.
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.
rust-critique
Deep code critique — read the target Rust code and apply the full review process. Evaluates soundness, ownership, error handling, type design, async correctness, performance, and architecture. Think like a senior Rust engineer giving honest feedback.