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/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/madappgang/magus/workspace-setup"><img src="https://agentmods.dev/badge/skills/madappgang/magus/workspace-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00054 | $0.02915 |
| Opus 5.5 | $0.00022 | $0.01166 |
| Sonnet 5.5 | $0.00011 | $0.00583 |
| Haiku 4.5 | $0.00005 | $0.00292 |
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 1mo 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 — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workspace Setup
Tmux workspace orchestration: startup scripts, dashboard archetypes, ambient monitoring, and one command across many hosts. Every tmux-mcp call addresses a numbered helper slot — a pane beside you in the user's window; the same number returns the same pane every time, and slot 1 is never your own pane. Windows and whole tmux sessions are not in this contract; where they are needed the step is marked [Bash].
1. Project Startup Script
One tmux session per project, named windows per concern. Windows and sessions are not in this contract, so the deliverable is a startup script the user runs and re-runs themselves — not a sequence of tool calls.
1. [Bash] tmux has-session -t myproject 2>/dev/null → exit 0 means it already exists
2. [if missing] generate the script below and hand it over
3. Report: "Workspace ready. Switch with: tmux switch-client -t myproject"
has-session is the only detection signal you need. mcp__plugin_terminal_mux__list-slots() lists the helper panes this agent has open — never the user's windows or panes, which this contract does not enumerate.
Four Hand-Off Patterns
| Pattern | When to use | How |
|---|---|---|
| A: Leave detached | Long background job | [Bash] tmux new-session -d -s "<name>" "<cmd>", give the attach command |
| B: Non-destructive inspect | User already in a workspace | capture-pane on a helper slot you opened; never their pane |
| C: Background build | User wants to keep working | [Bash] tmux new-session -d -s "build-job" "make all" |
| D: Extra pane here | User wants to stay where they are | A numbered slot — §2 |
Startup Script Artifact
Generate this and leave it for the user to re-run. Replace myproject and the path. Use named variables only — no positional arguments.
#!/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.
- 1mo ago Changed 72ded248f992
- 1mo ago Changed · -31 lines · +11 tokens per session 2b63ce5a1ee8
- 1mo ago First seen · 286 lines · 43 tokens per session scan A 2270894d0703
workspace-setup is a skill published in the GitHub repository MadAppGang/magus (13 stars, last pushed yesterday), licensed MIT. It adds 54 tokens to every session and 2,915 once invoked, about $0.0002 per session on Opus 5.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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.