Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/jrobelia/inventree-plugin-ai-toolkit/test-inventree-devcontainer)<a href="https://agentmods.dev/skills/jrobelia/inventree-plugin-ai-toolkit/test-inventree-devcontainer"><img src="https://agentmods.dev/badge/skills/jrobelia/inventree-plugin-ai-toolkit/test-inventree-devcontainer.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.00062 | $0.01913 |
| Opus 5 | $0.00031 | $0.00957 |
| Sonnet 5 | $0.00012 | $0.00383 |
| Haiku 4.5 | $0.00006 | $0.00191 |
Grade A, and why
test-inventree-devcontainer scanned grade A with 1 finding 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 8d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl.exe -s --max-time 10 http://localhost:8001/api/system/health/ How it starts
The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test the InvenTree Plugin AI Toolkit devcontainer
Purpose: Verify that the devcontainer image builds, the one-time setup completes, and the InvenTree dev server serves the expected version.
One-liner
From the toolkit root, after updating submodules and wiping stale volumes:
docker compose -f .devcontainer/docker-compose.yml -f .devcontainer/docker-compose.frontend-volumes.yml up -d --build
docker compose -f .devcontainer/docker-compose.yml -f .devcontainer/docker-compose.frontend-volumes.yml exec -u vscode toolkit bash -c "cd /workspace && bash .devcontainer/postCreateCommand.sh"
cd /workspace/reference/inventree-source && invoke dev.server -a 0.0.0.0:8001
Workflow
1. Align the InvenTree source submodule
The devcontainer points at reference/inventree-source and uses invoke tasks from it. The committed submodule pointer may lag origin/stable, which is where a new InvenTree release (and a new MIN_PYTHON_VERSION) can land.
git submodule update --init --recursive --remote --force
Completion criterion: reference/inventree-source/src/backend/InvenTree/InvenTree/version.py shows the expected INVENTREE_SW_VERSION and MIN_PYTHON_VERSION. If the goal is to validate a Python version bump, MIN_PYTHON_VERSION must match the devcontainer base image.
2. Wipe stale data volumes when the Python base image changes
/inventree-data/venv is stored on a named Docker volume. postCreateCommand.sh creates it with python3 -m venv, which fails if the directory already exists. After a Python version bump, start from an empty volume.
docker compose -f .devcontainer/docker-compose.yml -f .devcontainer/docker-compose.frontend-volumes.yml down -v
Completion criterion: docker volume ls no longer shows devcontainer_inventree-data before the next up.
3. Build and verify the toolkit image
docker compose -f .devcontainer/docker-compose.yml -f .devcontainer/docker-compose.frontend-volumes.yml build --no-cache toolkit
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.
- 8d ago First seen · 141 lines · 62 tokens per session scan A 57ccd9f6dcad
test-inventree-devcontainer is a skill published in the GitHub repository jrobelia/inventree-plugin-ai-toolkit (1 stars, last pushed 20d ago), licensed MIT. It adds 62 tokens to every session and 1,913 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
dotnet-testing-advanced-tunit-advanced
A guide for advanced TUnit testing in .NET. TUnit is a testing framework; the guide covers tests driven by data, dependency injection, integration tests, retries, time limits, and filtering.
dotnet-testing-advanced-aspire-testing
A guide to testing .NET Aspire distributed applications, which are programs made of several coordinated services. It covers tests that run the real service setup through an AppHost, the project that describes how those services are arranged.
dotnet-testing-advanced-aspnet-integration-testing
Guidance for ASP.NET Core integration tests, which test several web application parts together through HTTP requests and responses.
dotnet-testing-advanced-testcontainers-database
Guidance for integration tests that use Testcontainers, a library that starts real services in temporary Docker containers, with databases such as SQL Server, PostgreSQL, or MySQL.
dotnet-testing-advanced-webapi-integration-testing
Guidance for ASP.NET Core Web API integration tests, including HTTP endpoints and ProblemDetails, a standard format for describing API errors.
verify
Build the computer-use-demo image and drive the Streamlit UI headlessly to verify changes end-to-end.