Borrowing it
Nothing to install: this file belongs to jrobelia/inventree-plugin-ai-toolkit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jrobelia/inventree-plugin-ai-toolkit/main/AGENTS.mdgit clone --depth 1 https://github.com/jrobelia/inventree-plugin-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/instructions/jrobelia/inventree-plugin-ai-toolkit/agents-md)<a href="https://agentmods.dev/instructions/jrobelia/inventree-plugin-ai-toolkit/agents-md"><img src="https://agentmods.dev/badge/instructions/jrobelia/inventree-plugin-ai-toolkit/agents-md/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/instructions/jrobelia/inventree-plugin-ai-toolkit/agents-md"><img src="https://agentmods.dev/badge/instructions/jrobelia/inventree-plugin-ai-toolkit/agents-md.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.01340 | $0.01340 |
| Opus 5.5 | $0.00536 | $0.00536 |
| Sonnet 5.5 | $0.00268 | $0.00268 |
| Haiku 4.5 | $0.00134 | $0.00134 |
Grade A, and why
inventree-plugin-ai-toolkit AGENTS.md 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 1mo 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent skills
Issue tracker
Track issues/PRDs in GitHub. See docs/agents/issue-tracker.md.
Triage labels
Use the five canonical labels. See docs/agents/triage-labels.md.
Domain docs
Multi-context: root CONTEXT.md/CONTEXT-MAP.md, shared reference contexts, and per-plugin CONTEXT.md/docs/adr/. See docs/agents/domain.md.
Skill discipline
A skill is a mode (planning, research, grilling, implementation). While a skill is active, obey it literally and default to planning and asking, not doing.
- Follow the active skill's explicit instructions (plan-only, HITL, stop-after-X).
- Don't write implementation code during planning or research.
- Stop between skill steps and wait for the user before continuing.
- Ask and wait during HITL workflows (
/grilling,/prototype,/domain-modeling). - If a step could be planning or doing, ask before writing/editing files.
- Wayfinder: one ticket per session; research yields decision notes; map charting starts with
/grilling+/domain-modeling.
Session and handoff boundaries
- Stop when a skill says a phase is one session's work.
- "Continue" means continue the current step only, not the next ticket/phase.
- Stop on correction; fix the process and ask whether to resume or restart.
- Keep scratch work out of the repo unless agreed.
User interaction
- The user is a mechanical engineer and domain expert; explain what you are doing.
- If a request is ambiguous or next steps are unclear, do not guess. Ask follow-up questions and wait.
Toolkit context
- This repository is the InvenTree Plugin AI Toolkit.
plugins/contains independent git repositories, one per plugin.- Each plugin has its own
AGENTS.mdanddocs/agents/; respect them when working inside a plugin directory. - Shared domain language lives in
CONTEXT-MAP.mdandC:\Software Projects\inventree-plugin-ai-toolkit\docs\reference\inventree-bom-build-buy-suite\. - Devin-specific skills live in
.devin/skills/at the toolkit root. Shared/legacy skills remain in.agents/skills/. reference/contains theinventree-sourceandplugin-creatorsubmodules; use them as live source code and pattern reference when implementing plugins.- Use the devcontainer for consistent development and testing.
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.
- 1mo ago Changed · +2 lines · +130 tokens per session f25506518cfb
- 1mo ago First seen · 73 lines · 1,210 tokens per session scan A f55000236e59
inventree-plugin-ai-toolkit AGENTS.md is an instructions file published in the GitHub repository jrobelia/inventree-plugin-ai-toolkit (1 stars, last pushed 1mo ago), licensed MIT. It adds 1,340 tokens to every session, about $0.0054 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-31.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.