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 oaustegard/claude-skills --skill check-toolsgit clone --depth 1 https://github.com/oaustegard/claude-skillsWrote 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/oaustegard/claude-skills/check-tools)<a href="https://agentmods.dev/skills/oaustegard/claude-skills/check-tools"><img src="https://agentmods.dev/badge/skills/oaustegard/claude-skills/check-tools/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/oaustegard/claude-skills/check-tools"><img src="https://agentmods.dev/badge/skills/oaustegard/claude-skills/check-tools.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00037 | $0.00613 |
| Opus 5 | $0.00018 | $0.00307 |
| Sonnet 5 | $0.00007 | $0.00123 |
| Haiku 4.5 | $0.00004 | $0.00061 |
Grade A, and why
check-tools scanned grade A 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
pip, node, npm, java, gcc, git, curl, awk, grep, gzip, tar, make, sed) is How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check Tools - Development Environment Validator
Reports which development tools are installed and at what version, grouped by ecosystem. Default behavior reports every tool without failing validation — suited to diverse PaaS/container environments where only a subset of ecosystems is expected to be present.
When to use
- Verifying a container or environment has the tools a task needs
- Troubleshooting a build failure that might be a missing dependency
- Documenting system requirements
- Onboarding: confirming a dev environment is ready
Running it
# Fast check with exit code (0 = all required core tools present)
bash assets/check-tools.sh
# Development tools only
bash assets/environment-diagnostic.sh tools
# System info: hardware, mounts, processes
bash assets/environment-diagnostic.sh system
# Complete diagnostic (tools + system + package inventories), written to a file
bash assets/environment-diagnostic.sh full /path/to/report.txt
check-tools.sh exits non-zero only when a required core tool (python3,
pip, node, npm, java, gcc, git, curl, awk, grep, gzip, tar, make, sed) is
missing. Every other tool is reported (✅ found / ⚠️ optional and missing) but
does not fail the run.
Required vs. optional, by ecosystem
| Ecosystem | Required | Optional |
|---|---|---|
| Python | python3, pip | python, uv, poetry, black, mypy, pytest, ruff |
| Node.js | node, npm | nvm, yarn, pnpm, eslint, prettier, chromedriver |
| Java | java | mvn, gradle |
| Go | — | go |
| Rust | — | rustc, cargo |
| C/C++ | gcc | clang, cmake, ninja, conan |
| Utilities | git, curl, awk, sed, grep, gzip, tar, make | jq, rg, tmux, yq, vim, nano |
Full per-tool version-check commands and installation notes live in
references/tool-categories.md.
Files
assets/check-tools.sh— fast validation script (exit codes, quick checks)assets/environment-diagnostic.sh— comprehensive diagnostic withtools/system/fullmodesreferences/tool-categories.md— detailed per-tool breakdown and installation instructions
What ships with it
5 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.
- yesterday Changed · -363 lines eecfb2c74b9a
- 11d ago First seen · 434 lines · 37 tokens per session scan A 0d89496963bd
check-tools is a skill published in the GitHub repository oaustegard/claude-skills (148 stars, last pushed yesterday), licensed MIT. It adds 37 tokens to every session and 613 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
dbr-logs
This skill should be used when the user asks to fetch, search, or analyze Databricks job logs. Trigger phrases include "job logs", "databricks logs", "executor logs", "driver logs", "spark job failed", "check logs for", "why did my job fail", "OOM error in job", "check run logs", or requests to debug a Databricks job…
logging-best-practices
Expert logging guidance based on Boris Tane's loggingsucks.com philosophy. Use when implementing logging, adding observability, debugging production issues, or reviewing code that includes log statements. Covers wide events architecture, structured logging, smart sampling, and high-cardinality field design.
spark-engineer
Use when writing Spark jobs, debugging performance issues, or configuring cluster settings for Apache Spark applications, distributed data processing pipelines, or big data workloads. Invoke to write DataFrame transformations, optimize Spark SQL queries, implement RDD pipelines, tune shuffle operations, configure…
debugging-wizard
Parses error messages, traces execution flow through stack traces, correlates log entries to identify failure points, and applies systematic hypothesis-driven methodology to isolate and resolve bugs. Use when investigating errors, analyzing stack traces, finding root causes of unexpected behavior, troubleshooting…
Reverse Engineering & Binary Analysis
Binary analysis, assembly interpretation, disassembly, decompilation, firmware RE, and protocol reverse engineering.
log-analyzer
A log-analysis helper that reads application and system logs to find unusual patterns and likely causes. Logs are records of events such as errors, requests, warnings, and service activity.