All Claude Code modsholdennguyen/claude-code-setup

k9s

A Claude Code mod in holdennguyen/claude-code-setup

A live, interactive k9s terminal in a pane (k9s runs under a private tmux server, so kube auth and context come from the shell that launched Claude Code), plus two tools so the model can read the k9s screen and send it keys. While k9s runs, Bash calls that invoke kubectl are refused and the model is pointed at those tools; kubectl works as usual otherwise. One server per Claude Code process, a watchdog and a start-up sweep keep orphans from surviving, and an idle stop keeps k9s from polling the cluster unseen.

k9s reaches L2 (writes or runs) and passed claude plugin validate on Claude Code 2.1.302.

Events hooked: 7
API methods referenced: 12
Access from classified calls: L2, writes or runs: runs processes, drives Claude, reads mod state, draws
Reads mod state: the scan does not record whose state, so this does not show that it reads another mod’s values
Static scan, not a runtime test

Install hint

/plugin install k9s --marketplace holdennguyen/claude-code-setup

From the repository's own marketplace. Confirm the plugin name in the repository's README before installing. Mods need Claude Code 2.1.287 or later.

Access

L2 Writes or runsruns processes, drives Claude, reads mod state, draws

Validation

Passed on Claude Code 2.1.302

View the source on GitHub Back to the list

What the scan recorded

Observed events: Bash calls, mcp__k9s__screen calls, mcp__k9s__keys calls
Hooks: session.start, session.end, ui.close {id=k9s}, command.run {command=k9s}, tool.call {tool=Bash}, tool.call {tool=mcp__k9s__screen}, tool.call {tool=mcp__k9s__keys}, ui.message, ui.render {component=Pane, requestId=k9s}
API calls: $.clock.after, $.clock.every, $.clock.sleep, $.command.register, $.process.run, $.state.get, $.state.set, $.tool.register, $.ui.open, $.ui.panes, $.ui.resolve, $.ui.toast
Surface modules: hooks/screen.tsx
Validation on 2.1.302: Passed
Scanned revision: a1d4dbea5243
Marketplace passed: claude-code-setup

These are the hooks and API calls reported by claude plugin validate. Access levels describe the widest reach of those calls and are not safety ratings. Validation is a static check, not a runtime test, and a passing result does not prove that a mod works or is safe. How the scan works.

Badge for your README

Authors can show the latest scan result in their README. Each badge links to this page.

[![reach](https://raw.githubusercontent.com/karanb192/awesome-claude-code-mods/main/badges/holdennguyen--claude-code-setup--k9s-reach.svg)](https://mods.aidojo.si/mods/holdennguyen--claude-code-setup--k9s/)
[![validates](https://raw.githubusercontent.com/karanb192/awesome-claude-code-mods/main/badges/holdennguyen--claude-code-setup--k9s-validates.svg)](https://mods.aidojo.si/mods/holdennguyen--claude-code-setup--k9s/)