tooling-detector

tooling-detector is a skill for Claude Code from FortiumPartners/ensemble. It costs 0 tokens per session (2,897 once invoked), scanned C, original, MIT.

A project-analysis tool that detects whether a codebase uses Helm, Kubernetes, Kustomize, or Argo CD infrastructure files.

In plain words
What is it for?
It is for identifying Kubernetes and GitOps tooling and automatically loading matching skills for project analysis or delivery work.
Why use it?
It helps an agent recognize the project's deployment tools before choosing related workflows or instructions.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the ensemble-infrastructure plugin — 11 skills, 7 agents shipped together

Good fit It is for identifying Kubernetes and GitOps tooling and automatically loading matching…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/fortiumpartners/ensemble/tooling-detector
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 FortiumPartners/ensemble --skill tooling-detector
Clone the repo
git clone --depth 1 https://github.com/FortiumPartners/ensemble

Made for: Claude Code.

Or install ensemble-infrastructure, the plugin that ships this one along with the rest of its 11 skills, 7 agents.

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 tooling-detector

README.md
[![agentmods](https://agentmods.dev/badge/skills/fortiumpartners/ensemble/tooling-detector.svg)](https://agentmods.dev/skills/fortiumpartners/ensemble/tooling-detector)
Your own site
<a href="https://agentmods.dev/skills/fortiumpartners/ensemble/tooling-detector"><img src="https://agentmods.dev/badge/skills/fortiumpartners/ensemble/tooling-detector.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,897 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. A grade says what 26 rules found in the file — not that it is safe.
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.00000 $0.02897
Opus 5 $0.00000 $0.01448
Sonnet 5 $0.00000 $0.00579
Haiku 4.5 $0.00000 $0.00290

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

Security

Grade C, and why

tooling-detector scanned grade C with 1 finding 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 3d ago.

The scan reads SKILL.md. This mod also ships 2 executable files (detect-tooling.js, performance-benchmark.js), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Reaches for credential fileshighPrivilege escalation

SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.

- `.kube/config`, `kubeconfig`
packages/infrastructure/skills/tooling-detector/SKILL.md · 507 lines

How it starts

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

Tooling Detection System

Version: 1.0.0 | Purpose: Automatic detection of infrastructure tooling (Helm, Kubernetes, Kustomize, ArgoCD)


Overview

The tooling detection system automatically identifies infrastructure and DevOps tooling usage in projects using multi-signal analysis. It detects Helm charts, Kubernetes manifests, Kustomize configurations, and GitOps tools with 95%+ accuracy.

Supported Tools:

  • Helm: Kubernetes package manager
  • Kubernetes: Container orchestration platform
  • Kustomize: Kubernetes configuration customization
  • ArgoCD: GitOps continuous delivery

Use Cases:

  • Auto-load skills: Automatically load Helm/Kubernetes skills when detected
  • Project analysis: Identify tooling stack in existing projects
  • CI/CD integration: Dynamic skill loading based on detected tooling

Quick Start

Detect All Tools

node skills/tooling-detector/detect-tooling.js /path/to/project

Output:

{
  "detected": true,
  "tools": [
    {
      "tool": "helm",
      "name": "Helm",
      "confidence": 0.9,
      "signals": {
        "chart_yaml": true,
        "values_yaml": true,
        "templates_dir": true
      },
      "signal_count": 3
    },
    {
      "tool": "kubernetes",
      "name": "Kubernetes",
      "confidence": 0.85,
      "signals": {
        "api_version": true,
        "kind_field": true,
        "manifests_dir": true
      },
      "signal_count": 3
    }
  ]
}

Detect Specific Tool

# Detect Helm
node skills/tooling-detector/detect-tooling.js /path/to/project --tool helm

# Detect Kubernetes
node skills/tooling-detector/detect-tooling.js /path/to/project --tool kubernetes

Custom Confidence Threshold

node skills/tooling-detector/detect-tooling.js /path/to/project --min-confidence 0.8

Detection Signals

Helm Detection

Primary Signals (High Confidence):

  • Chart.yaml file (weight: 0.6) - Helm chart metadata
  • values.yaml file (weight: 0.3) - Default values
  • templates/ directory (weight: 0.2) - Template manifests

Read the full file on GitHub · 507 lines

Files

What ships with it

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

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. 3d ago First seen · 507 lines · 0 tokens per session scan C 76ab7a530cd4

Subscribe to this mod's changes

tooling-detector is a skill published in the GitHub repository FortiumPartners/ensemble (11 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,897 tokens. A static security scan graded it C with 1 finding (reaches for credential files). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories

cli-forge-github

Audit and fix GitHub repository health: rulesets vs CI alignment, branch hygiene, PR lifecycle, release automation flow, permission issues, and transient CI failures. Detects misconfigurations that cause PRs to hang, CI to fail silently, branches to accumulate, and releases to stall. Use when the user says 'PR stuck'…

Destynova2/cli-code-skills · 165 tokens

cli-audit-review

Scored MR/PR/diff review skill calibrated for strict infrastructure and automation changes. Use for merge-request reviews, pull-request reviews, scored reviewer gates, convention compliance, Ansible roles/collections, Molecule, GitLab CI, semantic-release, packaging, Go/Cobra CLIs, PowerShell, shell/Python helpers…

Destynova2/cli-code-skills · 138 tokens

cli-forge-pipeline

Expert CI/CD pipeline optimizer using biomimetic patterns from nature: leafcutter ants (task partitioning), slime mold (adaptive path optimization), army ants (self-organizing parallelism), honeybees (dynamic resource allocation), and mycelium (fault-tolerant routing). Works with any CI system — examples cover both…

Destynova2/cli-code-skills · 187 tokens

atmos-pro

Atmos Pro setup and workflows: settings.pro, GitHub OIDC, affected and inventory uploads, stack locks, pro commit, workflow dispatch, merge queues, and drift detection.

cloudposse/atmos · 38 tokens

atmos-sbom

Atmos SBOM provenance: CycloneDX and SPDX generation from vendor and Terraform evidence, coverage diagnostics, NTIA validation, and native CI workflow-artifact publication.

cloudposse/atmos · 36 tokens

context-recovery

Recovers project handoff context from local Codex, Claude Code, Gemini, CodeBuddy, and codexmate-derived sessions. Use when the user asks what happened in prior project/PR/branch/file/error work, needs a handoff brief, wants old decisions or validations recovered, or asks to summarize cross-session project activity…

SakuraByteCore/codexmate · 72 tokens