Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/daochild/agents-confignpx agentmods add skills/daochild/agents-config/archivariusWrote 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/daochild/agents-config/archivarius)<a href="https://agentmods.dev/skills/daochild/agents-config/archivarius"><img src="https://agentmods.dev/badge/skills/daochild/agents-config/archivarius/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/daochild/agents-config/archivarius"><img src="https://agentmods.dev/badge/skills/daochild/agents-config/archivarius.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.01859 |
| Opus 5.5 | $0.00013 | $0.00744 |
| Sonnet 5.5 | $0.00007 | $0.00372 |
| Haiku 4.5 | $0.00003 | $0.00186 |
Grade A, and why
archivarius 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 1mo 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 — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: archivarius
Role: Data Organization Architect — designs and maintains well-structured, discoverable, and maintainable information architectures for codebases, documentation, and knowledge bases.
When to Use
- Organizing or reorganizing codebases, docs, or knowledge bases
- Designing folder structures, naming conventions, taxonomies
- Creating/maintaining metadata schemas, tagging systems, cross-references
- Migrating or consolidating fragmented knowledge sources
- Establishing governance: naming conventions, ownership, lifecycle policies
Core Principles
1. Principle of Least Surprise
- Structures follow platform/framework conventions first
- Predictable locations:
src/,docs/,tests/,scripts/,data/,config/ - No "misc" or "utils" catch-alls without strong justification
2. Single Source of Truth
- One canonical location per concept
- Cross-references via links, not duplication
- Canonical paths documented in
ARCHITECTURE.mdorSTRUCTURE.md
3. Progressive Disclosure
- Top-level: domain-oriented (features, domains, layers)
- Mid-level: type-oriented (components, hooks, utils, types)
- Leaf: implementation files
- README at each level explaining purpose and conventions
4. Metadata Over Hierarchy
- Prefer tags, frontmatter, labels over deep nesting
- Max 3-4 directory levels before files
- Use indexes/READMEs for discovery, not deep trees
5. Ownership & Lifecycle
- Every directory has an
OWNERSorREADME.mdwith:- Purpose & scope
- Owner/team
- Retention policy (archive/delete criteria)
- Related docs/issues
Standard Structure Templates
Codebase (Monorepo)
root/
├── apps/ # Deployable applications
│ ├── web/
│ ├── api/
│ └── worker/
├── packages/ # Shared libraries (published or internal)
│ ├── ui/
│ ├── core/
│ └── config/
├── tools/ # Build tools, scripts, generators
├── docs/ # Documentation (see below)
├── infrastructure/ # IaC, deployment, environments
├── .github/ # CI/CD, workflows
└── ARCHITECTURE.md # Root architecture decision record
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.
- 1mo ago First seen · 204 lines · 33 tokens per session scan A f0b2fa30fad3
archivarius is a skill published in the GitHub repository daochild/agents-config (16 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 1,859 once invoked, about $0.0001 per session on Opus 5.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-07.
Other skills, from other repositories
owasp-reviewer-prompt
A paranoid OWASP-Top-10-aware system prompt for AI code review that traces data flow, treats every input as malicious, maps each finding to an OWASP category, and outputs a structured Summary / Findings / Severity / Score block reviewers can act on.
codigo-automacao
Skills para desenvolvimento de software, debug, APIs, automações no-code e uso avançado de ferramentas de IA para desenvolvimento. Use quando precisar de diagnóstico de bugs, construção de APIs, containerização, testes automatizados, integrações ou engenharia de prompts.
data-fetching
Read data in a Next.js 16 App Router app the canonical way — async Server Components first, URL searchParams for filter state, use() + when a Client Component needs server data, Route Handlers + SWR/React Query only as a last resort. Server Actions are for mutations, never reads. Use when the user is about to load…
dev-flow
Orchestrate an end-to-end product-development workflow built on atomic skills. Reads .workflow/meta.json in a project directory, works out which phase the user is in (idea → PRD → tasks → design → scaffolded → pages → modules → tests → pre-deploy gates → deployed), and delegates to whichever specialist skill owns the…
forms
Build or edit any form in a Next.js 16 App Router app through one shared toolkit in lib/forms/, with dirty + valid Save gating — on TanStack Form + Zod (default) or react-hook-form (auto-detected). Use when the user says "form", "edit panel", "create dialog", "settings page", "save button", "dirty state", or reaches…
eve-agent
Scaffold and manage an eve agent (Vercel's filesystem-first agent framework) — inside a Next.js app, as apps/agent in a monorepo, or alone at the repo root when the product has no UI. Use whenever the user wants to create, set up or initialize an eve agent; add a tool, skill, channel, connection, schedule, subagent or…