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 skills add memgraph/ai-toolkit --skill releasegit clone --depth 1 https://github.com/memgraph/ai-toolkitWrote 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/release)<a href="https://agentmods.dev/skills/memgraph/ai-toolkit/release"><img src="https://agentmods.dev/badge/skills/memgraph/ai-toolkit/release/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/release"><img src="https://agentmods.dev/badge/skills/memgraph/ai-toolkit/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 36 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00035 | $0.01282 |
| Opus 5.5 | $0.00014 | $0.00513 |
| Sonnet 5.5 | $0.00007 | $0.00256 |
| Haiku 4.5 | $0.00003 | $0.00128 |
Grade A, and why
release 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Workflows
All release workflows are triggered via workflow_dispatch (manual) from the GitHub Actions tab. Bump the version in the subproject's pyproject.toml before dispatching.
Workflow files
| Workflow file | Package | What it does | Secrets used |
|---|---|---|---|
release-mcp-memgraph.yaml |
mcp-memgraph | Build & publish to PyPI + Docker Hub | PYPI_TOKEN, DOCKERHUB_USERNAME, DOCKERHUB_TOKEN |
release-toolbox.yaml |
memgraph-toolbox | Build & publish to PyPI | PYPI_TOKEN |
release-langchain-memgraph.yaml |
langchain-memgraph | Build & publish to PyPI | PYPI_TOKEN |
release-lightrag-memgraph.yaml |
lightrag-memgraph | Build & publish to PyPI | PYPI_TOKEN |
release-unstructured2graph.yaml |
unstructured2graph | Build & publish to PyPI | PYPI_TOKEN |
release-hygm.yaml |
hygm | Build & publish to PyPI | PYPI_TOKEN |
release-memgraph-context-graph.yaml |
memgraph-context-graph | Build & publish to PyPI | PYPI_TOKEN |
release-actions-graph.yaml |
actions-graph | Build & publish to PyPI | PYPI_TOKEN |
release-skills-graph.yaml |
skills-graph | Build & publish to PyPI | PYPI_TOKEN |
release-resources-graph.yaml |
resources-graph | Build & publish to PyPI | PYPI_TOKEN |
release-sessions-graph.yaml |
sessions-graph | Build & publish to PyPI | PYPI_TOKEN |
release-context-graph-spaces.yaml |
context-graph-spaces | Build & publish to PyPI | PYPI_TOKEN |
release-context-graph-viewer.yaml |
context-graph-viewer | Build & publish to PyPI | PYPI_TOKEN |
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 Changed · +2 lines 9ba29bacd5b3
- 4d ago Changed · +2 lines 0ffb6890ea19
- 7d ago Changed · +2 lines d2caa7948f45
- 11d ago Changed · +12 lines ab83a3b92f93
- 1mo ago First seen · 43 lines · 35 tokens per session scan A fe32a6385072
release is a skill published in the GitHub repository memgraph/ai-toolkit (116 stars, last pushed 2d ago), licensed MIT. It adds 35 tokens to every session and 1,282 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-08-30.
Other skills, from other repositories
deploy-akashic
A deployment procedure for an Akashic project that checks and merges an approved pull request, then submits the resulting code revision to update a Docker-based service. The host system handles stopping, moving, and restarting the service.
ferrogate-release
Use when cutting a FerroGate release — building the container image and publishing it to GHCR. Covers the standing directive to NOT use GitHub Actions (too slow) and instead gate on the local ferrogate-test suite then push locally, including the no-sudo/no-Docker host path (musl-static + crane). Use for "release"…
deployment-operations
Use when planning, executing, diagnosing, verifying, hardening, or rolling back deployments and runtime operations, including releases, Docker Compose, containers, systemd, Kubernetes, health checks, incidents, environment configuration, production or staging troubleshooting, and local development runtime startup.
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…