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.
npx skills add monoes/monomind --skill mastermind-workspacesgit 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/skills/monoes/monomind/mastermind-workspaces)<a href="https://agentmods.dev/skills/monoes/monomind/mastermind-workspaces"><img src="https://agentmods.dev/badge/skills/monoes/monomind/mastermind-workspaces/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/skills/monoes/monomind/mastermind-workspaces"><img src="https://agentmods.dev/badge/skills/monoes/monomind/mastermind-workspaces.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.00045 | $0.02578 |
| Opus 5.5 | $0.00018 | $0.01031 |
| Sonnet 5.5 | $0.00009 | $0.00516 |
| Haiku 4.5 | $0.00005 | $0.00258 |
Grade A, and why
mastermind-workspaces 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mastermind Workspaces
This skill is invoked directly via /mastermind-workspaces.
Inputs
brain_context: BRAIN CONTEXT block (injected by command, or loaded below if standalone)org_name: org to manage workspaces for (required)action: list | status | attach | detach | stop | pruneworkspace_id: workspace id (required for status/detach/stop)project_id: project to filter by (optional for list)agent_id: agent to assign to workspace (required for attach)worktree_path: filesystem path of the worktree (required for attach)caller: command | master
Workspace Model
A workspace is a git worktree assigned to a project, optionally running services and assigned to an agent.
{
"id": "ws-abc123",
"project_id": "project-slug",
"agent_id": "backend-dev",
"worktree_path": "/tmp/monomind/worktrees/project-slug-abc123",
"branch": "feat/my-feature",
"status": "active",
"services": ["dev-server", "db-watcher"],
"createdAt": "2026-01-01T00:00:00Z",
"lastActiveAt": "2026-01-02T00:00:00Z"
}
Step 0 — Brain Load (standalone only)
If caller is not "command", load brain context following mastermind-protocol/SKILL.md Brain Load Procedure with namespace: ops.
Step 1 — Load Workspace Data
orgFile=".monomind/orgs/${org_name}.json"
[ ! -f "$orgFile" ] && { echo "ERROR: Org '${org_name}' not found."; exit 1; }
wsFile=".monomind/orgs/${org_name}-workspaces.json"
[ ! -f "$wsFile" ] && echo '{"workspaces":[]}' > "$wsFile"
projectsFile=".monomind/orgs/${org_name}-projects.json"
worktreeRegistry=".monomind/orgs/${org_name}-worktrees.json"
Step 2 — Execute Action
list (default)
echo "WORKSPACES — org: $org_name"
[ -n "$project_id" ] && echo "(filtered by project: $project_id)"
echo "────────────────────────────────────────────────────────"
total=$(jq '.workspaces | length' "$wsFile")
if [ "$total" -eq 0 ]; then
echo " No workspaces. Use --action attach to register one."
else
# Group by project
projects=$(jq -r --arg pid "${project_id:-}" '
.workspaces |
if $pid != "" then map(select(.project_id == $pid)) else . end |
[.[].project_id] | unique[]
' "$wsFile")
while IFS= read -r proj; do
[ -z "$proj" ] && continue
projName=$([ -f "$projectsFile" ] && jq -r --arg pid "$proj" '(.projects // [])[] | select(.id == $pid) | .name // $pid' "$projectsFile" || echo "$proj")
echo ""
echo " PROJECT: $projName"
echo " ──────────────────────────────────────────────────"
printf " %-18s %-14s %-18s %-12s %-6s %s\n" "ID" "STATUS" "AGENT" "BRANCH" "SVCS" "PATH"
jq -r --arg pid "$proj" '(.workspaces // [])[] | select(.project_id == $pid) |
[.id, (.status // "unknown"), (.agent_id // "(none)"),
(.branch // "?"), ((.services // []) | length | tostring),
(.worktree_path // "-")]
| @tsv' "$wsFile" | while IFS=$'\t' read -r id st ag br svc path; do
printf " %-18s %-14s %-18s %-12s %-6s %s\n" "$id" "$st" "$ag" "$br" "$svc" "$path"
done
done <<< "$projects"
fi
echo ""
echo "Total: $total workspace(s)"
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.
- 2d ago First seen · 263 lines · 45 tokens per session scan A 9a4d519dd27d
mastermind-workspaces is a skill published in the GitHub repository monoes/monomind (23 stars, last pushed 2d ago), licensed Apache-2.0. It adds 45 tokens to every session and 2,578 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 skills, from other repositories
agent-sync-coordinator
Agent skill for sync-coordinator - invoke with $agent-sync-coordinator.
publish-harness
Publish a generated harness to npm — runs the smoke test, signs the witness manifest, and dispatches npm publish --provenance from your tagged release.
issue-triage
Sort a backlog of issues and pull requests: label each by type and severity, link duplicates, try the bug reports, ask for the one missing detail, and turn the accepted ones into ready-to-work briefs.
implement-issue
Implement a GitHub issue or GitLab issue and create a PR/MR.
triage
Triage a GitHub repository's open issues by finding exact duplicates, rejecting evidenceably off-base requests, requesting concrete clarification, applying only existing labels, and opening a linked root-cause issue when multiple reports share one underlying invariant failure. Use when a maintainer asks to triage…
jira
Jira integration — view issues, generate branches, create tickets, transition status. Use when: user mentions Jira ticket key (XX-123), says /jira, wants to create branch from ticket, create a new ticket, or update Jira status. Not for: GitHub issues (use issue-analyze).