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/mgiovani/cc-arsenalWrote 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/mgiovani/cc-arsenal/cc-arsenal-git)<a href="https://agentmods.dev/plugins/mgiovani/cc-arsenal/cc-arsenal-git"><img src="https://agentmods.dev/badge/plugins/mgiovani/cc-arsenal/cc-arsenal-git/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/mgiovani/cc-arsenal/cc-arsenal-git"><img src="https://agentmods.dev/badge/plugins/mgiovani/cc-arsenal/cc-arsenal-git.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
cc-arsenal-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 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": "cc-arsenal-git",
"source": "./",
"strict": false,
"description": "Git and GitHub workflow skills: conventional commits, PR creation, release management, gitflow branching, GitHub Issues daily planner, branch syncing, and code-done-to-merged shipping",
"version": "5.2.0",
"author": {
"name": "Giovani Moutinho",
"email": "[email protected]",
"url": "https://github.com/mgiovani/cc-arsenal"
},
"homepage": "https://github.com/mgiovani/cc-arsenal",
"repository": "https://github.com/mgiovani/cc-arsenal",
"license": "MIT",
"keywords": [
"git",
"github",
"commits",
"pull-requests",
"conventional-commits",
"releases",
"issues"
],
"category": "development",
"skills": [
"./skills/git-commit/",
"./skills/git-create-pr/",
"./skills/git-release/",
"./skills/gitflow/",
"./skills/gh-daily/",
"./skills/git-sync/",
"./skills/ship/"
]
}What it installs
The manifest is a name and a version. 7 skills travel with it, and installing the plugin installs all of them — 921 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
2 files beside marketplace.json#cc-arsenal-git 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 · 34 lines scan A 9c8e14505239
cc-arsenal-git is a plugin published in the GitHub repository mgiovani/cc-arsenal (8 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-09-10.
Other plugins, from other repositories
prflow
Turn feature requests into review-ready pull requests: issue, implementation, tests, a review-and-fix loop, and docs. Runs locally or on GitHub Actions, and is built for complex brownfield repos. Each week its retrospective reads what you actually merged and proposes improvements to your skill extensions.
ensemble-git
Git workflow automation and conventional commits.
gitlab
Agent-callable GitLab tools — manage issues and merge requests, review diffs, commit files, run pipelines, and search. Use when the user mentions GitLab or wants to review or merge an MR, commit code, run CI, or manage issues — even if they don't name GitLab explicitly.
jj
Jujutsu (jj) version control skills for committing, pushing, opening PRs, and rebasing.
cas
Evidence-driven research, guarded Codex delegation, explicit native parallelism, secret protection, and approval gates for rm, commit, and push.
g-forge
Educated, enforced project management for AI development - a PM layer, parallel implementation waves, and a git-hook commit gate that can't be skipped. Make any model ship like a senior team.