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.
/plugin marketplace add glincker/claude-code-marketplacenpx agentmods add plugins/glincker/claude-code-marketplace/backend-architectgit clone --depth 1 https://github.com/glincker/claude-code-marketplaceWrote 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/glincker/claude-code-marketplace/backend-architect)<a href="https://agentmods.dev/plugins/glincker/claude-code-marketplace/backend-architect"><img src="https://agentmods.dev/badge/plugins/glincker/claude-code-marketplace/backend-architect.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
backend-architect 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 today.
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": "backend-architect",
"source": "./skills/agents/backend-architect",
"description": "Backend architecture agent for scalable API and database design",
"version": "1.0.0",
"keywords": [
"backend",
"architecture",
"api",
"agent"
]
}What ships with it
1 file beside marketplace.json#backend-architect 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.
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.
- today First seen · 12 lines scan A 1f66328215d8
backend-architect is a plugin published in the GitHub repository glincker/claude-code-marketplace (36 stars, last pushed 9mo ago), licensed Apache-2.0. 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-09-03.
Other plugins, from other repositories
google-plugins marketplace
Plugin marketplace listing 17 plugins: alloydb, alloydb-omni, bigtable, cloud-sql-mysql, cloud-sql-postgresql.
butterbase-skills
Build full-stack apps with Butterbase — AI-Native Backend-as-a-Service. Skills for app creation, schema design, frontend deployment, RLS debugging, serverless functions, and contributing.
sql-database-pipeline
Build SQL database pipelines with dlt: connect to any SQL source, load tables to a destination, tune performance with backends.
sap-abap
Comprehensive ABAP development skill for SAP systems. Use when writing ABAP code, working with internal tables, structures, ABAP SQL, object-oriented programming, RAP (RESTful Application Programming Model), CDS views, EML statements, ABAP Cloud development, string processing, dynamic programming, RTTI/RTTC, field…
reporting-and-database-access
MATLAB, Database Toolbox, MATLAB Report Generator, Parallel Computing Toolbox, and Simulink Report Generator.
postgres-sql
The PostgreSQL SQL dialect & data types that set Postgres apart from generic SQL. Use when writing or debugging Postgres-specific SQL — upsert (ON CONFLICT), RETURNING, MERGE, CTEs, window frames, GROUPING SETS, LATERAL, generated/identity columns, partitioning, jsonb/jsonpath/SQL-JSON (JSONTABLE), array.