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-monotaskgit 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-monotask)<a href="https://agentmods.dev/skills/monoes/monomind/mastermind-monotask"><img src="https://agentmods.dev/badge/skills/monoes/monomind/mastermind-monotask/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-monotask"><img src="https://agentmods.dev/badge/skills/monoes/monomind/mastermind-monotask.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.00040 | $0.03040 |
| Opus 5.5 | $0.00016 | $0.01216 |
| Sonnet 5.5 | $0.00008 | $0.00608 |
| Haiku 4.5 | $0.00004 | $0.00304 |
Grade C, and why
mastermind-monotask scanned grade C with 1 finding 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.
Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
monotask profile import-ssh-key ~/.ssh/id_ed25519 # changes pubkey — run before joining spaces How it starts
The opening of the file, as written. The whole thing — 351 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monotask CLI — Agent Reference (v1.1.4)
Monotask is a P2P local-first task manager. All data is stored in SQLite (~/.local/share/monotask/monotask.db). Always use --json for machine-readable output.
Global Flags
--data-dir <PATH> Override storage directory (must be consistent per instance)
Board
# Create — returns {id, title, deep_link}
monotask board create "Sprint 42" --json
# List — returns [{id, title}] (search by title with jq .title)
monotask board list --json
# Rename
monotask board rename <BOARD_ID> "New Title" --json
Column
# Create — returns {id, board_id}
monotask column create <BOARD_ID> "Todo" --json
# List — returns [{id, title, card_ids:[]}] ← field is "title", NOT "name"
monotask column list <BOARD_ID> --json
# Rename
monotask column rename <BOARD_ID> <COL_ID> "New Title" --json
# Delete (soft-deletes all cards in it)
monotask column delete <BOARD_ID> <COL_ID> --json
Card
Listing
# All cards in board (flat, includes col_id + col_title per card)
monotask card list <BOARD_ID> --json
# Filter by column (server-side, fast)
monotask card list <BOARD_ID> --col <COL_ID> --json
# Filter by label (server-side, exact match)
monotask card list <BOARD_ID> --label "role:writer" --json
# Combine filters
monotask card list <BOARD_ID> --col <TODO_COL> --label "role:reviewer" --json
JSON schema per item from card list:
{ "id":"<uuid>", "title":"<str>", "col_id":"<uuid>", "col_title":"<str>",
"labels":[], "due_date":null, "impact":null, "effort":null, "direct_priority":null }
Create / View / Move
# Create — returns {id, title, board_id, number}
CARD=$(monotask card create <BOARD_ID> <COL_ID> "Task title" --json | jq -r .id)
# View full card (includes parent + subtasks)
monotask card view <BOARD_ID> <CARD_ID> --json
# Move to different column (auto-detects current column)
monotask card move <BOARD_ID> <CARD_ID> <TO_COL_ID> --json
# Copy to another column (same board)
monotask card copy <BOARD_ID> <CARD_ID> <TARGET_COL_ID> --json
# Rename
monotask card rename <BOARD_ID> <CARD_ID> "New title" --json
# Soft-delete (hidden from all views)
monotask card delete <BOARD_ID> <CARD_ID> --json
# Soft-archive (hidden from normal views)
monotask card archive <BOARD_ID> <CARD_ID> --json
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 · 351 lines · 40 tokens per session scan C 3ce15efc7966
mastermind-monotask is a skill published in the GitHub repository monoes/monomind (23 stars, last pushed 2d ago), licensed Apache-2.0. It adds 40 tokens to every session and 3,040 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 1 finding (reaches for credential files). 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-swarm-issue
Agent skill for swarm-issue - invoke with $agent-swarm-issue.
agent-user-tools
Agent skill for user-tools - invoke with $agent-user-tools.
queue-handoff
Use when ending a turn, finishing a slice, blocked on another agent's work, or escalating to a human — durable work handoff via queue items so the system keeps moving across compactions, missed messages, and interruptions. Covers the hot-potato terminal-turn-rule (active work ends by passing the ball, not by going…
diag-harness
Kernel-version skew check (ADR-027). Reports manifest surface + manifest kernel + installed kernel + verdict (match/patch-diff/minor-diff/major-diff). Exits 1 on minor/major skew with a copy-pasteable npm install @metaharness/[email protected] next step. Exits 2 if no .harness/manifest.json at path.
score-harness
5-dimension scorecard (0-100, grade A/B/C/F) for a scaffolded harness. Dimensions: Repo understanding (25%), Agent usefulness (25%), MCP safety (20%), Test coverage (15%), Publish readiness (15%). Emits a 6-field badges block (score + mcpRisk + 4 booleans) ready for the harness README. Exit 0 A/B, 1 C, 2 F.
verify-witness
Verify the Ed25519 witness manifest of a scaffolded harness. Fast yes/no signature check that proves the publisher signed this exact file set — separate from the full release-readiness umbrella in validate-harness.