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 axiomgit 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/axiom)<a href="https://agentmods.dev/skills/protonium-labs/axiomcore-plugin/axiom"><img src="https://agentmods.dev/badge/skills/protonium-labs/axiomcore-plugin/axiom/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/protonium-labs/axiomcore-plugin/axiom"><img src="https://agentmods.dev/badge/skills/protonium-labs/axiomcore-plugin/axiom.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.00077 | $0.02655 |
| Opus 5 | $0.00039 | $0.01327 |
| Sonnet 5 | $0.00015 | $0.00531 |
| Haiku 4.5 | $0.00008 | $0.00265 |
Grade A, and why
axiom 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 — 141 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: /axiom <action> <arguments>.
If the requested action is ambiguous or contradictory, do NOT guess: flag it and ask for clarification before executing.
This skill owns axiom-config.md — all other skills read it, only this skill writes it. Templates used below ship in this skill folder: claude-kernel-template.md, soul-template.md, brand-config-template.md, axiom-config-template.md, getting-started-template.md.
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 |
|---|---|
start |
First-run onboarding: intro → interview → scaffold the workspace → first project |
activate <module> |
Activate M2-voice, M2-brand, M3 (todos), or M4 (dev planning) |
deactivate <module> |
Deactivate a module (flags only — user data is never deleted) |
tier <simple|advanced> |
Switch disclosure tier |
language <code> |
Change the working language |
status |
Show configuration: language, tier, modules, recent nudges |
overview |
This table |
If the action was unknown, say so first, then show the table.
If action is "start"
A. Detect state
Read the workspace root. Three cases:
- Fresh (no
axiom-config.md, empty folder or unfilled template copy): full flow below. - Partial (
axiom-config.mdexists but scaffolding or module files incomplete): report what exists, run only the missing parts. - Configured: report status and offer
activate/tier/languageinstead. Never re-scaffold over a working system.
B. Intro
Deliver this positioning (adapt wording to the conversation language, keep the order):
- Structure — "AxiomCore keeps everything you work on in one enforced system: numbered folders, consistent names, unique task IDs, and a wiki memory that mirrors it all. Nothing gets lost."
- Two work trees — "Everything you do lives in one of two trees: projects are temporary — a bounded goal, worked toward and finished once (a website launch, a market analysis); workstations are permanent — recurring routines repeated on a cadence (monthly reporting, ads monitoring). A finished project can become a workstation when its work turns routine."
- Disciplined workflow — "I never rush ahead: every task runs plan → your approval → step-by-step execution with validation. You stay in control."
- Health — "
/lintaudits the whole system on demand: broken links, orphan pages, naming violations." - Growth — "
/setuplets the system learn new capabilities without breaking the structure."
What ships with it
6 files 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.
- 12d ago First seen · 141 lines · 77 tokens per session scan A a7603d03f4ed
axiom is a skill published in the GitHub repository protonium-labs/axiomcore-plugin (3 stars, last pushed 1mo ago), licensed MIT. It adds 77 tokens to every session and 2,655 once invoked, about $0.0004 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.
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.
safe-write-operations
Reference — rules for safely executing write/destructive operations against ad accounts. Always loaded into the performance-marketer agent.