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/architecture-verifygit 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/architecture-verify)<a href="https://agentmods.dev/agents/ramilito/kubectl.nvim/architecture-verify"><img src="https://agentmods.dev/badge/agents/ramilito/kubectl.nvim/architecture-verify.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.00027 | $0.01127 |
| Opus 5 | $0.00014 | $0.00563 |
| Sonnet 5 | $0.00005 | $0.00225 |
| Haiku 4.5 | $0.00003 | $0.00113 |
Grade A, and why
architecture-verify 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Verification Subagent
Verifies codebase against architecture contract. Works with dependency graphs, not source code.
Overview
This subagent verifies the codebase adheres to the architecture contract by:
- Extracting dependency graphs (cheap)
- Checking against documented rules
- Sampling files only to verify pattern conformance
Invocation
"Verify architecture health"
"Check for architecture violations"
"Verify resource pattern conformance"
Phase 1: Extract Dependency Graph
Run these commands to build the graph (zero tokens):
Lua Dependencies
# Core -> * dependencies
for f in lua/kubectl/*.lua; do
echo "=== $f ==="
grep "^local.*require" "$f" | sed 's/.*require("\([^"]*\)").*/\1/'
done
# Resources -> * dependencies
for f in lua/kubectl/resources/*/init.lua; do
echo "=== $f ==="
grep "^local.*require" "$f" | sed 's/.*require("\([^"]*\)").*/\1/'
done
# Views -> * dependencies
for f in lua/kubectl/views/*/init.lua; do
echo "=== $f ==="
grep "^local.*require" "$f" | sed 's/.*require("\([^"]*\)").*/\1/'
done
# Actions -> * dependencies
for f in lua/kubectl/actions/*.lua; do
echo "=== $f ==="
grep "^local.*require" "$f" | sed 's/.*require("\([^"]*\)").*/\1/'
done
Rust Dependencies
# Module -> module dependencies
for f in kubectl-client/src/*.rs; do
echo "=== $f ==="
grep "^use crate::" "$f" | sed 's/use crate::\([^:;{]*\).*/\1/'
done
Phase 2: Verify Against Contract
With the dependency graph extracted, check these rules:
Lua Rules to Verify
| Rule | How to Check |
|---|---|
| Utils is leaf | No require in utils/*.lua that points outside utils |
| Client is leaf | No require in client/*.lua that points outside client |
| Resources don't cross-require | Resources only require base_resource, not other resources |
| Views don't require resources | No kubectl.resources.* in views/*/init.lua |
| Actions don't require resources | No kubectl.resources.* in actions/*.lua |
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 · 174 lines · 27 tokens per session scan A 9cf1cb5b0448
architecture-verify is an agent published in the GitHub repository Ramilito/kubectl.nvim (537 stars, last pushed 22d ago), licensed Apache-2.0. It adds 27 tokens to every session and 1,127 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
claworc-dev-troubleshooter
Use this agent when the user reports issues with the local Claworc development environment, encounters unexpected behavior in the control plane backend, frontend, LLM proxy, or running OpenClaw instances, or needs help diagnosing why something isn't working as expected. The agent assumes the environment is already…
k8s-pod-checker
Use this agent PROACTIVELY when troubleshooting Kubernetes pod issues or performing health checks. This includes diagnosing CrashLoopBackOff, ImagePullBackOff, pending pods, OOMKilled pods, or general pod health assessment across namespaces.
devops-troubleshooter
Expert DevOps troubleshooter specializing in rapid incident response, advanced debugging, and modern observability. Masters log analysis, distributed tracing, Kubernetes debugging, performance optimization, and root cause analysis. Handles production outages, system reliability, and preventive monitoring. Use…
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.