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 protonium-labs/axiomcore-plugin --skill wsgit clone --depth 1 https://github.com/protonium-labs/axiomcore-pluginWrote 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/protonium-labs/axiomcore-plugin/ws)<a href="https://agentmods.dev/skills/protonium-labs/axiomcore-plugin/ws"><img src="https://agentmods.dev/badge/skills/protonium-labs/axiomcore-plugin/ws.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.00060 | $0.03446 |
| Opus 5 | $0.00030 | $0.01723 |
| Sonnet 5 | $0.00012 | $0.00689 |
| Haiku 4.5 | $0.00006 | $0.00345 |
Grade A, and why
ws 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 7d 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task
Execute the requested action: $ARGUMENTS
Calling rule: /ws <action> <arguments>.
If the requested action is ambiguous or contradictory, do NOT guess: flag it and ask for clarification before executing.
Core principle: work is done at work-area level only. Workstations and sub-workstations are organizational structure for routines — the same rule work packages carry on the project side (root CLAUDE.md, Hierarchy Protocol). Projects are for temporary activity (done once); workstations are for repeated activity.
Tier check (read axiom-config.md first): in simple tier, every workstation is 2-level — do not ask the depth question, do not mention 3-level structure, and manage numbering silently. In advanced tier, follow the depth rules below in full.
Hierarchy depth (advanced tier — read before any action)
Every workstation is either 2-level or 3-level. The depth is chosen when the workstation is created and recorded in its registry as Levels: **2** or Levels: **3**.
| Depth | Chain | Sub-workstations | Addressing |
|---|---|---|---|
| 2-level | Workstation → Work Area (WA) | Not allowed | <ws> - <area> |
| 3-level | Workstation → Sub-workstation → Work Area (WA) | Mandatory — every WA lives in one | <ws> - <sub> - <area> |
Before any action other than "new WS": read vault/workstations/<workstation>/areas.md, take Levels, and obey it. WA numbers restart at 01 inside each sub-workstation, so at 3 levels a WA is identified only together with its sub-workstation — always address it that way.
The depth is locked. This skill never converts a workstation between 2 and 3 levels. If the user asks for it, refuse and point to /setup new (Setup Protocol): the change is drafted as a setup file, executed once, and archived to setup/done/.
If action is empty
Describe this skill: its purpose and the actions table from "overview". Do not execute anything.
If action is "overview" (or unknown)
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.
- 7d ago First seen · 189 lines · 60 tokens per session scan A 9b5bd038d5fd
ws is a skill published in the GitHub repository protonium-labs/axiomcore-plugin (3 stars, last pushed 1mo ago), licensed MIT. It adds 60 tokens to every session and 3,446 once invoked, about $0.0003 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
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…
collaboration-platform-administration
Administers the email, chat, meeting and file-sharing platform the organization runs on — tenant and domain configuration, mail authentication and routing, phishing and spam controls, shared mailboxes and distribution groups, external sharing and guest access, permission sprawl in file storage, and retention and legal…
onboarding-and-offboarding
Designs the joining and leaving experience — first-day readiness, ramp to productivity, knowledge capture, and clean exits. Use this to design or fix onboarding, shorten time to productivity, structure a leaver process, capture knowledge before someone leaves, or coordinate the access and asset steps around a joiner…
markifact-overview
Reference — what Markifact is, what the MCP server exposes, and the discover→inspect→run pattern. Always loaded into the performance-marketer agent.
safe-write-operations
Reference — rules for safely executing write/destructive operations against ad accounts. Always loaded into the performance-marketer agent.
reply-triage
A sorting guide for creator replies, emails, and automation results. It puts incoming items into five priority groups and suggests what to do next.