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 thanhtung2693/specgatenpx agentmods add plugins/thanhtung2693/specgate/local_plugin_assetsgit clone --depth 1 https://github.com/thanhtung2693/specgateGrade A, and why
specgate 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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- specgate — 100% identical, 0 lines differ
What it actually says
{
"name": "specgate",
"version": "0.2.3",
"description": "Focused SpecGate skills for project setup, work preparation, and delivery.",
"author": {
"name": "Thanh Tung"
},
"homepage": "https://github.com/thanhtung2693/specgate",
"repository": "https://github.com/thanhtung2693/specgate",
"license": "Apache-2.0",
"keywords": [
"specgate",
"sdlc",
"spec-driven",
"setup",
"readiness",
"handoff",
"coding-agent",
"delivery"
],
"skills": "./skills/",
"hooks": "./hooks/hooks-claude.json"
}
What ships with it
1 file beside plugin.json 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.
- 2d ago First seen · 24 lines scan A 69e32bd94967
specgate is a plugin published in the GitHub repository thanhtung2693/specgate (5 stars, last pushed 12d ago), licensed Apache-2.0. 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
pad
Talk to your project. Pad is local-first project management for developers and AI agents — this plugin gives Claude Code a conversational Pad skill, typed shortcuts (/pad:status, /pad:capture, /pad:onboard, /pad:connect, /pad:disconnect), and consent-gated live item-change notifications.
draft
Context-Driven Development: draft specs and plans before implementation. Structured workflows for features and fixes.
easychamp
EasyChamp tournament management — create sports leagues and tournaments, build brackets, schedule matches with venues, and record results. Backed by the EasyChamp MCP server.
throughline
Task-Track & Handoff for AI agents on long, multi-session work. Within a session it pins one ⭐️ MAIN goal (frozen title, explicit verdict at close) in an emoji-tagged task list so the agent doesn't drift; across sessions or agents it writes a plain-markdown handoff the next agent re-derives before trusting. Not for…
papi
Persistent project management inside your AI coding tool. PAPI plans what to build next, tracks every decision, and keeps projects coherent across sessions — so a new session starts where the last one left off instead of from nothing.
the-loop
An opinionated product-development-lifecycle harness that lets coding agents deliver work items end-to-end, with minimal human intervention, through a predictable loop of plan, execute, self-review, critic-review and escalate.