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 Emasoft/ghe-marketplacenpx agentmods add plugins/emasoft/ghe-marketplace/ghegit clone --depth 1 https://github.com/Emasoft/ghe-marketplaceWrote 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/emasoft/ghe-marketplace/ghe)<a href="https://agentmods.dev/plugins/emasoft/ghe-marketplace/ghe"><img src="https://agentmods.dev/badge/plugins/emasoft/ghe-marketplace/ghe.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
ghe 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 6d 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": "ghe",
"version": "0.6.64",
"description": "GHE (GitHub-Elements) - Automated project management for Claude Code using GitHub Issues as persistent memory with orchestrated DEV/TEST/REVIEW workflow.",
"author": {
"name": "Emasoft",
"email": "[email protected]"
},
"license": "MIT",
"repository": "https://github.com/Emasoft/ghe-marketplace",
"keywords": [
"ghe",
"github-elements",
"project-management",
"github",
"issues",
"memory",
"workflow",
"orchestration",
"agents",
"DEV",
"TEST",
"REVIEW"
]
}
What it installs
The manifest is a name and a version. 10 skills, 2 commands, 10 agents, 5 hooks travel with it, and installing the plugin installs all of them — 3,503 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill github-elements-tracking A 123 tokens
- Skill ghe-thread-manager A 229 tokens
- Skill ghe-design A 40 tokens
- Skill ghe-changelog A 64 tokens
- Skill ghe-requirements A 62 tokens
- Skill ghe-report A 453 tokens
- Skill ghe-checkpoint A 338 tokens
- Skill ghe-status A 288 tokens
- Skill ghe-claim A 326 tokens
- Skill ghe-transition A 405 tokens
- Command setup B 8 tokens
- Command spawn-agent C 15 tokens
- Agent review-thread-manager A 188 tokens
- Agent phase-gate A 132 tokens
- Agent dev-thread-manager A 137 tokens
- Agent enforcement A 93 tokens
- Agent github-elements-orchestrator A 133 tokens
- Agent reporter A 80 tokens
- Agent test-thread-manager A 139 tokens
- Agent ci-issue-opener A 91 tokens
- Agent memory-sync A 84 tokens
- Agent pr-checker A 75 tokens
- Hook PostToolUse A not measured
- Hook PreToolUse A not measured
- Hook SessionStart A not measured
- Hook Stop A not measured
- Hook UserPromptSubmit A not measured
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.
- 6d ago First seen · 26 lines scan A 0b915be2050d
ghe is a plugin published in the GitHub repository Emasoft/ghe-marketplace (4 stars, last pushed 9mo 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.
project-shipper
PROACTIVELY use this agent when approaching launch milestones, release deadlines, or go-to-market activities. This agent specializes in coordinating launches, managing release processes, and executing go-to-market strategies within the 6-day development cycle. Should be triggered automatically when release dates are…
odin-git
ODIN workflows for commits, branches, pull requests, review feedback, and issue tracking.
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.
tgc-skills
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.
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.