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 cwensel/arcaneum --skill arc-corpusgit clone --depth 1 https://github.com/cwensel/arcaneumWrote 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/cwensel/arcaneum/arc-corpus)<a href="https://agentmods.dev/skills/cwensel/arcaneum/arc-corpus"><img src="https://agentmods.dev/badge/skills/cwensel/arcaneum/arc-corpus/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/cwensel/arcaneum/arc-corpus"><img src="https://agentmods.dev/badge/skills/cwensel/arcaneum/arc-corpus.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 16 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Excessive Agency · line 24 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 73 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00067 | $0.02029 |
| Opus 5 | $0.00034 | $0.01014 |
| Sonnet 5 | $0.00013 | $0.00406 |
| Haiku 4.5 | $0.00007 | $0.00203 |
Grade A, and why
arc-corpus 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 8d 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Corpus Management (Dual-Index)
A corpus maintains both a Qdrant collection (semantic search) and a MeiliSearch index (full-text search) in sync.
For adding or updating content, always prefer arc corpus sync over arc index, arc collection, or arc indexes.
The corpus commands manage Qdrant and MeiliSearch together. Single-system commands
(arc index, arc collection, arc indexes) are for advanced workflows that need one system without the other.
# Create corpus (creates both collection and index)
arc corpus create MyCorpus --type pdf
arc corpus create MyCorpus --type code
arc corpus create MyCorpus --type markdown
arc corpus create MyCorpus --type pdf --models qwen3-embed,jina-v3 # Multiple models
# Delete corpus (deletes both collection and index)
arc corpus delete MyCorpus # With confirmation prompt
arc corpus delete MyCorpus --confirm # Skip confirmation
arc corpus delete MyCorpus --confirm --json # JSON output
# Sync files to both systems (preferred command for adding/updating content)
arc corpus sync MyCorpus /path/to/files
arc corpus sync MyCorpus /path/one /path/two /path/three # Multiple directories
arc corpus sync MyCorpus /path/to/files --parity # Detect renames, remove files no longer on disk
arc corpus sync MyCorpus /path/to/files --parity --dry-run # Preview parity changes first
arc corpus sync MyCorpus /path/to/files --force # Force reindex
arc corpus sync MyCorpus /path/to/files --verify # Verify after sync
arc corpus sync MyCorpus /path/to/files --verbose # Show progress
arc corpus sync MyCorpus /path/to/files --no-gpu # CPU-only mode (stable on Apple Silicon)
# Keep a git repo in sync automatically (installs a git hook)
arc corpus hook install # Guided: pick/create corpus, choose hooks
arc corpus hook install MyCorpus # Auto-sync on every commit
arc corpus hook install MyCorpus --hook post-merge # Also stay current after pulls
arc corpus hook install MyCorpus --service # Plus an OS watcher for reboot recovery
arc corpus hook status # What is installed in this repo
arc corpus hook uninstall MyCorpus # Remove just this corpus's hook
# Sync only what a commit touched, without installing a hook
arc corpus sync MyCorpus --changed-since HEAD # Last commit
arc corpus sync MyCorpus --changed-since ORIG_HEAD..HEAD # Since a pull
# Repair incomplete or garbled files
arc corpus repair MyCorpus # Detect and fix quality issues
arc corpus repair MyCorpus --dry-run # Preview what would be repaired
arc corpus repair MyCorpus --quality-threshold 0.5 # More aggressive detection
arc corpus repair MyCorpus --verbose # Show per-file quality scores
# View corpus info (both systems)
arc corpus info MyCorpus
arc corpus info MyCorpus --json
# List indexed items with parity status
arc corpus items MyCorpus # Table output with Q/M chunk counts
arc corpus items MyCorpus --json # JSON output for automation
# Check and restore parity between systems
arc corpus parity MyCorpus # Check and backfill single corpus
arc corpus parity MyCorpus --dry-run # Preview only
arc corpus parity MyCorpus --verify # Verify chunk counts match
arc corpus parity MyCorpus --repair-metadata # Fix missing git metadata (code corpora)
arc corpus parity MyCorpus --verbose # Detailed progress
# All-corpora mode (no corpus name)
arc corpus parity # Process all corpora
arc corpus parity --dry-run # Preview all
arc corpus parity --confirm # Skip confirmation prompt
# Create missing MeiliSearch indexes for qdrant_only corpora
arc corpus parity --create-missing --dry-run # Preview what would be created
arc corpus parity --create-missing --confirm # Create and sync all
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.
- 8d ago First seen · 183 lines · 67 tokens per session scan A f4046ab739d3
arc-corpus is a skill published in the GitHub repository cwensel/arcaneum (7 stars, last pushed 4d ago), licensed MIT. It adds 67 tokens to every session and 2,029 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
pinecone
Managed vector DB for production RAG and search.
data-engineer
Build scalable data pipelines, modern data warehouses, and real-time streaming architectures. Implements Apache Spark, dbt, Airflow, and cloud-native data platforms.
graphjin-env
Use when setting up a training or evaluation loop against a GraphJin agent environment — running the container, reading /health, driving episodes hosted or step-by-step or with your own agent over MCP, splitting train from eval, exporting trajectories, and deciding whether two rewards can be compared.
similarity-search-patterns
Implement efficient similarity search with vector databases. Use when building semantic search, implementing nearest neighbor queries, or optimizing retrieval performance.
ingesting-into-data-lake
Import data into the AWS data lake from S3 files, local uploads, JDBC databases (Oracle, SQL Server, PostgreSQL, MySQL, RDS, Aurora), Amazon Redshift, Snowflake, BigQuery, DynamoDB, or existing Glue catalog tables (migration). Default target is S3 Tables; standard Iceberg on a general purpose bucket is supported where…
nornicdb-qdrant-migration
Migrate from Qdrant to NornicDB end-to-end through NornicDB's Qdrant-compatible gRPC surface. Covers connection setup, collection→database mapping, point→node mapping, the vector-config and named-vector replication, point upsert in batches, count verification, and what (deliberately) does not transfer (snapshots, HNSW…