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 agents/ramilito/kubectl.nvim/logsgit clone --depth 1 https://github.com/Ramilito/kubectl.nvimWrote 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/agents/ramilito/kubectl.nvim/logs)<a href="https://agentmods.dev/agents/ramilito/kubectl.nvim/logs"><img src="https://agentmods.dev/badge/agents/ramilito/kubectl.nvim/logs.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.1 | $0.00028 | $0.02958 |
| Opus 5 | $0.00014 | $0.01479 |
| Sonnet 5 | $0.00006 | $0.00592 |
| Haiku 4.5 | $0.00003 | $0.00296 |
Grade A, and why
logs 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pod Logs Feature Guidance
ALWAYS use this subagent for ANY task involving:
- Log streaming, tailing, or fetching
- JSON expand/collapse in log output
- Log view keybindings or syntax highlighting
- Histogram visualization
LogSessionUserData or related mlua bindings
For general mlua FFI patterns (async functions, JSON serialization, error handling), use the rust subagent.
File Map
| Layer | File | Purpose |
|---|---|---|
| Rust | kubectl-client/src/cmd/log_session.rs |
Streaming session, histogram, log fetching, toggle_json() |
| Rust | kubectl-client/src/cmd/mod.rs:124-128 |
Registers log_stream_async and log_session exports |
| Rust | kubectl-client/src/lib.rs:474-488 |
Exposes toggle_json to Lua |
| Rust | kubectl-client/src/structs.rs |
LogConfig/PodRef structs + custom FromLua impl |
| Lua | lua/kubectl/client/init.lua |
client.log_session() / client.toggle_json() wrappers |
| Lua | lua/kubectl/client/types.lua |
kubectl.LogSession / kubectl.ToggleJsonResult annotations |
| Lua | lua/kubectl/resources/pods/init.lua |
Entry points: Logs(), TailLogs(), LogsWithPods(), LogsForFilter(), get_pods_for_logs() |
| Lua | lua/kubectl/views/logs/session.lua |
Session manager: options, timer polling, lifecycle |
| Lua | lua/kubectl/resources/pod_logs/mappings.lua |
Keybindings only — no sibling init.lua/definition.lua |
| Vim | syntax/k8s_pod_logs.vim |
Syntax highlighting |
pod_logs is not a BaseResource.extend module. Its view is assembled ad hoc inside pods/init.lua's LogsWithPods() (a framed buffer built via resource_factory's view_framed), and its mappings are loaded generically from the k8s_pod_logs filetype (strip k8s_ prefix → require kubectl.resources.pod_logs.mappings).
Data Flow
Two distinct code paths share one pod-list resolver but differ in transport:
Lua Transport Rust (dylib)
-------------------------------------------------------------------------------------------
Logs() / LogsWithPods() --> commands.run_async --> fetch_logs_async
one-shot, full buffer (libuv worker thread, (async fn) resolves
replace via buffers.set_content args JSON-encoded) targets, merges streams,
renders histogram
TailLogs() / session:start() --> client.log_session --> log_session
follow, incremental append (direct sync FFI call, blocks (sync fn) LogConfig via
--> views/logs/session.lua timer custom FromLua, spawns one
(vim.uv.new_timer, 200ms) polls Tokio task per container
session:read_chunk(), appends lines into a shared LogSession
toggle_json() -----------------------------------------------------> cmd::log_session::toggle_json
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 · 183 lines · 28 tokens per session scan A 2c774acea437
logs is an agent published in the GitHub repository Ramilito/kubectl.nvim (537 stars, last pushed 22d ago), licensed Apache-2.0. It adds 28 tokens to every session and 2,958 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-09-04.
Other agents, from other repositories
Meshery Code Contributor
Expert-level software engineering agent specialized in contributing to Meshery's cloud native infrastructure and application management platform.
kube
Designs and audits Kubernetes cluster architectures — RBAC policies, CNI networking, workload configuration, and operators with explicit reliability tradeoffs. Use when designing a cluster, auditing RBAC, or rightsizing workloads. Trigger with "design a Kubernetes cluster", "audit our RBAC".
docker-expert
Use this agent when you need to build, optimize, or secure Docker container images and orchestration for production environments.
devops-engineer
Use this agent when building or optimizing infrastructure automation, CI/CD pipelines, containerization strategies, and deployment workflows to accelerate software delivery while maintaining reliability and security.
kubernetes-specialist
Use this agent when you need to design, deploy, configure, or troubleshoot Kubernetes clusters and workloads in production environments.
deploy-to-staging
Use this agent PROACTIVELY when deploying applications to staging or QA environments. This includes running test suites before deployment, building production bundles, creating Docker images, pushing to container registries, deploying to Kubernetes staging namespaces, and running smoke tests. Invoke when someone says…