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 skills add fakoli/fakoli-plugins --skill k8s-sidecar-testinggit clone --depth 1 https://github.com/fakoli/fakoli-pluginsWrote 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/skills/fakoli/fakoli-plugins/k8s-sidecar-testing)<a href="https://agentmods.dev/skills/fakoli/fakoli-plugins/k8s-sidecar-testing"><img src="https://agentmods.dev/badge/skills/fakoli/fakoli-plugins/k8s-sidecar-testing/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/fakoli/fakoli-plugins/k8s-sidecar-testing"><img src="https://agentmods.dev/badge/skills/fakoli/fakoli-plugins/k8s-sidecar-testing.svg" alt="Reviewed on agentmods" width="80" 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.00043 | $0.00516 |
| Opus 5.5 | $0.00017 | $0.00206 |
| Sonnet 5.5 | $0.00009 | $0.00103 |
| Haiku 4.5 | $0.00004 | $0.00052 |
Grade A, and why
k8s-sidecar-testing 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 1mo 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.
What it actually says
K8s Sidecar Testing
Use the helpers for the nat464 demo topology. Inspect the actual project manifests and container names first; adapt the checks if its contract differs. The supplied cluster setup is IPv4-primary dual-stack, not IPv6-only or an AWS EKS emulator.
Resolve SKILL_DIR to the directory containing this installed SKILL.md. Helpers live at $SKILL_DIR/scripts/; manifests and Dockerfile belong to the user's project, selected with --project-dir. These are separate paths. When working inside a VM, transfer the whole skill directory as well as the project.
- Read the plugin README for prerequisites, topology, arguments, and mutation boundaries. Reuse an authorized existing test environment when available; VM provisioning is optional.
- Select an explicit kubeconfig context and a dedicated namespace using
--context/--namespaceorKUBE_CONTEXT/KUBE_NAMESPACE. Helpers preserve the caller'sKUBECONFIG. Never infer a target from whichever context is current. - For existing pods, run
validate-paths.sh; it does not deploy resources. For a requested deployment, rundeploy-test.sh --project-dir ...with both project manifests. It validates supported resources and ownership before applying, then returns the checks' actual exit status. Existing unowned resources are not adopted. - Run
benchmark.sh --iterations 50only when performance measurement is requested. Report failed samples as well as p50/p95/p99. External HTTP checks require--external-url; a skipped check is not a pass. - On requested cleanup,
teardown.shremoves only known, owned Pods/ConfigMaps in the selected namespace. VM deletion is a separate explicitly targeted operation documented in the README.
All helpers accept --help. Provisioning, image import, deploy, cleanup, and benchmarks are independent operations; a request to inspect or validate does not imply permission to run all phases. Treat nonzero exits, missing prerequisites, absent IPv6, timeout, and infrastructure errors as incomplete/failed evidence. Do not rerun or broaden scope silently.
See troubleshooting for diagnosing failed checks and the authoritative upstream sources behind networking assumptions.
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- agents/openai.yaml 220 B
- references/troubleshooting.md 4.5 KB
- scripts/benchmark.sh 227 B runs code
- scripts/build-image.sh 229 B runs code
- scripts/deploy-test.sh 229 B runs code
- scripts/k3s-setup.sh 227 B runs code
- scripts/sidecar.py 19 KB runs code
- scripts/teardown.sh 226 B runs code
- scripts/validate-paths.sh 232 B runs code
- scripts/vm-setup.sh 226 B runs code
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.
- 1mo ago Changed · -110 lines · -74 tokens per session 9e29ec1855da
- 1mo ago First seen · 131 lines · 117 tokens per session scan A 1ea07ecf667e
k8s-sidecar-testing is a skill published in the GitHub repository fakoli/fakoli-plugins (4 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 516 once invoked, about $0.0002 per session on Opus 5.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 skills, from other repositories
demo-review
Quality-checks a rendered demo video before it ships — extracts frames, grades each section against its successCriteria, and finds spinners, empty states, clipped text, exposed secrets, audio/video desync, and pacing problems. Use after a draft render, before a final render, or when asked whether a demo video is good…
agent-e2e-test-specialist
Specialist subagent: Playwright, Cypress, and visual regression testing specialist. Use only when the user explicitly asks for E2E tests, browser test automation, or visual regression testing. Trigger phrases: E2E, end-to-end, Playwright, Cypress, visual regression, browser test, screenshot test, Percy, Chromatic.
cypress-ops
Cypress end-to-end and component testing operations - selector/retry-ability strategy, cy.intercept network stubbing, cy.session auth, component vs e2e, flake diagnosis, CI, Test Replay. Use for: cypress, e2e test, component test, cy.get, cy.intercept, cy.session, data-cy, data-test, retry-ability, flake, flaky test…
playwright-ops
Playwright end-to-end testing operations - selectors, fixtures, network mocking, auth, parallelism, CI, visual regression, flake hunting. Use for: playwright, e2e test, end-to-end testing, browser test, getByRole, page object, storageState, trace viewer, flaky test, test sharding, visual regression, toHaveScreenshot…
visual-proof
Capture before/after screenshot evidence of a web page at real breakpoints (375, 768, 1440) in both light and dark themes, using Playwright against a local dev server or a deployed URL. Use before starting any visual change to capture the current state, and again after to prove the delta. Also use when asked to "show…
e2e
Orchestrates e2e testing: BDD scenarios, Playwright autotests. Triggers: e2e tests, BDD scenarios, write autotest.