vigilante-issue-implementation-on-kubernetes

vigilante-issue-implementation-on-kubernetes is a skill for Codex from aliengiraffe/vigilante. It costs 39 tokens per session (918 once invoked), scanned A, original, Apache-2.0.

A procedure for implementing GitHub issues in Kubernetes-focused repositories, including safer handling of deployment configuration and workload security.

In plain words
What is it for?
Use it to complete Vigilante-dispatched issues involving Kubernetes manifests, workloads, labels, validation, RBAC, or service-account settings.
Why use it?
It keeps Kubernetes changes limited to the issue while checking configuration, permissions, service accounts, and manifest quality.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: mentions AGENTS.md; mentions Codex.

Good fit Use it to complete Vigilante-dispatched issues involving Kubernetes manifests, workloads, labels, validation, RBAC, or service-account settings.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/aliengiraffe/vigilante/vigilante-issue-implementation-on-kubernetes
Install

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.

Any agent
npx skills add aliengiraffe/vigilante --skill vigilante-issue-implementation-on-kubernetes
Clone the repo
git clone --depth 1 https://github.com/aliengiraffe/vigilante

Made for: Codex.

Wrote 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.

agentmods badge for vigilante-issue-implementation-on-kubernetes

README.md
[![agentmods](https://agentmods.dev/badge/skills/aliengiraffe/vigilante/vigilante-issue-implementation-on-kubernetes/github.svg)](https://agentmods.dev/skills/aliengiraffe/vigilante/vigilante-issue-implementation-on-kubernetes)
Your own site
<a href="https://agentmods.dev/skills/aliengiraffe/vigilante/vigilante-issue-implementation-on-kubernetes"><img src="https://agentmods.dev/badge/skills/aliengiraffe/vigilante/vigilante-issue-implementation-on-kubernetes/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.

agentmods 80×15 button for vigilante-issue-implementation-on-kubernetes

Your own site · 80×15
<a href="https://agentmods.dev/skills/aliengiraffe/vigilante/vigilante-issue-implementation-on-kubernetes"><img src="https://agentmods.dev/badge/skills/aliengiraffe/vigilante/vigilante-issue-implementation-on-kubernetes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 918 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00039 $0.00918
Opus 5 $0.00019 $0.00459
Sonnet 5 $0.00008 $0.00184
Haiku 4.5 $0.00004 $0.00092

Measured 11d ago against content hash c600ce52abf5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

vigilante-issue-implementation-on-kubernetes 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 11d 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.

skills/vigilante-issue-implementation-on-kubernetes/SKILL.md · 62 lines

How it starts

The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Vigilante Kubernetes Issue Implementation

Focus

  • Read the prompt for detected tech stacks, process hints, and Kubernetes security guidance before changing manifests.
  • Treat Kubernetes manifest changes as operationally sensitive — not as generic YAML edits.
  • Keep changes scoped to the issue and do not broaden into unrelated cluster-ops or security redesign work.

Manifest Hygiene

  • Use recommended Kubernetes labels (app.kubernetes.io/name, app.kubernetes.io/version, etc.) on all new resources.
  • Validate manifest YAML syntax before committing. Use kubectl --dry-run=client -o yaml or an equivalent offline validator when available.
  • Prefer kustomize overlays or Helm values for environment-specific configuration rather than duplicating manifests.
  • Keep resource definitions focused — one resource per file when practical, with clear naming.

Service Account Hygiene

  • Do not use the default service account for workloads. Create dedicated service accounts scoped to the workload's needs.
  • Set automountServiceAccountToken: false on pods and service accounts that do not need API access.
  • When a workload requires API access, bind the minimum RBAC permissions to its dedicated service account.

Pod and Container Security Context

  • Set runAsNonRoot: true and specify a numeric runAsUser in the pod or container securityContext.
  • Set allowPrivilegeEscalation: false on containers.
  • Set readOnlyRootFilesystem: true where the application supports it, using emptyDir volumes for writable paths.
  • Drop all capabilities and add back only what is required: securityContext.capabilities.drop: ["ALL"].
  • Prefer Restricted Pod Security Standards when the workload allows it.

RBAC and Permissions

  • Follow least-privilege principles: prefer Role and RoleBinding (namespace-scoped) over ClusterRole and ClusterRoleBinding unless the workload genuinely needs cluster-wide access.
  • Avoid wildcards (*) in RBAC rules for verbs, resources, or API groups.
  • When the issue only requires application-level changes, do not introduce or modify cluster-scoped resources.

Read the full file on GitHub · 62 lines

Files

What ships with it

1 file 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.

Changes

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.

  1. 11d ago First seen · 62 lines · 39 tokens per session scan A c600ce52abf5

Subscribe to this mod's changes

vigilante-issue-implementation-on-kubernetes is a skill published in the GitHub repository aliengiraffe/vigilante (40 stars, last pushed 2d ago), licensed Apache-2.0. It adds 39 tokens to every session and 918 once invoked, about $0.0002 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-30.

Related

Other skills, from other repositories

document-processor

Guidance for processing documents, extracting content, and transforming structured information. Use when the user asks to process, parse, extract, or transform document content such as PDFs, Word files, or spreadsheets.

vixues/LeAgent · 44 tokens

skill-packager

Authors Agent Skills v1.0 packages (SKILL.md plus references/scripts), runs packageskill to produce a standards-compliant zip, and uses installskill to add skills from HTTPS, registry, workspace, or an uploaded archive. Use when the user wants to turn documentation, workflows, or code into a portable skill, export a…

vixues/LeAgent · 87 tokens

workflow-helper

Guidance for creating, managing and executing workflow automations that chain multiple tools and agents together. Use when the user asks about building, listing, running or composing workflows and automated task pipelines.

vixues/LeAgent · 41 tokens

attendance-signin-sheet

A spreadsheet generator for printable attendance or meeting sign-in sheets. It turns a list of names into rows with columns such as signatures, dates, departments, or employee IDs.

vixues/LeAgent · 51 tokens

data-analyzer

Guidance for analyzing structured data, generating statistics and producing data-driven insights. Use when the user asks to analyze data, compute statistics, find patterns, or generate analytical reports.

vixues/LeAgent · 39 tokens

procurement-audit

A procurement review workflow that checks contracts and purchase documents against uploaded purchasing rules. It links each finding to the relevant rule and supporting text.

vixues/LeAgent · 39 tokens