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/memgraph/ai-toolkitnpx agentmods add skills/memgraph/ai-toolkit/setupWrote 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/memgraph/ai-toolkit/setup)<a href="https://agentmods.dev/skills/memgraph/ai-toolkit/setup"><img src="https://agentmods.dev/badge/skills/memgraph/ai-toolkit/setup/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/memgraph/ai-toolkit/setup"><img src="https://agentmods.dev/badge/skills/memgraph/ai-toolkit/setup.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.00014 | $0.00605 |
| Opus 5.5 | $0.00006 | $0.00242 |
| Sonnet 5.5 | $0.00003 | $0.00121 |
| Haiku 4.5 | $0.00001 | $0.00060 |
Grade A, and why
setup 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 3d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memgraph Context Graph
Use this skill when the user asks whether Claude Code activity is being captured, how Memgraph Context Graph hooks work, or why graph facts are missing.
Model
Claude Code Plugin -> Claude Code Runtime Adapter -> Event Protocol -> Graph Connector -> Memgraph.
The plugin only installs runtime hook wiring. It must not assign graph meaning. Graph connectors decide which normalized events matter.
Checks
For first-time setup, run the plugin bootstrap once. It installs the CLI and runs memgraph-context-graph setup claude-code --no-tui, which finds or starts Memgraph, sets the user's identity and checks the hooks:
./scripts/bootstrap.sh
If setup reports a failure, show the user its "To fix" line; it is the exact command to run next.
Run the single CLI doctor first. It checks the same Python environment that the hook command uses:
memgraph-context-graph doctor --runtime claude-code --connector skills-graph --connector actions-graph --connector sessions-graph
If doctor is not available, use the strict hook smoke:
printf '{"hook_event_name":"Stop","session_id":"doctor"}' \
| memgraph-context-graph hook run claude-code --connector skills-graph --connector actions-graph --connector sessions-graph --strict
Do not check skills_graph with system python3; memgraph-context-graph may be installed in an isolated uv tool or pipx environment.
Configuration
Connection settings live in ~/.config/context-graph/config.toml. Hook subprocesses read from this file (not environment variables).
setup writes memgraph.url and identity.user_id; other values (credentials, keys) are set with config set.
View current config:
memgraph-context-graph config show
Set values:
memgraph-context-graph config set identity.user_id "username"
memgraph-context-graph config set memgraph.url "neo4j://coordinator:7687"
memgraph-context-graph config set memgraph.user "username"
memgraph-context-graph config set memgraph.password
memgraph-context-graph config set memgraph.database "dbname"
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.
- 3d ago First seen · 72 lines · 14 tokens per session scan A a33a2159990f
setup is a skill published in the GitHub repository memgraph/ai-toolkit (116 stars, last pushed 2d ago), licensed MIT. It adds 14 tokens to every session and 605 once invoked, about $0.0001 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-10-14.
Other skills, from other repositories
agent-platform-model-registry
Agent Platform Model Registry Management. Use when you need to upload, list, describe, update, or delete machine learning models (and their versions) in the Agent Platform Model Registry. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform models.
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
google-cloud-solution-agentic-analytics-spark-knowledge-catalog
Discovers requirements and designs an end-to-end governed agentic analytics solution using Knowledge Catalog and Managed Service for Apache Spark (Lightning Engine). Use when designing data science and analytics workflows across structured and unstructured distributed data (including in S3, Azure Blob, AlloyDB, and…
training-check
Interactively monitor training metrics from the current Codex session, periodically checking WandB or fallback logs for NaN, divergence, plateaus, and broken runs.
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
finetuning
Fine-tune models on Microsoft Foundry using SFT (supervised), DPO (preference), or RFT (reinforcement with graders). Covers dataset preparation, training job submission, deployment, and evaluation. USE FOR: fine-tune, SFT, DPO, RFT, training data, grader, distillation, fine-tuned model, training job, large file…