acumatica-gi-descriptions

acumatica-gi-descriptions is a skill for Claude Code, Codex from hallboys/MCP4Acumatica. It costs 150 tokens per session (2,169 once invoked), scanned A, original, Apache-2.0.

A description-writing skill for Acumatica Generic Inquiries, which are configured business-data searches and reports. It also describes their result columns using the inquiry's actual tables, joins, filters, and fields.

In plain words
What is it for?
Use it when preparing AI-facing descriptions for Acumatica inquiries and their columns, while separating platform-wide behavior from settings specific to one customer system.
Why use it?
It prevents an AI assistant from choosing or explaining an inquiry based only on a vague name and presenting an unsupported guess as fact.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when preparing AI-facing descriptions for Acumatica inquiries and their columns, while separating platform-wide behavior from settings specific to one customer system.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/hallboys/mcp4acumatica/acumatica-gi-descriptions
Install

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.

Any agent
npx skills add hallboys/MCP4Acumatica --skill acumatica-gi-descriptions
Clone the repo
git clone --depth 1 https://github.com/hallboys/MCP4Acumatica

Made for: Claude Code, Codex.

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.

agentmods badge for acumatica-gi-descriptions

README.md
[![agentmods](https://agentmods.dev/badge/skills/hallboys/mcp4acumatica/acumatica-gi-descriptions/github.svg)](https://agentmods.dev/skills/hallboys/mcp4acumatica/acumatica-gi-descriptions)
Your own site
<a href="https://agentmods.dev/skills/hallboys/mcp4acumatica/acumatica-gi-descriptions"><img src="https://agentmods.dev/badge/skills/hallboys/mcp4acumatica/acumatica-gi-descriptions/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.

agentmods 80×15 button for acumatica-gi-descriptions

Your own site · 80×15
<a href="https://agentmods.dev/skills/hallboys/mcp4acumatica/acumatica-gi-descriptions"><img src="https://agentmods.dev/badge/skills/hallboys/mcp4acumatica/acumatica-gi-descriptions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 150 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,169 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00150 $0.02169
Opus 5 $0.00075 $0.01085
Sonnet 5 $0.00030 $0.00434
Haiku 4.5 $0.00015 $0.00217

Measured 12d ago against content hash 6e4926c4a22b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

acumatica-gi-descriptions 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 12d ago.

The scan reads SKILL.md. This mod also ships 4 executable files (scripts/align_columns.mjs, scripts/audit_truncation.mjs, scripts/build_brief.mjs, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/acumatica-gi-descriptions/SKILL.md · 185 lines

How it starts

The opening of the file, as written. The whole thing — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Describing Generic Inquiries for AI consumption

A GI name tells a model almost nothing. PO-Receipt and PO Receipt History Analysis are different grains of different tables; GL-Trial Balance may not be a trial balance at all. When several GIs are exposed under names like these, a model picks by vibes and answers confidently from the wrong one.

The fix is a description per GI and per result column — but a description invented from the name just launders a guess into something that looks authoritative. Everything here exists to make descriptions fall out of the GI's actual design.

Tag legend

This skill mixes platform behaviour with instance-specific observations. Keep them apart, or you will carry one tenant's configuration into another as if it were a rule.

  • [UNIVERSAL] — Acumatica platform/API behaviour. Holds for any tenant on a comparable version. Safe to rely on; still confirm the release.
  • [TENANT] — depends on a specific instance's configuration, customization or data. Never copy the value into another engagement — only the lesson.

The pipeline

Work in this order. Each step feeds the next, and skipping the metadata pull is what produces plausible-sounding fiction.

  1. Inventory every GI, with parameter count and exposure flags.
  2. Select which GIs are worth describing. Most instances have hundreds; a large menu is as useless to a model as an undescribed one.
  3. Pull design metadata for the selection: result columns, joins, conditions.
  4. Build a per-GI brief that condenses that metadata into something writable.
  5. Draft GI-level, then column-level descriptions.
  6. Validate mechanically before anyone reads them.
  7. Load into Acumatica and verify by reading back.

references/workflow.md has the concrete steps, queries and slicing strategy. Read it when you start step 1.

The rules that actually bite

These are the ones that produce confidently wrong output if ignored. Each cost real debugging time.

Read the full file on GitHub · 185 lines

Files

What ships with it

8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

  1. 12d ago First seen · 185 lines · 150 tokens per session scan A 6e4926c4a22b

Subscribe to this mod's changes

acumatica-gi-descriptions is a skill published in the GitHub repository hallboys/MCP4Acumatica (17 stars, last pushed 9d ago), licensed Apache-2.0. It adds 150 tokens to every session and 2,169 once invoked, about $0.0007 per session on Opus 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.

Related

Other skills, from other repositories

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

unity-version-split

Split a C# file into Unity 6.5+ and pre-Unity 6.5 variants. Use when a file needs different implementations for different Unity versions due to API changes (e.g., EntityId vs int, GetEntityId vs GetInstanceID).

IvanMurzak/Unity-MCP · 59 tokens

opik-diagnose

Surface the Opik traces worth a developer's attention, ranked by signal — Diagnostics issues first, then errors, failed tool calls, latency, regressions, and low online-eval scores. With the Opik MCP connected it lists the project's agentinsightsissue entities, offers to turn Diagnostics on when the project has it…

comet-ml/opik-mcp · 187 tokens

specflow-use

To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.

griddynamics/rosetta · 27 tokens

mcp-google-map-project

Project knowledge for developing and maintaining @cablate/mcp-google-map. Architecture, Google Maps API guide, GIS domain knowledge, and design decisions. Read this skill to onboard onto the project or make informed development decisions.

cablate/mcp-google-map · 49 tokens

ue-mcp-epic-routing

Use when deciding between ue-mcp's native category actions and Epic's wrapped ToolsetRegistry tools (the epic actions, incl. the Blueprint graph DSL) for a task in Unreal. Pulls in when authoring Blueprint graph bodies, or any time both a native action and an epic action could do the job and you need to pick.

db-lyon/ue-mcp · 81 tokens