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 OctoPerf/octoperf-claude-plugins --skill octoperf-workspacegit clone --depth 1 https://github.com/OctoPerf/octoperf-claude-pluginsWrote 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/octoperf/octoperf-claude-plugins/octoperf-workspace)<a href="https://agentmods.dev/skills/octoperf/octoperf-claude-plugins/octoperf-workspace"><img src="https://agentmods.dev/badge/skills/octoperf/octoperf-claude-plugins/octoperf-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/octoperf/octoperf-claude-plugins/octoperf-workspace"><img src="https://agentmods.dev/badge/skills/octoperf/octoperf-claude-plugins/octoperf-workspace.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.00000 | $0.01325 |
| Opus 5 | $0.00000 | $0.00662 |
| Sonnet 5 | $0.00000 | $0.00265 |
| Haiku 4.5 | $0.00000 | $0.00133 |
Grade A, and why
octoperf-workspace 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 12d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workspace — who works where, and with what
A workspace is the container everything else lives in. Read this before adding someone to one, changing what they can do, or wondering why a provider a colleague swears exists is nowhere to be found.
What a workspace scopes
Two levels, and confusing them is the most common source of "I can't see it":
| Scoped to the workspace | Scoped to a project |
|---|---|
| Members and their roles | Virtual users, scenarios, variables, files |
| Load-generator providers and their agents | Monitors (they run through a workspace agent) |
| Notifications (email, Slack, Teams, JIRA, …) | Bench results and reports |
So a provider added to workspace A cannot run a scenario of a project in
workspace B, a notification fires for every project of its workspace, and
list_workspace_agents takes the workspace that owns the monitor's project —
not the project. Deep dives live in octoperf://skills/onpremise-agent
(providers and agents), octoperf://skills/notifications (channels and events)
and octoperf://skills/monitoring (monitors and the agents that carry them).
Create sparingly, because deleting is not yours to do
Anyone can create a workspace; nobody can casually remove one. Deletion takes the platform administrator on-premise, or an OctoPerf support request on SaaS — deliberately, since removing a workspace takes every project, provider and past result it holds. Being admin of the workspace is not enough: that is the platform role, a different thing.
Before create_workspace, call list_workspaces and reuse. A new workspace
earns its place when a separate set of members or load generators is needed
— a client, a team, an isolated environment. Merely grouping work is what
create_project is for. The creator becomes admin of what they create.
update_workspace renames or re-describes one. The name is what every member
sees in their switcher, so a rename is visible to all of them at once.
Names are 80 characters at most, descriptions 2000 — the web form's own bounds. Past them the edit form is invalid the moment it opens, so the write is refused rather than truncated.
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.
- 12d ago First seen · 112 lines · 0 tokens per session scan A d9cdf2366733
octoperf-workspace is a skill published in the GitHub repository OctoPerf/octoperf-claude-plugins (0 stars, last pushed 5d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,325 tokens. 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
persona-customer-support
Manage customer support — track tickets, respond, escalate issues.
persona-event-coordinator
Plan and manage events — scheduling, invitations, and logistics.
persona-project-manager
Coordinate projects — track tasks, schedule meetings, and share docs.
persona-team-lead
Lead a team — run standups, coordinate tasks, and communicate.
recipe-create-doc-from-template
Copy a Google Docs template, fill in content, and share with collaborators.
recipe-create-events-from-sheet
Read event data from a Google Sheets spreadsheet and create Google Calendar entries for each row.