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/infohata/mind-vaultnpx agentmods add skills/infohata/mind-vault/artefact-retrievalWrote 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/infohata/mind-vault/artefact-retrieval)<a href="https://agentmods.dev/skills/infohata/mind-vault/artefact-retrieval"><img src="https://agentmods.dev/badge/skills/infohata/mind-vault/artefact-retrieval/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/infohata/mind-vault/artefact-retrieval"><img src="https://agentmods.dev/badge/skills/infohata/mind-vault/artefact-retrieval.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.00043 | $0.02456 |
| Opus 5 | $0.00022 | $0.01228 |
| Sonnet 5 | $0.00009 | $0.00491 |
| Haiku 4.5 | $0.00004 | $0.00246 |
Grade A, and why
artefact-retrieval 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 10d 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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SKILL_artefact-retrieval
Overview
IDE-agnostic pattern for retrieving valuable artefacts (plans, analyses, validation reports, research notes) that AI coding assistants generate outside the project tree, and importing them into the project's docs/artefacts/ taxonomy for permanent retention and cross-session reuse.
Host Environments
This skill works identically whether the agent is invoked from:
- Claude Code (CLI, IDE extension, or Desktop app)
- Antigravity (Gemini brain workspace)
- Cursor (Plan Mode, Composer, or Agent)
- Any combination — same project, multiple assistants across sessions
The retrieval logic is source-agnostic: each IDE/assistant writes its artefacts to a known location outside the repo, and this skill catalogues those locations so any agent can sweep them into the project artefact tree.
⚠️ Claude Code auto-memory: consult, don't copy
~/.claude/projects/*/memory/ is personal memory, not an artefact store — memory files stay where they are and are never copied into docs/artefacts/.
But memory informs retrieval. Before sweeping IDE locations, skim:
MEMORY.mdand anyproject_*.mdentries for the active project — they often name current initiatives, IDEA numbers, modules, stakeholders, and deadlines. Use these to seedPROJECT_KEYWORDSfor the discovery sweep (§2) and the unsaved-artefacts audit (§5).user_*.md/feedback_*.mdfor signals about which assistant (Cursor / Antigravity / Claude Code) the user has been using recently — narrows where to look first.
The same consult-don't-copy rule applies to ~/.claude/CLAUDE.md and private user config. ~/.gemini/ / ~/.cursor/ config, credentials, and session metadata remain fully off limits — only generated work product (plans, analyses, walkthroughs) from those workspaces is a retrieval candidate.
When to Use
- 🆕 Starting a new project and looking for validated knowledge from prior work
- 🔍 Researching proven patterns before implementing a solution
- ✅ Validating assumptions against documented findings
- 🧹 Periodic sweep for completed plans and analyses that still live outside the repo
- 🔄 Ensuring consistency across agents (Claude Code / Antigravity / Cursor all see the same canonical knowledge)
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.
- 10d ago First seen · 232 lines · 43 tokens per session scan A 9a47453e870d
artefact-retrieval is a skill published in the GitHub repository infohata/mind-vault (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 43 tokens to every session and 2,456 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…