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/deploy-inventree-plugin)<a href="https://agentmods.dev/skills/jrobelia/inventree-plugin-ai-toolkit/deploy-inventree-plugin"><img src="https://agentmods.dev/badge/skills/jrobelia/inventree-plugin-ai-toolkit/deploy-inventree-plugin.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.00039 | $0.00998 |
| Opus 5 | $0.00019 | $0.00499 |
| Sonnet 5 | $0.00008 | $0.00200 |
| Haiku 4.5 | $0.00004 | $0.00100 |
Grade C, and why
deploy-inventree-plugin scanned grade C 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.
Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
"key_file": "C:/Users/<user>/.ssh/id_ed25519" How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy an InvenTree plugin
Purpose: Install a built .whl package on a remote InvenTree server and verify it comes back healthy.
One-liner
From the toolkit root, on the Windows host:
.\scripts\Deploy-Plugin.ps1 -Plugin "<PluginFolderName>" -Server staging
Workflow
1. Identify the plugin and target server
Ask the user for the plugin folder name and confirm staging or production. For production, the script requires typed yes confirmation and should only run after staging has been manually tested.
2. Verify server configuration
Open config\servers.json and confirm the requested server entry exists with at least:
{
"url": "https://staging.example.com",
"ssh": {
"host": "staging.server.com",
"user": "inventree",
"port": 22,
"key_file": "C:/Users/<user>/.ssh/id_ed25519"
}
}
Optional overrides (if auto-detection fails or you want to be explicit):
| Field | Default | Meaning |
|---|---|---|
compose_dir |
auto-detected | Directory containing the InvenTree compose.yaml / docker-compose.yml |
service_name |
inventree-server |
Docker Compose service name for the InvenTree server container |
data_dir |
<compose_dir>/inventree-data |
Host path where the wheel is uploaded before being mounted into the container |
container_data_path |
/home/inventree/data |
Container path matching the data volume mount |
docker_command |
auto-detected (docker compose or docker-compose) |
Docker Compose command on the remote |
3. Build if needed
Deploy-Plugin.ps1 calls scripts/build-plugin.sh inside the devcontainer if the dist/ directory is missing or if source files are newer than the wheel. To force a build, use -Build.
4. Deploy
Run the one-liner from the top of this skill, adding switches as needed.
Switches:
| Switch | Meaning |
|---|---|
-Build |
Force a build before deploying |
-SkipRestart |
Install the wheel but do not restart the InvenTree container |
-SkipCollect |
Skip running collectplugins after restart |
-NoVerify |
Skip the post-deploy health check |
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 · 101 lines · 39 tokens per session scan C ada0f3306490
deploy-inventree-plugin is a skill published in the GitHub repository jrobelia/inventree-plugin-ai-toolkit (1 stars, last pushed 20d ago), licensed MIT. It adds 39 tokens to every session and 998 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (reaches for credential files). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
deployment-sop
Deployment workflows, pre-deploy validation, smoke testing, and rollback procedures. Use when deploying to staging or production, running smoke tests, validating deployments, or planning rollback. Do NOT use for local development or CI pipeline configuration.
drawio
WORKFLOW SKILL — Generate Azure architecture diagrams in .drawio via simonkurtz-MSFT MCP server (full Azure icon set, batch creation, transactional mode). Covers architecture, dependency, runtime-flow, and as-built diagrams. WHEN: 'draw.io diagram', 'Azure architecture diagram', 'as-built diagram', 'runtime flow…
azure-bicep-patterns
UTILITY SKILL — Reusable Azure Bicep patterns: hub-spoke, private endpoints, diagnostics, AVM composition. WHEN: "hub-spoke Bicep", "private endpoint module", "diagnostic settings", "AVM Bicep composition". USE FOR: Bicep template design, hub-spoke networking, private endpoint patterns, AVM modules. DO NOT USE FOR…
deploy-model
Unified Azure OpenAI model deployment skill with intelligent intent-based routing. Handles quick preset deployments, fully customized deployments (version/SKU/capacity/RAI policy), and capacity discovery across regions and projects. USE FOR: deploy model, deploy gpt, create deployment, model deployment, deploy openai…
azure-governance-discovery
ANALYSIS SKILL — Azure Policy discovery: effective assignments (incl. MG-inherited), definitions/exemptions, effect classification, emits governance-constraints JSON. WHEN: 'Azure policy discovery', 'effective policy assignments', 'governance constraints', '04g-Governance Phase 1', 'refresh governance JSON'. DO NOT…
azure-defaults
UTILITY SKILL — Applies canonical Azure defaults through an IaC workflow covering governance precedence, CAF naming, AVM-first composition, unique suffixes, cost monitoring, VNet planning, and lifecycle checks. WHEN: "Azure naming convention", "CAF naming", "resource tags", "AVM module", "security baseline", "region…