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/EternallLight/tgc-skillsWrote 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/eternalllight/tgc-skills/tgc-skills)<a href="https://agentmods.dev/plugins/eternalllight/tgc-skills/tgc-skills"><img src="https://agentmods.dev/badge/plugins/eternalllight/tgc-skills/tgc-skills/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/eternalllight/tgc-skills/tgc-skills"><img src="https://agentmods.dev/badge/plugins/eternalllight/tgc-skills/tgc-skills.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
tgc-skills 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 10d 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": "tgc-skills",
"description": "A shipping pipeline for Claude Code: orchestrate a locked plan with fresh-context agents, polish the diff, ship it to a reviewed PR, run an agent review-fix loop until clean, and clean up after merge.",
"version": "0.1.0",
"author": {
"name": "Andrey Gruniov",
"url": "https://github.com/EternallLight"
},
"homepage": "https://github.com/EternallLight/tgc-skills",
"repository": "https://github.com/EternallLight/tgc-skills",
"license": "MIT",
"keywords": ["orchestration", "code-review", "shipping", "pipeline", "agents", "pr", "workflow"]
}
What it installs
The manifest is a name and a version. 9 skills travel with it, and installing the plugin installs all of them — 614 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 10d ago First seen · 14 lines scan A adc29849b998
tgc-skills is a plugin published in the GitHub repository EternallLight/tgc-skills (8 stars, last pushed 1mo 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
fuse-rules
Global rules for all Claude Code sessions: APEX workflow, SOLID/DRY enforcement, project detection, agent delegation, frontend/git standards.
lanes-bridges
Bridge Lanes with GitHub and Linear: import issues, batch-spawn a session per ticket, and post results back upstream. Split out of lanes-desktop in 0.7.0.
dev
Ralph Loop development lifecycle: ticket assignment through merge-ready PR. Includes start, code, pr, poll, ci, backport, work, grill-with-docs, to-prd, to-issues, handoff, and qe.
workbench
Ticket-to-PR development workflow: triage, plan with verified citations, implement inside the plan, review, commit, PR. Pluggable issue trackers (Jira, Azure DevOps, GitHub Issues) or a backlog in the repo, so it works with no tracker at all.
ooda-loop marketplace
Plugin marketplace listing 1 plugin: ooda-loop.
vibe-flow
Orchestration skills for Vibe Kanban: plan → ship → link → review → merge with wave-based dispatch, executor routing (T0-T4), and autonomous fix loops.