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 saski/arnesto --skill wiki-history-ingestgit clone --depth 1 https://github.com/saski/arnestoWrote 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/saski/arnesto/wiki-history-ingest)<a href="https://agentmods.dev/skills/saski/arnesto/wiki-history-ingest"><img src="https://agentmods.dev/badge/skills/saski/arnesto/wiki-history-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/saski/arnesto/wiki-history-ingest"><img src="https://agentmods.dev/badge/skills/saski/arnesto/wiki-history-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.00062 | $0.00425 |
| Opus 5 | $0.00031 | $0.00212 |
| Sonnet 5 | $0.00012 | $0.00085 |
| Haiku 4.5 | $0.00006 | $0.00042 |
Grade A, and why
wiki-history-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 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.
What it actually says
Unified History Ingest Router
This is a thin router for history sources only. It does not replace wiki-ingest for documents.
Subcommands
If the user invokes /wiki-history-ingest <target> (or equivalent text command), dispatch directly:
| Subcommand | Route To |
|---|---|
claude |
claude-history-ingest |
codex |
codex-history-ingest |
auto |
infer from context using rules below |
Routing Rules
- If the user explicitly says
claudeorcodex, route directly. - If the user provides a path/source:
~/.claudeor Claude memory/session JSONL artifacts ->claude-history-ingest~/.codexor rollout/session index artifacts ->codex-history-ingest
- If ambiguous, ask one short clarification:
- "Should I ingest
claudeorcodexhistory?"
- "Should I ingest
- If the user asks for another history source, say that only
claudeandcodexhistory ingesters are installed in this repository.
Execution Contract
- After routing, execute the destination skill's workflow exactly.
- Do not duplicate destination logic in this file.
- Leave manifest/index/log update semantics to the destination skill.
UX Convention
- Use
wiki-ingestfor documents/content sources - Use
wiki-history-ingestfor agent history sources
Examples:
/wiki-history-ingest claude/wiki-history-ingest codex$wiki-history-ingest claude(agents that use$skillinvocation)
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 · 49 lines · 62 tokens per session scan A 16e044730e01
wiki-history-ingest is a skill published in the GitHub repository saski/arnesto (5 stars, last pushed today), licensed Unlicense. It adds 62 tokens to every session and 425 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-09-03.
Other skills, from other repositories
brain-ingest
The process for digesting a conversation, document, or research result, classifying it, and writing it down as brain content (a root-page update or a new/updated page) through the brain CLI.
immune
Hybrid adaptive memory: Cheatsheet (positive patterns pre-generation) and Immune (negative patterns post-generation) with Hot/Cold tiered auto-learning. Triggers on: "scan for errors", "immune scan", "check output quality", "antibody scan". NOT for PR review (use pr-review) or repo audits (use repo-sentinel).
usage-audit
Audit a Claude Code setup for token waste and context bloat. Checks MCP servers, CLAUDE.md, skills, and settings against bloat filters. Triggers on: "audit my context", "usage audit", "token audit", "context bloat". NOT for codebase audits.
memory-and-handoff
Two-mode skill: (1) session memory — load/persist durable workflow state under .cc10x/ (activeContext, patterns, progress) so context survives compaction; (2) handoff package — portable, secrets-redacted export for a coworker, different tool, or fresh non-cc10x session.
agent-common
Shared preamble loaded by all cc10x agents — memory protocol, contract format, output rules.
context-engineering
Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project.