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 instructions/cwensel/arcaneum/agents-mdgit 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/instructions/cwensel/arcaneum/agents-md)<a href="https://agentmods.dev/instructions/cwensel/arcaneum/agents-md"><img src="https://agentmods.dev/badge/instructions/cwensel/arcaneum/agents-md.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.00484 | $0.00484 |
| Opus 5 | $0.00242 | $0.00242 |
| Sonnet 5 | $0.00097 | $0.00097 |
| Haiku 4.5 | $0.00048 | $0.00048 |
Grade A, and why
arcaneum AGENTS.md 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 3d 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
AGENTS.md
This file provides guidance for AI agents working with this repository.
Commit Message Convention
This project follows Conventional Commits. Release notes are generated by grouping commits by type, so non-conforming messages land in a generic "Other" section.
Format
<type>(<scope>): <description>
[optional body]
[optional footer]
- type (required, lowercase): one of the types below
- scope (optional): area affected, e.g.
search,cli,ci,indexing - description (required): imperative mood, no trailing period
- breaking change: add
!after type/scope (e.g.feat(cli)!: ...) or aBREAKING CHANGE:footer
Types
| Type | Use for |
|---|---|
feat |
New feature visible to users |
fix |
Bug fix |
perf |
Performance improvement (no behavior change) |
refactor |
Code change that's neither a fix nor a feature |
docs |
Documentation only |
test |
Adding or updating tests |
build |
Build system or dependencies (pyproject.toml, packaging) |
ci |
CI/CD workflows (.github/workflows/) |
chore |
Maintenance, tooling, release commits |
style |
Formatting (no code change) |
revert |
Reverts a previous commit |
Examples
feat(search): add --limit flag to arc search semantic
fix(cli): handle empty corpus argument
ci: pin third-party actions to commit SHAs
docs(readme): update install instructions
chore(release): 0.4.2
refactor(indexing)!: rename BatchIndexer to ChunkIndexer
Rules
- ✅ Use the convention for all commits on
main - ✅ Release commits are
chore(release): X.Y.Z - ✅ Use
!orBREAKING CHANGE:footer for breaking changes — these surface at the top of release notes - ❌ Do NOT capitalize the description
- ❌ Do NOT end the description with a period
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.
- 3d ago First seen · 62 lines · 484 tokens per session scan A 5520a61788c7
arcaneum AGENTS.md is an instructions file published in the GitHub repository cwensel/arcaneum (7 stars, last pushed 8d ago), licensed MIT. It adds 484 tokens to every session, about $0.0024 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 instructions, from other repositories
daisyui code_generation_with_git.instructions.md
Instructions for saadeghi/daisyui, covering activation, initial setup, development loop, error handling and session end.
Commit Message
Comprehensive Conventional Commits guidelines for openwebui-extensions.
ai-git-commiter CLAUDE.md
Instructions for zdt1013/ai-git-commiter, covering ai git commiter, 项目结构, 技术栈, 常用命令 and 安装依赖.
wallfacer CLAUDE.md
Instructions for changkun/wallfacer: If you didn't add a test, you didn't fix a bug. Every bug fix must include a reproducible test that fails without the fix and passes with it. You commit frequently, one small scope diff at a time. Push to main once a full batch of work is complete and verified. Leftover must be…
safe-docx AGENTS.md
Instructions for UseJunior/safe-docx, covering openspec instructions, ecma-376 conformance, workflow conventions, branch naming and commits.
goldfinger AGENTS.md
Instructions for redscaresu/goldfinger, covering agents.md, two audiences — don't confuse them, what goldfinger is, hard rules and before every commit.