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 CloudChef/atlasclaw-providers --skill requestgit clone --depth 1 https://github.com/CloudChef/atlasclaw-providersWrote 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/cloudchef/atlasclaw-providers/request)<a href="https://agentmods.dev/skills/cloudchef/atlasclaw-providers/request"><img src="https://agentmods.dev/badge/skills/cloudchef/atlasclaw-providers/request/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/cloudchef/atlasclaw-providers/request"><img src="https://agentmods.dev/badge/skills/cloudchef/atlasclaw-providers/request.svg" alt="Reviewed on agentmods" width="80" 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.00068 | $0.14895 |
| Opus 5.5 | $0.00027 | $0.05958 |
| Sonnet 5.5 | $0.00014 | $0.02979 |
| Haiku 4.5 | $0.00007 | $0.01490 |
Grade C, and why
request 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 1mo 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.
Harvests environment variableshighData exfiltration
Enumerating or grepping the environment for keys collects credentials unrelated to what the mod says it does.
call submit. Collect the secret again, display a new masked preview, and ask How it starts
The opening of the file, as written. The whole thing — 1,233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
request
Submit cloud resource, application environment, or ticket/work order requests through the service catalog.
Flow
The request workflow owns request-projected
smartcmp_list_logical_templates and smartcmp_list_images tools. They reuse
the same read-only scripts as the datasource global-query tools, but remain
visible when AtlasClaw projects only the cmp.request capability.
Multi-resource routing boundary
This skill is for one CMP request flow at a time. That single flow may still represent one service catalog / one resource type / one shared parameter set with quantity N.
Keep the request in this skill when the user wants multiple instances of the same resource type with the same configuration, for example:
- "several identical Linux VMs for one project"
- "multiple instances of the same database service with shared parameters"
- "quantity N of one resource type with one shared parameter set"
Route to request-decomposition-agent only when the request needs to be split
into distinct sub-requests, especially when the user gives:
- multiple resource types in one ask
- per-instance differences such as "first ..., second ..., third ..."
- different specs per instance
- mixed roles/components that should become separate CMP requests
Quantity by itself is not a decomposition signal. The request workflow and
submit tool should interpret same-type quantity from the user's original
language without requiring AtlasClaw core to pre-structure resource_count.
When this boundary is hit, do not continue with the single-catalog parameter collection flow in this skill.
Single-instance vs shared-quantity contract
This skill supports two request shapes, and they are not interchangeable:
- Single-instance request: one resource type, one instance, one
resourceSpecsitem, and no top-level count field unless the selected catalog explicitly requires one. - Same-type multi-instance request: one resource type, one shared
parameter set, one explicit quantity value from the selected catalog schema
or fallback
quantity, withresourceSpecsfollowing the selected catalog schema.
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.
- 1mo ago First seen · 1,233 lines · 68 tokens per session scan C 60e0c79ac308
request is a skill published in the GitHub repository CloudChef/atlasclaw-providers (17 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 68 tokens to every session and 14,895 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it C with 1 finding (harvests environment variables). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
add-linear
Add Linear channel integration via Chat SDK. Issue comment threads as conversations.
mission-control
Interact with Mission Control — AI agent orchestration dashboard. Use when registering agents, managing tasks, syncing skills, or querying agent/task status via MC APIs.
task-management
Use before any Worker taskflow call or assigned-task workflow, including reading task state, acknowledging a task, executing a task, tracking progress, handling blockers/questions, submitting structured results, or reporting completion. Always use this skill when the message mentions assigned task, task ID…
task-coordination
Coordinate access to shared task directories using .processing marker files. Use before accessing a Worker's workspace to prevent conflicts when both Manager and Worker might modify files simultaneously.
team-management
Use when admin requests creating a team, importing a team, managing team composition, adding/removing workers from a team, or delegating tasks to a Team Leader.
project-management
Use when admin asks to start a multi-worker project, when a Worker @mentions you with task completion in a project room, when project plan changes are needed, or when a blocked task needs resolution.