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 FortiumPartners/ensemblenpx agentmods add plugins/fortiumpartners/ensemble/gitgit clone --depth 1 https://github.com/FortiumPartners/ensembleWrote 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/fortiumpartners/ensemble/git)<a href="https://agentmods.dev/plugins/fortiumpartners/ensemble/git"><img src="https://agentmods.dev/badge/plugins/fortiumpartners/ensemble/git.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
ensemble-git 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": "ensemble-git",
"version": "5.2.1",
"description": "Git workflow automation and conventional commits",
"author": {
"name": "Fortium Partners",
"email": "[email protected]",
"url": "https://github.com/FortiumPartners"
},
"repository": "https://github.com/FortiumPartners/ensemble",
"license": "MIT",
"keywords": [
"git",
"workflow",
"commits",
"ensemble"
],
"commands": "./commands",
"skills": "./skills",
"agents": [
"./agents/git-workflow.md",
"./agents/github-specialist.md",
"./agents/release-agent.md"
]
}
What it installs
The manifest is a name and a version. 3 skills, 3 agents travel with it, and installing the plugin installs all of them — 203 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.
- yesterday First seen · 26 lines scan A 74264144881a
ensemble-git is a plugin published in the GitHub repository FortiumPartners/ensemble (11 stars, last pushed 1mo ago), 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-03.
Other plugins, from other repositories
commit-commands
Streamline your git workflow with simple commands for committing, pushing, and creating pull requests.
aidd-vcs
External artifacts: commit, pull-request, release-tag, issue-create.
comfyui-plugin
ComfyUI custom-node pack lifecycle - scaffold a pack, create + seed the repo, open the gitops adoption PR, publish to the Comfy Registry, and add README screenshots.
use-git
Git and GitHub CLI conventions for Claude Code: tmpfile patterns, HEREDOC commits, GPG signing, safe push practices, and permission-prompt avoidance.
android-release-bump
Reusable Android release workflow with version bumps, Play release notes, verification, optional headless emulator QA, and optional Play upload.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.