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 FortiumPartners/ensemble --skill tooling-detectorgit clone --depth 1 https://github.com/FortiumPartners/ensembleWrote 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/fortiumpartners/ensemble/tooling-detector)<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>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.00000 | $0.02897 |
| Opus 5 | $0.00000 | $0.01448 |
| Sonnet 5 | $0.00000 | $0.00579 |
| Haiku 4.5 | $0.00000 | $0.00290 |
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.
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` 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.yamlfile (weight: 0.6) - Helm chart metadatavalues.yamlfile (weight: 0.3) - Default valuestemplates/directory (weight: 0.2) - Template manifests
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.
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.
- 3d ago First seen · 507 lines · 0 tokens per session scan C 76ab7a530cd4
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.
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'…
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…
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…
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.
atmos-sbom
Atmos SBOM provenance: CycloneDX and SPDX generation from vendor and Terraform evidence, coverage diagnostics, NTIA validation, and native CI workflow-artifact publication.
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…