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 sseshachala/conductai --skill rundock-workspacegit clone --depth 1 https://github.com/sseshachala/conductaiWrote 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/sseshachala/conductai/rundock-workspace)<a href="https://agentmods.dev/skills/sseshachala/conductai/rundock-workspace"><img src="https://agentmods.dev/badge/skills/sseshachala/conductai/rundock-workspace/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/sseshachala/conductai/rundock-workspace"><img src="https://agentmods.dev/badge/skills/sseshachala/conductai/rundock-workspace.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.00014 | $0.01292 |
| Opus 5 | $0.00007 | $0.00646 |
| Sonnet 5 | $0.00003 | $0.00258 |
| Haiku 4.5 | $0.00001 | $0.00129 |
Grade A, and why
Workspace Management 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 9d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manage the Rundock workspace: initial setup, configuration updates, and health checks.
Setup (new or existing workspace)
Read before asking. Before asking the user anything:
- Read
CLAUDE.mdif it exists - Run
lson the workspace root and key directories - Check
.claude/settings.jsonfor tool permissions, hooks, and MCP servers - Check
.claude/skills/and.claude/agents/for existing capabilities - Summarise what you found. Propose a plan based on what already exists.
Only ask about things the files don't answer:
- Who will use it (just the user, or a team)?
- Any tools or integrations not already visible in the config?
Create or update CLAUDE.md
Write a CLAUDE.md at the workspace root with:
- Clear heading with the workspace name
- What the workspace is for
- Key rules and conventions
- File structure and naming patterns
- Tool or integration notes
Keep it concise. CLAUDE.md should be a quick reference, not a manual.
Set up folder structure
Suggest the best-fit structure based on the workspace purpose:
PARA (personal productivity, knowledge management):
0 Inbox/,1 Projects/,2 Areas/,3 Resources/,4 Archive/
Functional (business or team workspaces):
- Organised by domain:
Clients/,Operations/,Finance/,Marketing/, etc.
Minimal (lightweight, low-maintenance):
Inbox/,Working/,Reference/
Let the user choose or adapt. Don't impose a structure they won't maintain.
Audit (workspace health check)
Run this when the user asks "how's my workspace?" or "review my setup."
Check workspace fundamentals
- CLAUDE.md exists and is current (not stale or generic)
- Folder structure matches the workspace's actual use
-
.claude/agents/exists with at least one agent -
.claude/settings.jsonhas appropriate permissions
Check skill completeness
For every skill file in .claude/skills/:
- Frontmatter fields. Each skill file must have a YAML frontmatter block with
nameanddescriptionfields. Flag any skill missing either field. - Body content. The content after the frontmatter closing
---must be non-empty. Flag skills that are stubs (frontmatter only, no instructions).
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.
- 9d ago First seen · 119 lines · 14 tokens per session scan A f670a9caa491
Workspace Management is a skill published in the GitHub repository sseshachala/conductai (32 stars, last pushed today), licensed Apache-2.0. It adds 14 tokens to every session and 1,292 once invoked, about $0.0001 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-30.
Other skills, from other repositories
intelligence-docs
Keeps the CopilotKit Intelligence landing page in sync when a new Intelligence feature ships or when Intelligence docs are added, renamed, or removed. Use when adding Intelligence capabilities, writing or moving pages under docs/intelligence, editing IntelligenceFeatureCards, or changing…
background-task
Add or modify work that runs outside the request/response cycle — emails, document ingestion, webhooks, cleanups, scheduled jobs. Use when something is slow or fire-and-forget, or when adding a periodic/cron task. This project's queue is {{ cookiecutter.backgroundtasks }}.
agent-tool
Add a new tool/function the AI agent can call (e.g. look something up, hit an external API, perform an action). Use when extending the assistant's capabilities, wiring a new function into the agent, or when the model needs a new action. This project uses {{ cookiecutter.aiframework }}.
frontend-feature
Build a new page, view, or data-driven feature in the Next.js frontend. Use when adding a route under the dashboard/marketing area, wiring UI to a backend endpoint, adding client state, or creating a localized page. Covers App Router, data fetching, Zustand stores, and i18n.
rag-knowledge
Work with the RAG knowledge base — ingest documents, run semantic search, manage collections, or add a sync source/connector (Google Drive, S3). Use when populating or debugging the knowledge base, tuning retrieval, or adding a new document source. This project uses {{ cookiecutter.vectorstore }} + {{…
alembic-migration
Create, review, and apply database schema changes with Alembic. Use whenever a SQLAlchemy model is added or changed, a column/index/constraint needs to change, or a data backfill is required — anything that alters the PostgreSQL schema.