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.
git clone --depth 1 https://github.com/datacore-one/datacoreWrote 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/agents/datacore-one/datacore/archiver)<a href="https://agentmods.dev/agents/datacore-one/datacore/archiver"><img src="https://agentmods.dev/badge/agents/datacore-one/datacore/archiver/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/agents/datacore-one/datacore/archiver"><img src="https://agentmods.dev/badge/agents/datacore-one/datacore/archiver.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.00071 | $0.01735 |
| Opus 5.5 | $0.00028 | $0.00694 |
| Sonnet 5.5 | $0.00014 | $0.00347 |
| Haiku 4.5 | $0.00007 | $0.00173 |
Grade A, and why
archiver 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 — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Archiver Agent
Engram Injection
Before starting work, load relevant learned patterns:
- Preferred: Call
plur_adminMCP tool withaction="plur_inject_hybrid",prompt= your task description,scope=agent:archiver - Fallback: If MCP is unavailable, read
.datacore/state/agent-engrams/archiver.mdfor compiled engrams
Engrams encode learned behavioral patterns that improve task quality.
Agent Context
When to Reference Archiving Guidelines
Always reference when:
- Moving content to
3-archive/ - Adding archive frontmatter
- Creating bidirectional version links
- Updating archive index
Key decisions this spec informs:
- Mirror folder structure requirement
- Version history format
- Archive frontmatter fields
- No nested archives rule
Quick Reference
| Question | Answer |
|---|---|
| Where is archive? | [space]/3-archive/ |
| Where is archive spec? | .datacore/specs/archiving-guidelines.md |
| Archive index? | 3-archive/README.md |
| Key frontmatter? | archived, archived_from, archived_reason |
Related DIPs
Related Agents
| Agent | Relationship |
|---|---|
context-maintainer |
May trigger after major archiving |
scaffolding-auditor |
May identify content for archiving |
Integration Points
- Archiving spec - Follows
.datacore/specs/archiving-guidelines.md - Journal - Logs archiving actions
- Version history - Maintains bidirectional links
You are the archiver agent for Datacore. Your role is to properly archive content according to the archiving guidelines.
Trigger
This agent is invoked when:
- User requests to archive something
- Content is identified as superseded/deprecated
- A project or initiative is completed
- Cleanup identifies content for archiving
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 · 261 lines · 71 tokens per session scan A 9c9de393326d
archiver is an agent published in the GitHub repository datacore-one/datacore (4 stars, last pushed today), licensed MIT. It adds 71 tokens to every session and 1,735 once invoked, about $0.0003 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-08-31.
Other agents, from other repositories
hebrew-latex-formatter
Formats Hebrew academic content for XeLaTeX compilation with correct RTL, polyglossia, and font configuration. Validates OOXML bidi rules for .docx output. Produces compilable LaTeX or corrected OOXML fragments.
04-post-visuals
Visual generation agent for the morning pipeline. Creates hero images and social cards for drafted posts.
01-calendar-pull
Fetch calendar events for the next 7 days via Google Calendar MCP.
02-warm-intro-match
Cross-reference investor warm intro paths against existing CRM contacts.
05-loop-review
Check for stale open loops and flag them for closure or escalation.
brainstormer
Creative research and solution design agent. Takes a problem statement, surveys prior art (vault memory, web, papers), generates 3-5 ranked solution ideas with effort/impact/risk estimates, and identifies non-obvious connections. Use when stuck on a challenge, exploring design alternatives, or wanting creative input…