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/Eigenwise/eigenwise-toolshedWrote 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/eigenwise/eigenwise-toolshed/quality-gate)<a href="https://agentmods.dev/plugins/eigenwise/eigenwise-toolshed/quality-gate"><img src="https://agentmods.dev/badge/plugins/eigenwise/eigenwise-toolshed/quality-gate/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/eigenwise/eigenwise-toolshed/quality-gate"><img src="https://agentmods.dev/badge/plugins/eigenwise/eigenwise-toolshed/quality-gate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
quality-gate 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": "quality-gate",
"version": "1.0.0",
"description": "Local JavaScript and TypeScript function complexity and measured V8 coverage, with per-function CRAP scores strictly below 6.",
"author": { "name": "Eigenwise", "email": "[email protected]" },
"homepage": "https://github.com/Eigenwise/eigenwise-toolshed/tree/main/plugins/quality-gate",
"repository": "https://github.com/Eigenwise/eigenwise-toolshed",
"license": "MIT",
"suiteTimeout": 120000,
"types": "./types/index.d.ts",
"keywords": ["quality", "complexity", "coverage", "crap", "typescript"]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 38 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 · 13 lines scan A fccfc5a9cb6e
quality-gate is a plugin published in the GitHub repository Eigenwise/eigenwise-toolshed (280 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-10-19.
Other plugins, from other repositories
quality-assurance-suite
Find gaps that could break a release, mislead a maintainer, or make a passing test meaningless.
mattpocock-skills
Skills adapted from Matt Pocock's public collection.
sound
Code taste as installable rules. Probe a repo's stack, select only the rules its code shows a surface for (evidence-cited per rule), confirm, and scaffold a browsable .claude/sound/ rule map (surfaced by the sound:prime skill). Installed rules are user-owned; re-runs reconcile.
jira-pack
Issue-tracker pack: /jira-fix takes a ticket link of any type, verifies tracker access, classifies it as a defect or a change, reproduces the defect or writes a failing acceptance test for the change, routes the work to core executors, comments back with evidence and moves the ticket to the QA column. Opt-in; requires.
xonovex-core
Apply software design, testing, review, version control, credentials, and accessibility practices.
atlas-review
Takes the open pull requests of the Atlas/Bella monorepo from arrival to reviewed, fixed, merged, pushed and reported. The review itself is code-review:code-review, which is read-only, so resolving what it finds is this skill's own stage and the reason it exists. Lands by rebase rather than merge commit, pulls so…