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 ingestgit 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/ingest)<a href="https://agentmods.dev/skills/protonium-labs/axiomcore-plugin/ingest"><img src="https://agentmods.dev/badge/skills/protonium-labs/axiomcore-plugin/ingest/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/ingest"><img src="https://agentmods.dev/badge/skills/protonium-labs/axiomcore-plugin/ingest.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.00033 | $0.00510 |
| Opus 5 | $0.00016 | $0.00255 |
| Sonnet 5 | $0.00007 | $0.00102 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
ingest 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.
What it actually says
Task
Execute the requested action: $ARGUMENTS
Calling rule: /ingest <action> <arguments>.
If the requested action is ambiguous or contradictory, do NOT guess: flag it and ask for clarification before executing.
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 |
|---|---|
all |
Process every unprocessed file in vault/sources/ |
file <name> |
Process one specific source file |
overview |
This table |
If the action was unknown, say so first, then show the table.
If action is "all" or "file"
- Scope:
all: listvault/sources/and compare againstvault/log.mdingest entries to find unprocessed files. Large batches: one source at a time, report progress.file <name>: match the name invault/sources/; if missing or empty, list the folder and ask.
- Read each source fully. PDFs, images, transcripts, articles alike.
- Integrate, don't just summarize, per source:
- Update existing pages where the topic exists; create new pages only for genuinely new topics (one topic per page).
- Add YAML frontmatter (
tags,created,updated,source) and[[wiki links]]to every related page. A single source may touch 10-15 pages. - Route by content: user-related →
vault/me/, project-related →vault/projects/<name>/, general knowledge →vault/knowledge/. - Flag contradictions explicitly in the page and in the report; never silently overwrite.
- Never modify the source file itself (CLAUDE.md hard rule).
After any action
- One log entry per source:
## [YYYY-MM-DD HH:MM] /ingest | <source> -> pages touched. - Update
vault/index.mdwith new pages. - Report: sources processed, pages created/updated, contradictions flagged.
Notes
- All pages must pass markdownlint.
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 · 56 lines · 33 tokens per session scan A 4afe2e79351d
ingest is a skill published in the GitHub repository protonium-labs/axiomcore-plugin (3 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 510 once invoked, about $0.0002 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
deliverable-creation
Produce polished, consulting-quality deliverables including slide decks, reports, memos, and one-pagers. Use this skill when the user mentions: create a deck, build a presentation, make slides, write a report, executive summary, one-pager, synthesis, storyboard, slide structure, pyramid principle, consulting deck…
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.
reviewing-docs
Use when the user has a finished or near-finished document (memo, business review, PRD, decision doc, briefing, comms, framework, talking points, post-mortem) and wants it pressure-tested before it ships, such as "review this doc", "poke holes in this", "is this ready to send". Works on any doc, not just…
ingest
An intake process for turning a PDF or PowerPoint deck, spreadsheet, wiki page, or pasted figures into traceable evidence for product hypotheses.
preserve-security-evidence
Preserve security evidence before analysis, containment, or remediation changes it. Use for artifacts, volatile host state, vulnerability validation, records, logs, screenshots, commands, hashes, timelines, and reproducible handoffs.