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/gipert/dbettoWrote 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/plugins/gipert/dbetto/inspect-textdb)<a href="https://agentmods.dev/plugins/gipert/dbetto/inspect-textdb"><img src="https://agentmods.dev/badge/plugins/gipert/dbetto/inspect-textdb/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/plugins/gipert/dbetto/inspect-textdb"><img src="https://agentmods.dev/badge/plugins/gipert/dbetto/inspect-textdb.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
inspect-textdb 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.
What it actually says
{
"name": "inspect-textdb",
"description": "Load, query, and verify dbetto TextDB/Catalog/Props metadata (JSON/YAML text databases and time-validity files).",
"version": "1.0.0",
"author": { "name": "Luigi Pertoldi", "email": "[email protected]" }
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 192 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 First seen · 7 lines scan A e81cd6d96350
inspect-textdb is a plugin published in the GitHub repository gipert/dbetto (2 stars, last pushed today), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
metaxy marketplace
Plugin marketplace listing 1 plugin: metaxy.
metaxy
Provides the /metaxy skill for guidance on feature definitions, versioning, and metadata stores, plus MCP tools for exploring feature graphs and querying metadata.
data-engineering
ETL pipeline construction, data warehouse design, batch processing workflows, and data-driven feature development.
database-cloud-optimization
Database query optimization, cloud cost optimization, and scalability improvements.
database-design
Database architecture, schema design, and SQL optimization for production systems.
database-migrations
Database migration automation, observability, and cross-database migration strategies.