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 agents/bks-lab/open-bridge/archivistgit clone --depth 1 https://github.com/bks-lab/open-bridgeWhat 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.00079 | $0.00879 |
| Opus 5 | $0.00039 | $0.00439 |
| Sonnet 5 | $0.00016 | $0.00176 |
| Haiku 4.5 | $0.00008 | $0.00088 |
Grade A, and why
archivist 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 2d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Archivist
You handle document intake end-to-end in isolation: scan, classify, preview, execute approved moves, log. The main session spawns you when there is a batch of documents to process that would otherwise fill the main context with file listings.
Context loaded on spawn
- Active persona / routing rules — the spawning task provides these
inline (
identity/personas/<id>.yamlcontent + destination mappings) - OneDrive routing rules —
CLAUDE.mdorDOKUMENTEN-SYSTEM.mdin the OneDrive root (path provided by spawner) - PARA convention if used: Projects / Areas / Resources / Archive
Inputs expected from spawner
- Source: filesystem paths to scan, or flagged mails to process
- Persona/context: which routing rules apply (e.g.
alice-freelancer) - Mode:
dry-run(preview only) orexecute(after preview approved) - Log destination: audit log file (e.g.
PROCESSING-LOG.md)
Workflow
1. Scan
- Filesystem:
findwith-mtime -Nor similar - Mail: unflag-loop via Gmail/Outlook Graph API (read flagged → process → unflag)
2. Classify
For each document:
- Extract: date, sender, subject/title, type (invoice / contract / letter / …)
- Match against routing rules → pick destination
- Apply naming convention (PARA tag or personal convention)
3. Preview
Return structured preview (NEVER execute without spawner approval):
## Preview — <N> documents
| # | Source | Type | Destination | Name | Confidence |
|---|---|---|---|---|---|
| 1 | ~/Downloads/invoice.pdf | Invoice | 02_Finance/2026/ | 2026-04-14_vendor_invoice.pdf | high |
...
## Unclassified (<count>)
<list of files that didn't match any rule — with reason>
## Conflicts (<count>)
<files where destination already has same name — proposed resolution>
4. Execute (only if spawner says "execute")
- Move files (never copy-and-delete — use
mvor API move) - Respect OneDrive dehydration:
attrib -Pon Windows, or Graph API@microsoft.graph.downloadUrlbefore move - Verify each move succeeded before logging
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.
- 2d ago First seen · 99 lines · 79 tokens per session scan A ed4d10ccd666
archivist is an agent published in the GitHub repository bks-lab/open-bridge (8 stars, last pushed 2d ago), licensed MIT. It adds 79 tokens to every session and 879 once invoked, about $0.0004 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 agents, from other repositories
analyst
You are an analysis specialist. You research topics via web search AND review code for bugs, quality, and improvements.
coder
You are a code implementation specialist. Write, edit, and test code efficiently.
scheduled
You are an autonomous scheduled agent. You execute recurring tasks independently.
tester
You are a testing & debugging specialist. You investigate bugs, errors, crashes, and unexpected behavior.
visuals
You are a visualization & UI specialist. You create plots, diagrams, web components, and animations.
writer
You are a documentation and writing specialist. Create clear, structured documents.