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/monoes/monomindWrote 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/monoes/monomind/workflow-export)<a href="https://agentmods.dev/commands/monoes/monomind/workflow-export"><img src="https://agentmods.dev/badge/commands/monoes/monomind/workflow-export/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/monoes/monomind/workflow-export"><img src="https://agentmods.dev/badge/commands/monoes/monomind/workflow-export.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.00034 | $0.00527 |
| Opus 5.5 | $0.00014 | $0.00211 |
| Sonnet 5.5 | $0.00007 | $0.00105 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
workflows:workflow-export 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 yesterday.
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
Workflow Export
Inspect and export workflows. The CLI has no workflow command; the real equivalents operate on org configs (.monomind/orgs/<name>.json) and Mastermind procedures.
How to Invoke
Skill("workflows:workflow-export")
CLI Reference
# List orgs (workflows) in the project and their runtime state
npx monomind org list
npx monomind org status
# Validate one or all org configs
npx monomind org validate api-dev
npx monomind org validate
# Export an org's flow as a Mermaid diagram (latest run by default)
npx monomind org flow api-dev
npx monomind org flow api-dev --run <run-id>
# Summarize runs
npx monomind org report api-dev
npx monomind org report api-dev --all
npx monomind org report api-dev --by-role
npx monomind org report api-dev --format mermaid
# Portable step-by-step procedures for platforms without native skills
npx monomind mastermind --list
npx monomind mastermind run plan --print > plan-workflow.md
Sharing a Workflow
The org config is a plain JSON file, so it can be copied into another project's .monomind/orgs/ and checked with npx monomind org validate <name>. For a full archive with the org's data, use the mastermind-export skill (and mastermind-import on the other side).
Org Starter Templates
| Template | Roles |
|---|---|
dev-team |
tech-lead, developer, code-reviewer, qa |
research-pod |
lead-analyst, researcher, fact-checker |
content-team |
editor-in-chief, writer, reviewer |
kg-extraction |
kg-lead, entity-extractor, relationship-resolver, ontology-validator |
advisor-orchestrator |
advisor, worker-1, worker-2 |
Related Skills
workflows:workflow-execute— Run workflowsworkflows:workflow-create— Create a reusable workflowmastermind-export/mastermind-import— Org archives
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.
- yesterday First seen · 63 lines · 34 tokens per session scan A f8a90a6ef798
workflows:workflow-export is a command published in the GitHub repository monoes/monomind (23 stars, last pushed yesterday), licensed Apache-2.0. It adds 34 tokens to every session and 527 once invoked, about $0.0001 per session on Opus 5.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-10-26.
Other commands, from other repositories
multi-repo-swarm
Coordinate AI swarms across multiple repositories, enabling organization-wide automation and intelligent cross-project collaboration.
sync-coordinator
Multi-package synchronization and version alignment with ruv-swarm coordination for seamless integration between claude-code-flow and ruv-swarm packages.
auto-agent
Automatically spawn and manage agents based on task requirements.
jira
Retrieve a Jira ticket, analyze requirements, update status, or add comments. Uses the jira-integration skill and MCP or REST API.
bienvenida
Grupo: Rutina del día a día En una frase: Primera vez post-clone — checklist + mensaje de bienvenida con commands recomendados (incluye /setup si falta estructura). Cuándo: Justo después de clonar o abrir el DT por primera vez; la IA también puede mostrarlo sin invocación si no hay sesión local. Quién: Cualquier…
morning
The coffee report — cross-project map deltas, arrives on its own (scheduled).