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 agentmods add skills/protonium-labs/axiomcore-plugin/setupnpx skills add protonium-labs/axiomcore-plugin --skill setupgit 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/setup)<a href="https://agentmods.dev/skills/protonium-labs/axiomcore-plugin/setup"><img src="https://agentmods.dev/badge/skills/protonium-labs/axiomcore-plugin/setup.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 | $0.00067 | $0.01684 |
| Opus 5 | $0.00034 | $0.00842 |
| Sonnet 5 | $0.00013 | $0.00337 |
| Haiku 4.5 | $0.00007 | $0.00168 |
Grade A, and why
setup 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 4d 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 — 98 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: /setup <action> <arguments>.
If the requested action is ambiguous or contradictory, do NOT guess: flag it and ask for clarification before executing.
First-run onboarding and module activation are owned by /axiom — if the user asks for initial setup, point them to /axiom start.
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)
| Argument | Action |
|---|---|
new <capability idea> |
Guided interview + structure analysis → draft a new setup file in setup/ |
run <name> |
Execute a pending setup file and archive it to setup/done/ |
list |
Show pending and installed capabilities |
overview |
This table |
If the action was unknown, say so first, then show the table.
If action is "new"
Goal: turn a capability idea into a reviewable setup file — nothing is implemented in this action.
- Check $ARGUMENTS (after "new"): the capability idea. If empty: ask what capability the user wants. If the idea is a hierarchy-depth change for an existing project or workstation, skip the capability interview and follow "Structural migrations" below instead — the file has a fixed content list.
- Interview, one block at a time, only what the idea leaves open:
- Goal: what should the capability do, for whom, how often (recurring or one-off)?
- Inputs: what arrives, where does it land (folder, MCP, email)?
- Outputs: what is produced, where does it go?
- Integrations: which MCPs/services are needed?
- Additions: new skills, agents, vault areas?
- Analyze the current structure: root CLAUDE.md rules (hierarchy, WP-only work, vault mirroring), existing projects,
vault/index.md, installed capabilities insetup/done/. The capability must fit the system rules — e.g. a "drop folder for bills" becomes a WPresources/folder inside a finance project, not a foreign folder. - Draft
setup/su-<NNN>-<name>.md(kebab-case name, no-setupsuffix — the folder and the acronym already say it): sections Capability, Prerequisites, Installs (concrete list), Open decisions (what remains to clarify at run time), Definition (detailed behavior). Status: pending. Allocate<NNN>here, at drafting, fromNext setupinsetup/README.mdand bump the counter — monotonic, never reused; a discarded draft does not free its number. Setup files are deliverables: the file carries the standard header block and changelog (.claude/templates/output-document-template.md, acronymSU) and keeps its name when it is later archived todone/— the number is how it is cited afterwards. - Read the draft back to the user; iterate until approved. Lint the file.
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.
- 4d ago First seen · 98 lines · 67 tokens per session scan A e07b9c13b331
setup is a skill published in the GitHub repository protonium-labs/axiomcore-plugin (3 stars, last pushed 1mo ago), licensed MIT. It adds 67 tokens to every session and 1,684 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
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.
change-management
Comprehensive change management consulting toolkit — stakeholder mapping, ADKAR framework, Kotter's 8-Step Model, communication planning, resistance analysis, cultural assessment, readiness assessment, training needs analysis, impact assessment, and transition planning.
customer-insights
Analyze customer behavior, map journeys, develop personas, and identify growth opportunities. Use this skill when the user mentions: customer insights, voice of customer, VoC, customer journey, journey mapping, JTBD, jobs to be done, persona, customer segmentation, churn analysis, retention, NPS, CSAT, customer…
digital-transformation
Assess digital maturity, build transformation roadmaps, evaluate AI/automation opportunities, rationalize technology stacks, and design data and cloud strategies. Use this skill when the user mentions: digital transformation, digital maturity, digital strategy, technology modernization, legacy modernization…
m-and-a-strategy
M&A strategy formulation, target screening, synergy modeling, integration planning, and post-merger performance tracking. Use this skill when the user mentions: M&A strategy, mergers and acquisitions, acquisition strategy, buy vs build, target screening, synergy analysis, synergy modeling, integration planning…