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/Junhanliu-dev/espalier-engineeringWrote 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/junhanliu-dev/espalier-engineering/marketplace)<a href="https://agentmods.dev/plugins/junhanliu-dev/espalier-engineering/marketplace"><img src="https://agentmods.dev/badge/plugins/junhanliu-dev/espalier-engineering/marketplace/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/junhanliu-dev/espalier-engineering/marketplace"><img src="https://agentmods.dev/badge/plugins/junhanliu-dev/espalier-engineering/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
espalier-engineering marketplace 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": "espalier-engineering",
"owner": {
"name": "Zayhan"
},
"description": "Marketplace publishing the Espalier Engineering plugin \u2014 auto-discovered, project-specific guardrails for AI coding agents",
"version": "0.30.0",
"plugins": [
{
"name": "espalier-engineering",
"source": {
"source": "github",
"repo": "Junhanliu-dev/espalier-engineering"
},
"description": "Train your AI coders the way you'd train a vine \u2014 discover your codebase's actual patterns, then encode them as rules, skills, agents, hooks, and a guided pipeline so generated code lands inside your conventions on the first try, not the fifth",
"version": "0.30.0",
"author": {
"name": "Zayhan"
},
"homepage": "https://github.com/Junhanliu-dev/espalier-engineering",
"repository": "https://github.com/Junhanliu-dev/espalier-engineering",
"license": "MIT"
}
]
}
The plugins it lists here
This marketplace lists 1 plugin kept in the same repository. Each has its own page, its own measurements and its own install command.
What ships with it
1 file beside marketplace.json 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 Changed 959cb1cb01b5
- 2d ago Changed 6fe4ecc4f4aa
- 1mo ago Changed 1f49af61ae8b
- 1mo ago Changed 83c225af41cb
- 1mo ago Changed 1dae2ded2cfc
- 1mo ago First seen · 26 lines scan A 4d3dea3f821e
espalier-engineering marketplace is a plugin published in the GitHub repository Junhanliu-dev/espalier-engineering (69 stars, last pushed yesterday), 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-30.
Other plugins, from other repositories
api-authentication
Secure API authentication with JWT, OAuth 2.0, API keys. Use for authentication systems, third-party integrations, service-to-service communication, or encountering token management, security headers, auth flow errors.
csrf-protection
Implements CSRF protection using synchronizer tokens, double-submit cookies, and SameSite attributes. Use when securing web forms, protecting state-changing endpoints, or implementing defense-in-depth authentication.
aceternity-ui
100+ animated React components (Aceternity UI) for Next.js with Tailwind. Use for hero sections, parallax, 3D effects, or encountering animation, shadcn CLI integration errors.
cloudflare-sandbox
Cloudflare Sandboxes SDK for secure code execution in Linux containers at edge. Use for untrusted code, Python/Node.js scripts, AI code interpreters, git operations.
rails-consultant
A collection of skills for Rails development and consulting, with an emphasis on learning, communication, and client success.
spec-first marketplace
Spec-first development: define a spec, implement it, and generate docs.