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/SummerEngine/summer-engine-agentWrote 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/summerengine/summer-engine-agent/gemini-extension)<a href="https://agentmods.dev/plugins/summerengine/summer-engine-agent/gemini-extension"><img src="https://agentmods.dev/badge/plugins/summerengine/summer-engine-agent/gemini-extension/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/summerengine/summer-engine-agent/gemini-extension"><img src="https://agentmods.dev/badge/plugins/summerengine/summer-engine-agent/gemini-extension.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
summer 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.
What it actually says
{
"name": "summer",
"version": "2.5.1",
"description": "Agent tooling for Summer Engine: MCP bridge, context primer, and game-dev skills. Use with the npm CLI for skill files on disk.",
"contextFileName": "GEMINI.md",
"mcpServers": {
"summer-engine": {
"command": "npx",
"args": ["summer-engine", "mcp"],
"cwd": "${extensionPath}"
}
},
"settings": [
{
"name": "enable_pre_commit_doctor",
"description": "Block git commits when summer doctor needs attention (off by default)",
"envVar": "SUMMER_PRE_COMMIT_DOCTOR",
"sensitive": false
}
]
}
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 First seen · 22 lines scan A fad426ef3431
summer is a plugin published in the GitHub repository SummerEngine/summer-engine-agent (59 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-09-08.
Other plugins, from other repositories
developer-essentials
Essential developer skills including Git workflows, SQL optimization, error handling, code review, E2E testing, authentication, debugging, and monorepo management.
worldos
WorldOS — simulate living, AI-generated worlds and play epic D&D 5e inside them. An AI DM generates stories live within persistent, canon-anchored worlds; deterministic 5e rules, searchable memory, a voiced AI companion, fully voice-acted.
git-pr
Committing, PR creation and review triage, and dependency upgrades.
prek
Set up git pre-commit hooks with prek, the fast pre-commit-compatible runner.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.
themes-example
themes-example. An open-source AI agent that brings the power of Gemini directly into your terminal.