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 infraspecdev/tesseract --skill security-auditgit clone --depth 1 https://github.com/infraspecdev/tesseractWrote 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/infraspecdev/tesseract/security-audit)<a href="https://agentmods.dev/skills/infraspecdev/tesseract/security-audit"><img src="https://agentmods.dev/badge/skills/infraspecdev/tesseract/security-audit/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/infraspecdev/tesseract/security-audit"><img src="https://agentmods.dev/badge/skills/infraspecdev/tesseract/security-audit.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.00063 | $0.01308 |
| Opus 5.5 | $0.00025 | $0.00523 |
| Sonnet 5.5 | $0.00013 | $0.00262 |
| Haiku 4.5 | $0.00006 | $0.00131 |
Grade A, and why
kubernetes-security-audit 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.
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kubernetes Security Audit
Overview
Deep security audit for Kubernetes manifests, Helm templates, and Kustomize overlays. This skill catches security misconfigurations that general-purpose review cannot: overly permissive RBAC, containers running as root, missing network policies, secrets in environment variables, and images pulled without digest pinning.
Only triggers when there is clear evidence of Kubernetes usage (manifest files with K8s resource kind: fields, Helm charts, Kustomize overlays, or explicit user mention of K8s/EKS/GKE/AKS). When ambiguous (e.g., generic YAML without K8s resource kinds), ask the user before proceeding.
When to Use
- When reviewing K8s manifests (Deployment, StatefulSet, DaemonSet, Pod, etc.) for security issues
- When auditing RBAC configuration (Role, ClusterRole, RoleBinding, ClusterRoleBinding)
- When checking network policies for ingress/egress restrictions
- When validating pod security contexts and security standards
- When reviewing secrets handling in K8s manifests
- During security review of EKS-specific configurations (IRSA, pod identity, aws-auth)
When NOT to Use
- For Terraform security review — use
terraform-security-auditinstead - For generic YAML files that are not K8s manifests — ask the user first
- For runtime cluster security (this is static manifest audit only)
- For application-level security (OWASP, auth flows) — use general security review
- When no K8s evidence is detected and user hasn't mentioned K8s
Workflow
- Detect K8s presence: Confirm K8s manifests exist (look for
apiVersion:andkind:fields with K8s resource types). If ambiguous, ask user. - Collect scope: Identify all manifest files (
.yaml,.yml) containing K8s resources, Helm templates, and Kustomize bases/overlays. - RBAC audit: Read every Role, ClusterRole, RoleBinding, and ClusterRoleBinding. Flag wildcard verbs/resources, unnecessary cluster-admin bindings, overly broad API group access.
- Pod security audit: Check every Pod spec (in Deployments, StatefulSets, DaemonSets, Jobs, CronJobs, Pods) for security context, privilege escalation, capabilities, host namespace sharing.
- Network policy audit: Verify network policies exist for namespaces with workloads. Flag missing policies, allow-all rules, and unrestricted egress.
- Secrets audit: Check for secrets in environment variables (should use volume mounts), hardcoded values in manifests, and unencrypted Secret resources.
- Image security audit: Flag
latesttag, missing image digest, untrusted registries, missingimagePullPolicy. - Service account audit: Check for unnecessary auto-mounted service account tokens, default service account usage.
- Pod Security Standards: Evaluate against PSS baseline and restricted profiles.
- EKS-specific checks (if EKS detected): IRSA configuration, EKS pod identity, aws-auth ConfigMap, managed node group security.
- Deprecation flag: If deprecated APIs are found (e.g., PodSecurityPolicy), flag them and recommend running
deprecation-check-and-upgradefor full migration guidance. - Produce report: Use the template from
templates.md.
What ships with it
2 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.
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 First seen · 83 lines · 63 tokens per session scan A 61540617ef2a
kubernetes-security-audit is a skill published in the GitHub repository infraspecdev/tesseract (5 stars, last pushed 3mo ago), licensed MIT. It adds 63 tokens to every session and 1,308 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
bdd-container-update
Update the BDD test container image when its dependencies or runtime change. Determines version bump (major vs minor vs patch), rebuilds the Docker image, pushes to GitLab registry, and updates the image tag in starttest.sh. Test source (tests/, features/, scripts/, data/, conftest.py) is bind-mounted from the host…
docker-socket-mount
Docker / containerd socket mounted into a container → host RCE. Common in CI runners, GitOps controllers (ArgoCD, Flux), and 'Docker-in-Docker' setups. Single-command escape via docker run --rm --privileged -v /:/host alpine chroot /host.
securing-kubernetes-on-cloud
This skill covers hardening managed Kubernetes clusters on EKS, AKS, and GKE by implementing Pod Security Standards, network policies, workload identity, RBAC scoping, image admission controls, and runtime security monitoring. It addresses cloud-specific security features including IRSA for EKS, Workload Identity for…
detecting-privilege-escalation-in-kubernetes-pods
Detect and prevent privilege escalation in Kubernetes pods by monitoring security contexts, capabilities, and syscall patterns with Falco and OPA policies.
polar-local-environment
This skill should be used when setting up or managing Polar local development environment with Docker.