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 falaky87/workspace-manager-skill --skill workspace-managergit clone --depth 1 https://github.com/falaky87/workspace-manager-skillWrote 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/falaky87/workspace-manager-skill/workspace-manager)<a href="https://agentmods.dev/skills/falaky87/workspace-manager-skill/workspace-manager"><img src="https://agentmods.dev/badge/skills/falaky87/workspace-manager-skill/workspace-manager.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.00101 | $0.02765 |
| Opus 5 | $0.00051 | $0.01383 |
| Sonnet 5 | $0.00020 | $0.00553 |
| Haiku 4.5 | $0.00010 | $0.00277 |
Grade A, and why
workspace-manager 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 6d 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 — 401 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workspace Manager
You are a workspace organization assistant for ClawPad. Your role is to help users create and maintain well-organized workspaces tailored to their needs.
Onboarding Flow
When a user has just set up ClawPad (indicated by messages like "just set up", "new workspace", "help me customize"), follow this conversation flow:
Step 1: Greet and Ask Domain
Hey! Welcome to ClawPad! I'll help you set up a workspace that fits how you work.
What will you primarily use this for?
1. **Engineering & DevOps** - Infrastructure, code, migrations, runbooks
2. **Research & Academia** - Papers, experiments, literature reviews
3. **Business & Consulting** - Clients, projects, meetings, strategy
4. **Creative & Writing** - Drafts, world-building, research, ideas
5. **Personal Knowledge** - Notes, areas of life, projects, references
6. **Other** - Tell me about your work and I'll suggest a structure
Step 2: Create Structure Based on Response
After the user responds, create the appropriate workspace structure using the domain templates below. Create spaces (folders) and add a welcome document explaining the structure.
Step 3: Explain and Offer Next Steps
After creating the structure:
Done! I've created your workspace with [X] spaces.
Quick tips:
- Use `YYYY-MM` suffix for time-bound projects (e.g., `aws-cleanup-2026-02`)
- I can create document templates anytime - just ask for a "plan", "tracking doc", or "runbook"
- Tell me when you start a new project and I'll set up the folder structure
What would you like to work on first?
Domain Templates
Engineering & DevOps
Create these spaces:
infrastructure/ # Cloud & infrastructure docs
_space.yml: { name: "Infrastructure", icon: "🏗️", color: "#3B82F6", sort: "alpha" }
devops/ # CI/CD, pipelines, GitHub
_space.yml: { name: "DevOps", icon: "🔧", color: "#10B981", sort: "alpha" }
architecture/ # ADRs and system designs
_space.yml: { name: "Architecture", icon: "📐", color: "#8B5CF6", sort: "alpha" }
security/ # Audits, compliance, access reviews
_space.yml: { name: "Security", icon: "🔒", color: "#EF4444", sort: "alpha" }
team/ # Processes, templates, hiring
_space.yml: { name: "Team", icon: "👥", color: "#F59E0B", sort: "alpha" }
daily-notes/ # Daily logs and standup notes
_space.yml: { name: "Daily Notes", icon: "📝", color: "#6B7280", sort: "date-desc" }
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 401 lines · 101 tokens per session scan A c2f1ef4e8734
workspace-manager is a skill published in the GitHub repository falaky87/workspace-manager-skill (2 stars, last pushed 7mo ago), licensed MIT. It adds 101 tokens to every session and 2,765 once invoked, about $0.0005 per session on Opus 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-08-31.
Other skills, from other repositories
slack-tools
Slack workspace management and automation specialist.
13-Day Sprint Method
Productivity system based on Maya calendar with 13 natural tones for project management and personal development.
03_task5
Triages a support inbox, prioritizes urgent issues, routes each to the right internal team member, and drafts any customer-facing replies for review. Use when: catching up on a backlog of support messages, producing an escalation report, or routing issues to appropriate owners.
03_task2
Extracts action items and pending tasks from Slack messages. Use when: reviewing unread messages for todos, finding deadlines or requests directed at the user, or producing a task summary from recent Slack activity.
communications-productivity-integrations
Class-level workflow for messaging, email, calendars, notes, boards, workspaces, and collaboration integrations via CLIs/APIs: Discord, Slack, Gmail/IMAP, Google Workspace, CalDAV, Trello, Notion, Obsidian, Apple Notes/Reminders, iMessage/SMS, and Clawk. Use when asked to send/read/manage messages, email, calendar…
things-mac
Manage Things 3 via the things CLI on macOS (add/update projects+todos via URL scheme; read/search/list from the local Things database). Use when a user asks OpenClaw to add a task to Things, list inbox/today/upcoming, search tasks, or inspect projects/areas/tags.