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/development)<a href="https://agentmods.dev/commands/monoes/monomind/development"><img src="https://agentmods.dev/badge/commands/monoes/monomind/development/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/development"><img src="https://agentmods.dev/badge/commands/monoes/monomind/development.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.00038 | $0.00605 |
| Opus 5.5 | $0.00015 | $0.00242 |
| Sonnet 5.5 | $0.00008 | $0.00121 |
| Haiku 4.5 | $0.00004 | $0.00060 |
Grade A, and why
workflows:development 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Development Workflow Coordination
Structure multi-agent development work. The CLI has no workflow command; run the stages with the Task tool, or as a dev-team org.
How to Invoke
Skill("workflows:development")
Stages
- Planning — requirements, architecture decisions (
planner) - Implementation — code (
coder) - Testing — unit and integration tests (
tester, in parallel with implementation where the contract is known) - Review — quality and security (
reviewer,Security Engineer) - Integration — wire the pieces together, run the full build and test suite
In the Conversation (Task Tool)
// Stage 1
Task({ subagent_type: "planner", prompt: "Plan a REST API with JWT auth: endpoints, data model, files to touch." })
// Stages 2-3, one message
Task({ subagent_type: "coder", prompt: "Implement the plan in src/api/ ..." })
Task({ subagent_type: "tester", prompt: "Write tests for the endpoints defined in the plan ..." })
// Stage 4, one message
Task({ subagent_type: "reviewer", prompt: "Review the diff for correctness and maintainability." })
Task({ subagent_type: "Security Engineer", prompt: "Review the auth code for vulnerabilities." })
Optional tracking:
npx monomind hooks pre-task --description "Build REST API with auth" --task-id rest-api
npx monomind hooks post-task --task-id rest-api --success true
npx monomind memory store --key "dev-pattern-rest-api" \
--value "JWT auth + Express + Zod validation worked well" --namespace patterns
As an Org
npx monomind org create rest-api --template dev-team --goal "Build REST API with auth"
npx monomind org run rest-api --dry-run
npx monomind org run rest-api
npx monomind org report rest-api
The dev-team template has tech-lead, developer, code-reviewer, and qa roles.
What Claude Code Actually Does
- Read/Write/Edit — create and modify files
- Bash — run tests, builds, type checks
- TodoWrite — track stages
- Task — spawn parallel agents
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 · 72 lines · 38 tokens per session scan A f7cd0a660ab1
workflows:development is a command published in the GitHub repository monoes/monomind (23 stars, last pushed yesterday), licensed Apache-2.0. It adds 38 tokens to every session and 605 once invoked, about $0.0002 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
pr-enhance
Command "pr-enhance" from ruvnet/ruflo, covering pr-enhance, usage, options, examples and enhance pr.
dart-mechanical-refactor
perform a behavior-preserving mechanical refactor.
pr
Automated PR code quality review with language-aware analysis and project-specific profiles.
refactor-sprint
Parallel refactor sprint — fires refactor-cleaner + code-simplifier + type-design-analyzer + tdd-guide simultaneously. Full cleanup in one pass.
test-coverage
Analyze test coverage, identify gaps, and generate missing tests to reach 80% project / 90% touched.
py-challenge-patches
You're a senior software engineer and care about the long term health of this project. Test coverage is important but tests should be legible and valuable and should be testing implementation and mocks.