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-create)<a href="https://agentmods.dev/commands/monoes/monomind/workflow-create"><img src="https://agentmods.dev/badge/commands/monoes/monomind/workflow-create/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-create"><img src="https://agentmods.dev/badge/commands/monoes/monomind/workflow-create.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.00030 | $0.00652 |
| Opus 5.5 | $0.00012 | $0.00261 |
| Sonnet 5.5 | $0.00006 | $0.00130 |
| Haiku 4.5 | $0.00003 | $0.00065 |
Grade A, and why
workflows:workflow-create 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.
How it starts
The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow Create
Create a reusable workflow. The CLI has no workflow command; a reusable workflow is an org config in .monomind/orgs/<name>.json.
How to Invoke
Skill("workflows:workflow-create")
CLI Reference
# Scaffold from a starter template
npx monomind org create api-dev --template dev-team --goal "Deliver API features from the backlog"
# Scheduled workflow (hosted by `org serve`)
npx monomind org create weekly-brief --template research-pod --goal "Weekly AI tooling brief" --schedule 2h
# Overwrite an existing config
npx monomind org create api-dev --template dev-team --force
# Validate after editing the JSON
npx monomind org validate api-dev
# List orgs in the project
npx monomind org list
org create Flags
| Flag | Description |
|---|---|
--template |
content-team | dev-team | research-pod | kg-extraction | advisor-orchestrator |
--goal |
Org goal (defaults to the template's placeholder) |
--schedule |
Daemon schedule, e.g. 30m or 2h |
--force |
Overwrite an existing org config |
-y, --yes |
Skip the per-role model confirmation prompt |
Workflow
-
Scaffold from the closest template:
npx monomind org create auth-flow --template dev-team --goal "Build auth features" -
Edit
.monomind/orgs/auth-flow.json— adjust roles, responsibilities, and models. For a guided design, use themastermind-createorgskill; to add a role, usemastermind-new-agent. -
Validate and preview:
npx monomind org validate auth-flow npx monomind org run auth-flow --dry-run -
Reuse it:
npx monomind org run auth-flow --task "Add password reset"
In-Conversation Alternative
For a one-off workflow, no config is needed: write the stages as a TodoWrite list and spawn Task-tool agents per stage (see workflows:workflow-execute). To keep the pattern for later:
npx monomind memory store --key "workflow-auth" \
--value "plan (planner) -> implement+test in parallel (coder, tester) -> review (reviewer)" \
--namespace patterns
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 · 82 lines · 30 tokens per session scan A eb62468f3d51
workflows:workflow-create is a command published in the GitHub repository monoes/monomind (23 stars, last pushed yesterday), licensed Apache-2.0. It adds 30 tokens to every session and 652 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).