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 skills/timurgaleev/memex/archive-crawlernpx skills add timurgaleev/memex --skill archive-crawlergit clone --depth 1 https://github.com/timurgaleev/memexWrote 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/timurgaleev/memex/archive-crawler)<a href="https://agentmods.dev/skills/timurgaleev/memex/archive-crawler"><img src="https://agentmods.dev/badge/skills/timurgaleev/memex/archive-crawler.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.1 | $0.00074 | $0.02802 |
| Opus 5 | $0.00037 | $0.01401 |
| Sonnet 5 | $0.00015 | $0.00560 |
| Haiku 4.5 | $0.00007 | $0.00280 |
Grade A, and why
archive-crawler 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 5d 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.
This is a copy
92% identical to archive-crawler — 101 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 332 lines — stays where its author put it; the contents beside it link to each section on GitHub.
archive-crawler — The Universal Archivist
Convention: see conventions/quality.md (via
get_skill conventions/quality) for citation rules, exact-phrasing requirements when capturing the user's reactions, and back-link enforcement.Convention: see
_brain-filing-rules.md(viaget_skill _brain-filing-rules) — this skill is schema-generic: it reads the user's filing rules from the rules page instead of hardcoding any specific era / archive layout.
Safety gate (REQUIRED, no exceptions)
archive-crawler refuses to run unless a scan_paths: allow-list is
explicitly set in the brain page config/archive-crawler (read it with
page_get config/archive-crawler). This is a deliberate safety fence
against the agent over-scoping a scan and ingesting sensitive content
(tax PDFs, medical records, credentials).
# config/archive-crawler — frontmatter; the allow-list is mandatory
scan_paths:
- ~/Documents/writing/
- ~/Dropbox/Archive/
- /mnt/backup/old-letters/
# Optional deny-list inside the allow-list:
# deny_paths:
# - ~/Documents/finances/
# - ~/Documents/medical/
If scan_paths is empty or the page is missing, the skill exits with:
archive-crawler: refusing to run. No `scan_paths:` allow-list on the
config/archive-crawler brain page. Add explicit paths the agent is
permitted to scan (page_put config/archive-crawler), then re-run.
This is a safety fence — the agent will not infer what's safe to read.
This contract is enforced by the agent itself: the allow-list check is the first step of every run, before any filesystem access.
What this is
Generic engine for exploring any tree of personal content within an
explicit allow-list. Works on local mounts, Dropbox API targets,
Backblaze B2, Gmail takeouts (.mbox), and similar archives. Filters
for "gold" (the user's own writing, ideas, relationships) and surfaces
it interactively for review. Skips noise (system files, configs, binary
blobs).
Concepts
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 332 lines · 74 tokens per session scan A 72990e058cf1
archive-crawler is a skill published in the GitHub repository timurgaleev/memex (8 stars, last pushed 4d ago), licensed MIT. It adds 74 tokens to every session and 2,802 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to archive-crawler, differing in 101 lines, and is treated as a copy.
Other skills, from other repositories
design-mcp-server
Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.
api-context
Canonical reference for the unified Context object passed to every tool and resource handler in @cyanheads/mcp-ts-core. Covers the full interface, its RequestContext base, all sub-APIs (ctx.log, ctx.state, ctx.requestInput, ctx.inputs, ctx.enrich, ctx.content), and when to use each.
api-canvas
DataCanvas primitive reference — a Tier 3 SQL/analytical workspace for tabular MCP servers, backed by DuckDB. Use when registering tables from upstream APIs, running ad-hoc SQL across them, and exporting results. Covers the acquire → register → query → export flow, per-table TTL, the token-sharing pattern for…
api-config
Reference for core and server configuration in @cyanheads/mcp-ts-core. Covers env var tables with defaults, priority order, server-specific Zod schema pattern, and Workers lazy-parsing requirement.
api-testing
Testing patterns for MCP tool/resource handlers using createMockContext and Vitest. Covers mock context options, handler testing, McpError assertions, format testing, Vitest config setup, and test isolation conventions.
field-test
Exercise tools, resources, and prompts against a live HTTP server via MCP JSON-RPC over curl. Starts the server, surfaces the catalog, runs real and adversarial inputs, and produces a tight report with concrete findings and numbered follow-up options. Use after adding or modifying definitions, or when the user asks to…