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/matteblack9/coding-agent-fabric/setup-remote-workspacenpx skills add matteblack9/coding-agent-fabric --skill setup-remote-workspacegit clone --depth 1 https://github.com/matteblack9/coding-agent-fabricWrote 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/matteblack9/coding-agent-fabric/setup-remote-workspace)<a href="https://agentmods.dev/skills/matteblack9/coding-agent-fabric/setup-remote-workspace"><img src="https://agentmods.dev/badge/skills/matteblack9/coding-agent-fabric/setup-remote-workspace.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.00028 | $0.00970 |
| Opus 5 | $0.00014 | $0.00485 |
| Sonnet 5 | $0.00006 | $0.00194 |
| Haiku 4.5 | $0.00003 | $0.00097 |
Grade A, and why
setup-remote-workspace scanned grade A 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl http://$HOST:$LISTENER_PORT/health How it starts
The opening of the file, as written. The whole thing — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
setup-remote-workspace
When To Use
- One workspace of an existing project must run remotely while the rest stay local
- The user wants a remote listener bound to one explicit workspace id
- The project already exists locally, but a specific workspace should execute elsewhere
This skill uses the same listener model as setup-remote-project, but registration happens at the workspace level instead of for a whole project.
Runtime Adaptation
claudeVerifyclaude-agent-sdkis importable on the remote host.cursorVerifycursor-agentexists on the remote host and is authenticated.codexVerifycodexis installed on the remote host and works non-interactively.opencodeVerifyopencodeplus provider login are already available on the remote host.
Difference From setup-remote-project
| setup-remote-project | setup-remote-workspace | |
|---|---|---|
| Target | Entire project or top-level workspace registration | One specific workspace id |
| Registration | Project/workspace chosen directly | Project and workspace are collected separately |
| Best fit | Moving a whole remote codebase | Mixing local and remote workspaces inside one project |
Rules
- Never deploy or overwrite a remote listener without confirmation
- Present detected values as numbered choices whenever possible
- Use one port per remote workspace listener, even when multiple listeners share the same host
- Preserve runtime guidance files on the remote workspace:
AGENTS.md,CLAUDE.md,.claude/,.cursor/rules,.cursorrules,opencode.json,.opencode/
Procedure
1. Environment Preflight
Verify:
orchestrator.yamlexistsorchestrator/remote/contains the deployment utilities- current
remote_workspacesentries are reviewed so the new listener does not collide with existing host/port pairs sshorkubectlis available for deployment
2. Identify The Target
Collect:
- local project name
- workspace name
- final registration name in
project/workspaceformat
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 · 153 lines · 28 tokens per session scan A 2c487d2428cf
setup-remote-workspace is a skill published in the GitHub repository matteblack9/coding-agent-fabric (2 stars, last pushed 5mo ago), licensed MIT. It adds 28 tokens to every session and 970 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…
rule
Skill "rule" from x-cmd/x-cmd, covering rule — rules to rule, 核心命令, 规则文件格式, 示例 and 验证规则文件格式.
cve
Look up CVE records via x cve — cached, zero-API-key, daily xz TSV. Load for cve, vulnerability id, kev, epss, nvd, cvelist, or security advisory.
azmon-mirroredcatalogs-operations-cli
Brings Azure Monitor, Application Insights, and Log Analytics telemetry into Fabric as Eventhouse external delta tables and correlates it with business data. Use to onboard observability data, judge whether latency or availability affected revenue, or build a Real-Time dashboard and Operations Agent over it.
atmos-auth
Authentication and identity management: providers (SSO/SAML/OIDC/GCP/Atmos Pro), identities, keyring, identity chaining, login/exec/shell/console, and github/sts for private GitHub access.
terraform-search-import
Discover existing cloud resources using Terraform Search queries and bulk import them into Terraform management. Use when bringing unmanaged infrastructure under Terraform control, auditing cloud resources, or migrating to IaC.