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/AgamiAI/agami-coreWrote 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/agamiai/agami-core/agami)<a href="https://agentmods.dev/plugins/agamiai/agami-core/agami"><img src="https://agentmods.dev/badge/plugins/agamiai/agami-core/agami/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/agamiai/agami-core/agami"><img src="https://agentmods.dev/badge/plugins/agamiai/agami-core/agami.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
agami-core 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 yesterday.
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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
What it installs
The manifest is a name and a version. 9 skills travel with it, and installing the plugin installs all of them — 1,415 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill agami-reconcile A 153 tokens
- Skill agami-save-golden A 189 tokens
- Skill agami-eval A 119 tokens
- Skill agami-serve A 139 tokens
- Skill agami-connect B 162 tokens
- Skill agami-save-correction B 121 tokens
- Skill agami-model B 177 tokens
- Skill agami-query D 163 tokens
- Skill agami-deploy D 192 tokens
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.
- yesterday Changed 8448f9b9d9c3
- 2d ago Changed e204b874d803
- 3d ago Changed ca2f5377833d
- 4d ago Changed 12a87421a638
- 6d ago Changed 4c2548d05173
- 9d ago Changed c5e03bbbf384
- 15d ago Changed c22a84b7a7bf
- 20d ago Changed 0d1b9456b82e
- 23d ago Changed f56c44a5e243
- 27d ago First seen · 14 lines scan A 35ef7ea2ce34
agami-core is a plugin published in the GitHub repository AgamiAI/agami-core (29 stars, last pushed yesterday), with no licence file. 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-30.
Other plugins, from other repositories
pg-aiguide
PostgreSQL documentation and best practices through semantic search and curated skills, including TimescaleDB and Tiger Cloud ecosystem tools.
ecto
Compatibility namespace for the Elixir/Phoenix plugin's /ecto: commands.
metabase-ai-assistant
MCP Server for Metabase - 152 tools for dbt metadata sync, reverse lineage exposures, smart question creator, and enterprise BI.
sql
SQL specialist: query optimization, schema and index design, execution-plan analysis, and platform-specific features across PostgreSQL, MySQL, SQL Server, SQLite, and Oracle.
data-engineering-skills
Data architecture, streaming pipelines, transformations, SQL optimization, and performance engineering.
database-skill
Production Postgres survival skills: schema design, performant queries, safe migrations, connection pooling, autovacuum/bloat tuning, and advanced patterns (queues, partitioning, batched backfills).