Content rules for shared crews
Workspaces on Pro, Team and Enterprise can share a crew to the community marketplace once a workspace admin turns on public sharing, and every listing is reviewed before it goes live. Browsing and installing are free for everyone. These are the rules a listing has to follow — in plain words, one sentence each. Effective 20 September 2026.
The eight rules
No secrets
Never include API keys, tokens, passwords or private keys — the automated check blocks them, and a listing is public once approved.
Nothing private
Do not point at your own servers, internal hostnames, private IPs or anyone’s confidential documents.
Safe by default
Every crew is published in advise mode; do not instruct it to run destructive commands, hide things from the user or work around its permissions.
Say what it does
The title, tagline and description must describe what the crew actually does — no placeholders, no unfinished text, no misleading claims.
Nothing harmful
No hateful, harassing, sexual or illegal content, and nothing designed to deceive or harm the people who install it.
One listing per crew
Update your existing listing instead of submitting a near-copy, and do not re-list someone else’s crew as your own.
Reports are taken seriously
Anyone can report a listing; three reports hide it until a reviewer looks, and listings that break these rules are removed.
What is checked automatically
Before a reviewer sees a submission, it runs through a fixed set of checks. A failed check blocks the submission and says what to fix; a warning goes through and is shown to the reviewer.
- SecretsBlocks
API keys, tokens, private keys and password-style assignments anywhere in the listing.
- Private hostsBlocks
localhost, private IP ranges, internal domains and your own workspace’s hostnames. Other unrecognised links are flagged for the reviewer.
- SizeBlocks
A persona over 64 KB, more than 20 skills on a persona, or a skill over 32 KB. A very long description (over 8 KB) is only flagged.
- Submission limitsBlocks
Up to 10 submissions per workspace per day and up to 50 personas per listing. Each new version is reviewed again before it goes live.
- Destructive commandsBlocks
Instructions such as rm -rf /, curl … | sh or a fork bomb. Prompt-injection phrases are flagged, not blocked.
- Execute modeFlags
A persona set to execute is published in advise mode; people who install it can switch it on afterwards.
- Unfinished textFlags
Instructions under 200 characters, or containing TODO / lorem ipsum.
- Near-duplicatesFlags
A title almost identical to an existing listing, or the same set of personas.
What publishing does to your crew
Three things are true of every approved crew, and none of them is a surprise on either side.
- It is published in advise mode: its instructions tell it to comment and suggest rather than change things, whatever mode you built it in. If it was approved with extra tools (for example Bash or Write), it can use them, and those tools are listed on its page before anyone installs it.
- The tools it asks for are kept, not removed. If your crew needs to run commands, write files or reach the network, say so in the crew — the request goes to the reviewer with your submission, and the approval is an approval of those tools.
- Everything it can do is written on the listing, next to each crew by name, above the install button. Nobody installs a crew that can run a shell thinking it can only read.
The license
Every community listing is published under the MIT License. In short:
- Anyone may use, modify and redistribute this crew, free of charge, anywhere — in AgentTask, in Claude Code, or in any other tool.
- Keep the copyright line and the license text with any copy you pass on. That is the one condition.
- It comes with no warranty: the publisher and AgentTask promise nothing about whether it works for you.
MIT permits resale, so anyone may sell a crew they obtained here. Installing writes a LICENSE file naming the publisher alongside the crew files. Read the full license