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.
git clone --depth 1 https://github.com/studiomeyer-io/studiomeyer-marketplaceWrote 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/commands/studiomeyer-io/studiomeyer-marketplace/crew-workflow)<a href="https://agentmods.dev/commands/studiomeyer-io/studiomeyer-marketplace/crew-workflow"><img src="https://agentmods.dev/badge/commands/studiomeyer-io/studiomeyer-marketplace/crew-workflow/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/studiomeyer-io/studiomeyer-marketplace/crew-workflow"><img src="https://agentmods.dev/badge/commands/studiomeyer-io/studiomeyer-marketplace/crew-workflow.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00017 | $0.00255 |
| Opus 5 | $0.00009 | $0.00128 |
| Sonnet 5 | $0.00003 | $0.00051 |
| Haiku 4.5 | $0.00002 | $0.00026 |
Grade A, and why
crew-workflow 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.
What it actually says
Run a Crew workflow: $ARGUMENTS
- Parse the arguments. First token is the workflow name, rest is the input.
- Valid workflows:
- strategy-review: CEO → CFO → CTO evaluation of a strategy
- content-pipeline: CMO → Analyst → Creative content production
- product-launch: Analyst → PM → CEO → CMO → CTO full launch analysis
- If the workflow name is missing or invalid, call
crew_workflow_listto show options and stop. - Call
crew_workflow_runfrom thestudiomeyer-crewMCP server with:name: the workflow nameinput: the rest of the argument
- The server returns the chained prompts in order. Execute each persona's analysis sequentially, passing the previous persona's output as input to the next.
- At the end, produce a unified summary covering all perspectives.
This can take 2-4 turns depending on the workflow length. Keep the user informed of which persona is currently analyzing.
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 Changed a95e3f1b8293
- 9d ago First seen · 21 lines · 17 tokens per session scan A 21989fb9b609
crew-workflow is a command published in the GitHub repository studiomeyer-io/studiomeyer-marketplace (2 stars, last pushed 4d ago), licensed MIT. It adds 17 tokens to every session and 255 once invoked, about $0.0001 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-31.
Other commands, from other repositories
octo-schedule
Manage scheduled workflow jobs for the Claude Octopus scheduler.
octo-scheduler
Manage the Claude Octopus scheduled workflow runner daemon.
discover
Run a full product discovery cycle — from outcome definition through opportunity mapping, prioritisation, and experiment design. Use when the team isn't sure what to build next, or before writing a PRD for a complex feature space.
next
Read the active sprint’s current status. Refresh stale compilation using grainulator compile --dir or grainulator.compile. Use the resulting nextactions with the user’s current scope and authorization. Output only the two Auto and Manual lists below, with no recap, status counters or offer to continue. Continue useful…
linear-bulk
Apply the same change to many Linear issues at once. Dry-run by default.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.