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.
git clone --depth 1 https://github.com/gulmezeren2-byte/erp-report-engineWrote 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/commands/gulmezeren2-byte/erp-report-engine/erp-schema)<a href="https://agentmods.dev/commands/gulmezeren2-byte/erp-report-engine/erp-schema"><img src="https://agentmods.dev/badge/commands/gulmezeren2-byte/erp-report-engine/erp-schema/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/commands/gulmezeren2-byte/erp-report-engine/erp-schema"><img src="https://agentmods.dev/badge/commands/gulmezeren2-byte/erp-report-engine/erp-schema.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.00029 | $0.00240 |
| Opus 5 | $0.00015 | $0.00120 |
| Sonnet 5 | $0.00006 | $0.00048 |
| Haiku 4.5 | $0.00003 | $0.00024 |
Grade A, and why
erp-schema 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 9d 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.
What it actually says
Show the canonical semantic model that erp-report-engine exposes to an agent: the entities, each column's type and meaning, and runnable example queries.
Use the Bash tool (no database or config required):
uvx --from erp-report-engine erp-report-engine schema
(or pipx run erp-report-engine schema, or erp-report-engine schema if the package is already installed.)
Then explain to the user:
- The canonical entities available (
orders,order_lines,inventory, and optionallyreceivables), and each one's grain. - That a semantic profile maps these canonical names to a specific ERP's real, cryptic tables (e.g.
LG_001_01_ORFICHEfor Logo Tiger) — the agent only ever sees the canonical names, never the raw schema. - That every query runs read-only and audited through the guard; a write, a file-reading function, or a second statement is refused before it reaches the database.
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.
- 9d ago First seen · 19 lines · 29 tokens per session scan A 030aa4073265
erp-schema is a command published in the GitHub repository gulmezeren2-byte/erp-report-engine (1 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 240 once invoked, about $0.0001 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-31.
Other commands, from other repositories
header
Commands built into the Metabase JAR for managing your instance, including database migrations, serialization, and administrative tasks.
footer
Open an SQL shell for the Metabase H2 DB.
psql-query
Run ad-hoc PostgreSQL analytics queries against dev/test database.
migrate
Generate and manage database migrations.
multi-backend
Run a backend-focused multi-model workflow for APIs, algorithms, data, and business logic.
d1-migration
Run D1 migration workflow — generate, inspect, apply.