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/skillpack-checknpx skills add timurgaleev/memex --skill skillpack-checkgit 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/skillpack-check)<a href="https://agentmods.dev/skills/timurgaleev/memex/skillpack-check"><img src="https://agentmods.dev/badge/skills/timurgaleev/memex/skillpack-check.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.00109 | $0.01268 |
| Opus 5 | $0.00055 | $0.00634 |
| Sonnet 5 | $0.00022 | $0.00254 |
| Haiku 4.5 | $0.00011 | $0.00127 |
Grade A, and why
skillpack-check 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 4d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skillpack Check
Contract
Running memex skillpack check returns a JSON report with:
healthy(bool): true if no action needed.summary(string): one-line summary safe to quote in a briefing.actions(string[]): every remediation command. If non-empty, run them.doctor: fullmemex doctor --fast --jsonoutput (brain/ops/meta checks).coverage: embedded/unembedded chunk counts + per-source health from the source rollup.
Exit code:
0— healthy, nothing to do.1— action needed. Readactions[]and execute.2— could not determine (binary crash or missing subcommand). Investigate.
From MCP, the same signal is available without shell access: run_doctor
for the check detail, get_status_snapshot for the one-glance rollup,
source_health for per-source ingest state.
When to run
- Daily timer (e.g. a systemd timer feeding the morning briefing):
memex skillpack check --quiet. Exit code alone tells you if anything is wrong; surface a one-liner in the briefing only when exit != 0. No JSON noise in happy-path briefings. - On demand:
memex skillpack checkfor the full JSON when debugging. - In a CI pipeline: same pattern — exit code gates, JSON is the evidence.
What to do with the output
Happy path (healthy: true)
Surface the summary in the agent's output only if asked. Nothing else.
Action needed (healthy: false)
The actions[] array contains the commands to run, in order. Execute them:
for cmd in $(echo "$REPORT" | jq -r '.actions[]'); do
eval "$cmd"
done
Common actions[] entries and what they mean:
memex embed— Embedding coverage has fallen behind (unembedded chunks exist). Run it (it's idempotent); it backfills only what's missing.memex reindex— Index drift between pages and the search index.memex cycle— Background maintenance is overdue (the server's own cycle normally handles this; a manual run catches it up).- Free-text action (no
Run:prefix in the source message) — agent judgment needed. Quote it in the report for the user.
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.
- 4d ago First seen · 140 lines · 109 tokens per session scan A 062bafc3ac98
skillpack-check is a skill published in the GitHub repository timurgaleev/memex (8 stars, last pushed 3d ago), licensed MIT. It adds 109 tokens to every session and 1,268 once invoked, about $0.0005 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 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-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…
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.