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 widnyana/eyay-toolkitsnpx agentmods add plugins/widnyana/eyay-toolkits/block-forbidden-git-addgit clone --depth 1 https://github.com/widnyana/eyay-toolkitsWrote 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/widnyana/eyay-toolkits/block-forbidden-git-add)<a href="https://agentmods.dev/plugins/widnyana/eyay-toolkits/block-forbidden-git-add"><img src="https://agentmods.dev/badge/plugins/widnyana/eyay-toolkits/block-forbidden-git-add.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
block-forbidden-git-add 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 4d ago.
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": "block-forbidden-git-add",
"version": "1.0.0",
"description": "Denies git commands that stage protected paths, whole-tree adds, or rewrite history.",
"author": {
"name": "widnyana",
"email": "[email protected]"
},
"homepage": "https://github.com/widnyana/eyay-toolkits/tree/main/plugins/block-forbidden-git-add",
"repository": "https://github.com/widnyana/eyay-toolkits",
"license": "MIT",
"keywords": ["git", "hook", "safety", "guardrail"]
}
What it installs
The manifest is a name and a version. 1 hook travel with it, and installing the plugin installs all of 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.
- 4d ago First seen · 14 lines scan A 739f964300b1
block-forbidden-git-add is a plugin published in the GitHub repository widnyana/eyay-toolkits (6 stars, last pushed 5d 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-08-31.
Other plugins, from other repositories
cc-safety-net
Block destructive commands and secret access.
han-communication
Foundational communication plugin for the Han suite. Owns the canonical readability standard, the writing-voice profile, and the explanation standard for talking to a reader who will not implement the work, plus the readability-guidance skill that surfaces the first two into a calling skill's own context for in-voice…
handbook-agent-spec-kit
Spec-driven development workflow system with structured phases: Requirements → Design → Tasks → Implementation.
go-ultimate
Opinionated Go development skill — architecture, conventions, production readiness, repo/CI hygiene, review, and MCP/agent patterns.
claude-code
Meta-tools for Claude Code configuration and customization.
rails-consultant marketplace
Plugin marketplace listing 1 plugin: rails-consultant.