shouldn't this be (files/join user-plugins-dir name)? You should probably also run name through munge-plugin-name. That said, you should probably also look into (::dir object/*behavior-meta*). That is set for plugin calls to the plugin directory. The only use case I can see (besides being a more discoverable name, which is valid in my opinion), would be inter-plugin file access, and I'm not sure how I feel about providing API for that It seems like the other plugin should provide sufficient API for your plugin to interact with.