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/yonatangross/orchestkitWrote 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/yonatangross/orchestkit/promote-lights)<a href="https://agentmods.dev/plugins/yonatangross/orchestkit/promote-lights"><img src="https://agentmods.dev/badge/plugins/yonatangross/orchestkit/promote-lights/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/yonatangross/orchestkit/promote-lights"><img src="https://agentmods.dev/badge/plugins/yonatangross/orchestkit/promote-lights.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
promote-lights 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": "promote-lights",
"version": "0.0.13",
"description": "Shows CI status lights above the prompt while a promote PR (base main) is open. One REST page per minute, PR-open only. Cancelled is not-pass.",
"author": {
"name": "OrchestKit"
},
"license": "MIT"
}
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 Changed a6db1cb18184
- 11d ago Changed e64b3b4ab061
- 20d ago Changed 28d4d52ade93
- 21d ago Changed · +2 lines e1dff72c6a95
- 1mo ago First seen · 8 lines scan A e4cc6eb03724
promote-lights is a plugin published in the GitHub repository yonatangross/orchestkit (295 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-17.
Other plugins, from other repositories
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says.
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.
claude-plugins-official marketplace
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations.
knowledge-work-plugins marketplace
Plugin marketplace listing 123 plugins: noibu, productivity, enterprise-search, cowork-plugin-management, sales.
code-modernization
Guided modernization for any legacy codebase: start with /modernize, get an assessment, an interactive map, the business rules mined from the code, and a plan you approve, then an upgrade, a rewrite or a rebuild with independent proof that the new code behaves like the old. Includes security hardening, a one-page…