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/zjunlp/skillnet/alfworld-device-operatornpx skills add zjunlp/SkillNet --skill alfworld-device-operatorgit clone --depth 1 https://github.com/zjunlp/SkillNetWrote 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/zjunlp/skillnet/alfworld-device-operator)<a href="https://agentmods.dev/skills/zjunlp/skillnet/alfworld-device-operator"><img src="https://agentmods.dev/badge/skills/zjunlp/skillnet/alfworld-device-operator.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.00093 | $0.00976 |
| Opus 5 | $0.00046 | $0.00488 |
| Sonnet 5 | $0.00019 | $0.00195 |
| Haiku 4.5 | $0.00009 | $0.00098 |
Grade A, and why
alfworld-device-operator 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Instructions
1. Skill Trigger
Activate this skill when the task goal explicitly requires using a device or appliance to interact with a target object. Common indicators include phrases like:
- "look at [object] under the [device]"
- "heat [object] with [device]"
- "cool [object] with [device]"
- "clean [object] with [device]"
2. Core Execution Flow
Follow this sequence when the skill is triggered:
Phase 1: Locate the Device
- Identify the device from the task description (e.g.,
desklamp,microwave,fridge). - Search common receptacles where such a device is typically found (e.g., desks, sidetables, countertops).
- Use the
go to {recep}action to navigate to and inspect these locations until the device is found. - Note the device's exact name (e.g.,
desklamp 1).
Phase 2: Locate the Target Object
- Identify the target object from the task description (e.g.,
laptop,mug,plate). - Search the environment for this object. It may not be near the device initially.
- Use the
go to {recep}and visual inspection to find the object. - Once found, use
take {obj} from {recep}to pick it up.
Phase 3: Co-locate Object and Device
- Navigate to the receptacle where the target device is located using
go to {recep}. - Ensure you are in the same location as the device before proceeding.
Phase 4: Operate the Device
- Execute the final use action. The specific action is determined by the device-object pair:
- For a
desklampand a viewable object (like alaptop,book), use:toggle {device} {recep}. - For a
microwaveand a heatable object, use:heat {obj} with {device}. - For a
fridgeand a coolable object, use:cool {obj} with {device}. - For a
faucet/spraybottleand a cleanable object, use:clean {obj} with {device}.
- For a
- Action Format: The action must use the exact object and device names discovered during Phases 1 & 2.
3. Key Assumptions & Rules
- Co-location Required: The skill assumes the final action requires the target object and the operating device to be in the same location (on the same receptacle).
- Device First: Prioritize finding the device before extensively searching for the target object, as the device's location is often a fixed landmark.
- Invalid Actions: If the environment responds with "Nothing happened," re-evaluate your object/device names and your location. Ensure you are using the correct action verb for the device type.
What ships with it
1 file 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 · 66 lines · 93 tokens per session scan A 61e52e1fb950
alfworld-device-operator is a skill published in the GitHub repository zjunlp/SkillNet (1,253 stars, last pushed 14d ago), licensed MIT. It adds 93 tokens to every session and 976 once invoked, about $0.0005 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-30.
Other skills, from other repositories
skill-creator
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Total_Fees_Calculation
Skill for computing total payment processing fees for a merchant over a specific day, date range, or month in the dabstep dataset. Use this skill whenever the question asks for "total fees", "fees paid", or "fees charged" for a merchant over some time period. The computation requires matching each transaction to a fee…
ddr-globem-analysis
Analyze a specific participant's longitudinal passive-sensing and psychological data in the GLOBEM digital depression research dataset. Use this skill whenever the task involves: analyzing a user's mental health or behavioral data from wearables/smartphones, generating QA pairs about behavioral/psychological changes…
applicable-fee-ids
Solve questions about which fee IDs apply to a payment merchant, transaction characteristics, or time period in the dabstep dataset. Use this skill for any question asking "which fee IDs apply to X", "what are the applicable fee IDs for merchant Y", "which merchants are affected by fee Z", or any query involving…
Fee_Delta_and_Impact_Simulation
Solve dabstep FeeDeltaandImpactSimulation questions: computing fee deltas when a fee's rate changes, and identifying which merchants are affected by fee rule changes. Use when asked about fee impact, delta payments, rate changes, or which merchants would be affected by modifying a fee rule.
mimic-iv-patient-analysis
Comprehensive strategy for analyzing individual patient records in MIMIC-IV EHR database and generating high-quality, diverse QA pairs. Use this skill whenever the task involves analyzing a specific patient's clinical data from MIMIC-IV (or similar EHR databases), querying across hospital and ICU tables, and…