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 MadAppGang/magus --skill workspace-setupgit clone --depth 1 https://github.com/MadAppGang/magusWrote 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/madappgang/magus/workspace-setup)<a href="https://agentmods.dev/skills/madappgang/magus/workspace-setup"><img src="https://agentmods.dev/badge/skills/madappgang/magus/workspace-setup.svg" alt="Measured on agentmods" 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.00043 | $0.02754 |
| Opus 5 | $0.00022 | $0.01377 |
| Sonnet 5 | $0.00009 | $0.00551 |
| Haiku 4.5 | $0.00004 | $0.00275 |
Grade A, and why
workspace-setup scanned grade A 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
watch -n1 'curl -s localhost:3000/health' # health probe How it starts
The opening of the file, as written. The whole thing — 286 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workspace Setup
Tmux workspace orchestration: session construction, dashboard archetypes, ambient monitoring, and multi-host pane synchronization.
1. Session Workspace Construction
One tmux session per project, named windows per concern.
Windows are not in the agentic MCP scope.
create-window,kill-window,resize-paneandrename-sessionexist in the tmux-mcp binary but are hidden at-scope agentic, which is what this plugin ships. Building a multi-window session is therefore a Bash job — use the startup script below, which is what you should be handing the user anyway. Multi-pane work needs no Bash at all; see §2.
Session Construction Tool Sequence
1. mcp__tmux__list-sessions() → scan for a session named "project"
// find-session was removed from the Go binary; filter client-side
2. [if not found] mcp__tmux__create-session({ name: "project" })
3. Windows: generate the startup script below and let the user run it —
window creation is not available at this scope.
4. Report: "Workspace ready. Switch with: tmux switch-client -t project"
Four Hand-Off Patterns
| Pattern | When to use | How |
|---|---|---|
| A: Leave detached | Long background job | Create session, give the attach command |
| B: Non-destructive inspect | User already in a session | capture-pane without touching anything |
| C: Background build | User wants to keep working | tmux new-session -d -s "build-job" "make all" |
| D: Extra pane here | User wants to stay where they are | A numbered slot — §2 |
Session Startup Script Artifact
Generate this and leave it for the user to re-run. Replace myproject and the path.
#!/bin/bash
SESSION="myproject"
ROOT="$HOME/projects/myproject"
tmux new-session -d -s "$SESSION" -n "server" -c "$ROOT"
tmux send-keys -t "$SESSION:server" "bun run dev" Enter
tmux new-window -t "$SESSION" -n "tests" -c "$ROOT"
tmux send-keys -t "$SESSION:tests" "bun test --watch" Enter
tmux new-window -t "$SESSION" -n "git" -c "$ROOT"
tmux send-keys -t "$SESSION:git" "lazygit" Enter
tmux select-window -t "$SESSION:server"
tmux attach-session -t "$SESSION"
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 · 286 lines · 43 tokens per session scan A 2270894d0703
workspace-setup is a skill published in the GitHub repository MadAppGang/magus (9 stars, last pushed 2d ago), licensed MIT. It adds 43 tokens to every session and 2,754 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.