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 Maximilien-ai/clawmax --skill workspace-lsgit clone --depth 1 https://github.com/Maximilien-ai/clawmaxWrote 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/maximilien-ai/clawmax/workspace-ls)<a href="https://agentmods.dev/skills/maximilien-ai/clawmax/workspace-ls"><img src="https://agentmods.dev/badge/skills/maximilien-ai/clawmax/workspace-ls.svg" alt="Measured on agentmods" 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.00048 | $0.00295 |
| Opus 5 | $0.00024 | $0.00148 |
| Sonnet 5 | $0.00010 | $0.00059 |
| Haiku 4.5 | $0.00005 | $0.00030 |
Grade A, and why
workspace-ls 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 8d 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.
What it actually says
Workspace Directory Listing
This skill lets you inspect your workspace directory structure.
Usage
Run ls -la or find on the workspace directories to see:
- Agent configurations (AGENTS/)
- Workflow definitions (WORKFLOWS/)
- Organization files (ORG/)
- Custom skills (SKILLS/custom/)
- System files (SYSTEM/)
Example Commands
# List workspace root
ls -la $OPENCLAW_WORKSPACE/
# List all agents
ls -la $OPENCLAW_WORKSPACE/AGENTS/
# List all workflows
ls -la $OPENCLAW_WORKSPACE/WORKFLOWS/
# Find all .md files
find $OPENCLAW_WORKSPACE -name "*.md" -maxdepth 3
# Check agent identity
cat $OPENCLAW_WORKSPACE/AGENTS/*/IDENTITY.md
When to Use
- After template apply: verify agents and workflows were created
- During debugging: check file permissions and structure
- For system tests: validate workspace state
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.
- 8d ago First seen · 52 lines · 48 tokens per session scan A 5dd16b018a6c
workspace-ls is a skill published in the GitHub repository Maximilien-ai/clawmax (94 stars, last pushed yesterday), licensed MIT. It adds 48 tokens to every session and 295 once invoked, about $0.0002 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
debug-failing-test
Debug a failing test using an iterative logging approach, then clean up and document the learning.
foundry-hosted-agent-validation
Step-by-step process for validating a Python Foundry hosted agent sample (under python/samples/04-hosting/foundry-hosted-agents/) end to end — running it locally (native runtime and azd ai agent run) and after deploying it to an Azure AI Foundry project with azd. Use this when asked to validate a hosted agent sample.
python-feature-lifecycle
Guidance for package and feature lifecycle in the Agent Framework Python codebase, including stage meanings, feature-stage decorators, feature enums, and how to move APIs from one stage to the next.
python-development
Coding standards, conventions, and patterns for developing Python code in the Agent Framework repository. Use this when writing or modifying Python source files in the python/ directory.
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
reverse-engineering-tools
Guide for reverse engineering protected games and anti-cheat components across user mode, kernel mode, and hypervisor-aware environments. Use this skill when analyzing drivers, IOCTL protocols, callback registration, injected-code artifacts, integrity checks, protected binaries, or debugging security-sensitive game…