get-available-resources

get-available-resources is a skill for Claude Code, Codex from agentlas-ai/agentlas-desktop. It costs 63 tokens per session (2,278 once invoked), scanned A, a copy of get-available-resources, Apache-2.0.

A local detector that reports the computing resources available to the current process, including CPU, memory, disk, scheduler, container, and accelerator limits.

In plain words
What is it for?
It helps plan resource-sensitive local workloads and produces a redacted JSON snapshot for conservative CPU, memory, storage, scheduler, and accelerator planning.
Why use it?
It distinguishes hardware that exists on a host from resources actually usable by a job or container. It avoids stress tests, large allocations, device changes, and revealing sensitive host details.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It helps plan resource-sensitive local workloads and produces a redacted JSON snapshot for conservative CPU, memory, storage, scheduler, and accelerator planning.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/agentlas-ai/agentlas-desktop/get-available-resources
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 agentlas-ai/agentlas-desktop --skill get-available-resources
Clone the repo
git clone --depth 1 https://github.com/agentlas-ai/agentlas-desktop

Made for: Claude Code, 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 get-available-resources

README.md
[![agentmods](https://agentmods.dev/badge/skills/agentlas-ai/agentlas-desktop/get-available-resources/github.svg)](https://agentmods.dev/skills/agentlas-ai/agentlas-desktop/get-available-resources)
Your own site
<a href="https://agentmods.dev/skills/agentlas-ai/agentlas-desktop/get-available-resources"><img src="https://agentmods.dev/badge/skills/agentlas-ai/agentlas-desktop/get-available-resources/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 get-available-resources

Your own site · 80×15
<a href="https://agentmods.dev/skills/agentlas-ai/agentlas-desktop/get-available-resources"><img src="https://agentmods.dev/badge/skills/agentlas-ai/agentlas-desktop/get-available-resources.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,278 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.
Origin 88% copy Near-identical to another mod 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.00063 $0.02278
Opus 5.5 $0.00025 $0.00911
Sonnet 5.5 $0.00013 $0.00456
Haiku 4.5 $0.00006 $0.00228

Measured 1mo ago against content hash 1ecca3aff630, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

get-available-resources 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.

The scan reads SKILL.md. This mod also ships 5 executable files (scripts/_common.py, scripts/accelerator_diagnostics.py, scripts/detect_resources.py, …), 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.

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.

Origin

This is a copy

88% identical to get-available-resources — 39 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

plugins/agentlas-science-skills/skills/get-available-resources/SKILL.md · 278 lines

How it starts

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

Get Available Resources

Build a conservative picture of resources available to the current process. Keep host inventory, process affinity, cgroup/container limits, scheduler allocation, and accelerator runtime usability separate.

Safety contract

Follow these rules:

  • Run detection when the user requests it or a specific workload needs resource planning. Do not persist a fingerprint for every scientific task.
  • Use stdout by default. Persist only when the user chooses an explicit generic local filename.
  • Do not run stress tests, benchmarks, large allocations, write probes, device resets, driver installation, or clock/power changes.
  • Do not dump the environment. Read only the named Slurm and accelerator variables implemented by the detector.
  • Do not report hostnames, absolute paths, cgroup paths, job IDs, device UUIDs, PCI addresses, or raw visibility-variable values.
  • Treat a missing observation as unknown. Never convert unknown to unlimited.
  • Never infer that a visible host CPU, memory pool, or GPU is usable inside a scheduler allocation or container.

The bundled detector uses only fixed executable/argument tuples, no shell, short timeouts, bounded stdout/stderr, and partial-failure warnings.

Quick start

Run from this skill directory.

Ephemeral stdout snapshot

python scripts/detect_resources.py

The command emits only JSON to stdout. Redirect it only when ordinary shell permissions are acceptable.

Explicit private file

python scripts/detect_resources.py --output resource-snapshot.json

Explicit output is restricted to one .json filename in the current directory, uses private permissions, rejects symlinks and path traversal, and refuses overwrite unless --force is supplied.

Optional psutil enhancement

The standard-library detector works without installation. For broader cross-platform physical-core, affinity, available-memory, swap, and disk coverage:

uv pip install "psutil==7.2.2"

Read the full file on GitHub · 278 lines

Files

What ships with it

8 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. 1mo ago First seen · 278 lines · 63 tokens per session scan A 1ecca3aff630

Subscribe to this mod's changes

get-available-resources is a skill published in the GitHub repository agentlas-ai/agentlas-desktop (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 63 tokens to every session and 2,278 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to get-available-resources, differing in 39 lines, and is treated as a copy.

Related

Other skills, from other repositories

winui-wpf-migration

Migrate or port a WPF app to WinUI 3: namespaces (System.Windows to Microsoft.UI.Xaml), control mapping (DataGrid, WrapPanel, TabControl), Dispatcher to DispatcherQueue, imaging, MVVM with CommunityToolkit.Mvvm, ThemeResource. Use when converting WPF code or fixing migration build errors.

microsoft/winappCli · 73 tokens

deploy-fullstack-vercel

Build and deploy a full-stack app (React frontend + Python/FastAPI backend) or a Vellum app to Vercel as a serverless demo with seeded data.

vellum-ai/vellum-assistant · 41 tokens

vercel-token-setup

Set up a Vercel API token for publishing apps using browser automation.

vellum-ai/vellum-assistant · 20 tokens

cua-spaces

Work inside cua Spaces through the cua MCP server. A Space is a remote or local computer the user can watch; you can run commands in it, move files in and out, show its desktop or a single window on the user's screen, start coding agents inside it, teleport a signed-in app session into it, and share the host's network…

trycua/cua · 102 tokens

electron-expert

Expert in Electron framework, desktop app development, IPC, and cross-platform packaging. Use when the user mentions desktop, Node.js, cross platform, Windows, macOS, or Linux, or when the task involves Electron Architecture, Process Types, IPC Communication, or App Lifecycle.

personamanagmentlayer/pcl · 59 tokens

ai-deployment-patterns

Guides expert-level ai deployment patterns implementation: ai-ml and devops decision frameworks, production-ready patterns, and concrete templates for ai deployment patterns workflows. Use when the user asks about ai deployment patterns, ai deployment patterns configuration, or ai-ml best practices for ai projects. Do…

FerroxLabs/wayland · 87 tokens