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 agentmods add skills/desirecore/market/configuring-computenpx skills add desirecore/market --skill configuring-computegit clone --depth 1 https://github.com/desirecore/marketWrote 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/desirecore/market/configuring-compute)<a href="https://agentmods.dev/skills/desirecore/market/configuring-compute"><img src="https://agentmods.dev/badge/skills/desirecore/market/configuring-compute.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 | $0.00080 | $0.01578 |
| Opus 5 | $0.00040 | $0.00789 |
| Sonnet 5 | $0.00016 | $0.00316 |
| Haiku 4.5 | $0.00008 | $0.00158 |
Grade A, and why
configuring-compute 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 4d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configure Compute
Configure DesireCore compute through governed tools. Do not call the local
/api/compute/* management endpoints from Bash, HttpRequest, or scripts: those
endpoints intentionally require a trusted renderer Origin and instance token.
Security contract
- API keys are write-only for agents. Never read
secrets.json, requestComputeCredential(action='get', raw=true), or repeat a key in tool results or chat. - Use
ComputeCredential(action='set')to create or replace the key of an existing user-managed provider. If the provider has no credential reference, the tool creates and attaches one without returning the plaintext. This path is approval-gated and audited; approval cards, tool events, receipts, and session history redact the sensitive value. System-managed credentials are not writable. - Pass a value to
ComputeCredential(action='set')only when the user already supplied the replacement key in the current request. If the agent must never handle the plaintext, use the GUI to focus the password field, let the user type into it directly, then continue the save flow. Never ask for the key in ordinary chat or read the masked field back into the model. credentialMode=nonemeans the provider needs no key. Ollama is treated asnoneeven when an older config does not declare the field.- If the user asks for the current key, explain that the agent can replace it but cannot read it back. The human-only UI reveal flow remains separate.
Workflow for an existing provider
First confirm ManageCompute is available through the current tool catalog. If
it is absent (for example on an older installed client), use the governed GUI
workflow below for the whole task; do not fall back to local HTTP.
- Call
ManageCompute(action='list'). Record the exact provider ID, enabled state, credential mode, status, and model count. - If credential mode is
requiredand the user supplied a new key in the current request, callComputeCredential(action='set', providerId=..., value=...). Do not echo the value. If the agent must not handle plaintext, use the human-entry GUI flow below. Fornone, skip this step. - Call
ManageCompute(action='set_enabled', providerId=..., enabled=true). - Call
ManageCompute(action='sync_models', providerId=...). For Ollama this discovers locally installed models; for supported cloud providers it merges the built-in model list. - Call
InspectModelsto verify the intended model is selectable. When the user asked for a real test, run one short fixed-model conversation and verify the run receipt names the requested provider/model.
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.
- 4d ago First seen · 134 lines · 80 tokens per session scan A 06a1881a74aa
configuring-compute is a skill published in the GitHub repository desirecore/market (2 stars, last pushed 4d ago), licensed MIT. It adds 80 tokens to every session and 1,578 once invoked, about $0.0004 per session on Opus 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-08-31.
Other skills, from other repositories
designing-architectures
Architecture knowledge reference covering API design, security architecture, cloud-native patterns, caching strategies, message queues, and data security. Use when designing system architecture, APIs, or cloud-native infrastructure.
data-distributed-compute
Use this skill when designing distributed compute for Hadoop MapReduce, Spark, Dask, Ray, YARN, or K8s resource management. This skill enforces: execution model selection, cluster topology, shuffle optimization, data locality, speculative execution, and resource tuning. Do NOT use for: single-node compute, GPU-only…
com.googleapis.compute-mcp-mcp
Provides capabilities that let LLM agents perform a range of infrastructure management tasks.
colab-remote
Orchestrate Google Colab Pro/Pro+ GPU instances as remote training backends via SSH. Compounds /agent-browser (to launch Colab sessions and install colab-ssh) with SSH (to operate the runtime remotely). Use when: (1) launching a Colab notebook for GPU training, (2) running training jobs on Colab from the local…
tao-run-on-kubernetes
Kubernetes execution platform — submits TAO container jobs as k8s Jobs with NVIDIA GPU scheduling; single-pod for one node, Indexed Jobs for multi-node distributed training. Use when running on EKS / GKE / AKS / on-prem clusters with the NVIDIA GPU Operator installed, or when integrating TAO into an existing…
configuration
Skill "configuration" from chaterm/terminal-skills, covering openclaw 配置管理, 概述, 核心配置文件, application.yml 结构 and /opt/openclaw/conf/application.yml.