github-elements-orchestrator

github-elements-orchestrator is an agent for coding agents from Emasoft/ghe-marketplace. It costs 133 tokens per session (3,287 once invoked), scanned A, original, MIT.

An agent for coordinating GitHub Elements issues, discussion threads, maintenance work, and development, testing, and review workflows.

In plain words
What is it for?
Use it to manage issue work, coordinate threads, run maintenance cycles, enforce process rules, and report problems.
Why use it?
It keeps related work moving through the required thread stages and applies the project's workflow rules.

Agent

Part of the ghe plugin — 10 skills, 2 commands, 10 agents, 5 hooks shipped together

Install

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.

agentmods
npx agentmods add agents/emasoft/ghe-marketplace/github-elements-orchestrator
Clone the repo
git clone --depth 1 https://github.com/Emasoft/ghe-marketplace

Or install ghe, the plugin that ships this one along with the rest of its 10 skills, 2 commands, 10 agents, 5 hooks.

Per session 133 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,287 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00133 $0.03287
Opus 5 $0.00067 $0.01643
Sonnet 5 $0.00027 $0.00657
Haiku 4.5 $0.00013 $0.00329

Measured 3d ago against content hash 3ffb7186ec7c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

github-elements-orchestrator 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 3d 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.

plugins/ghe/agents/github-elements-orchestrator.md · 372 lines

How it starts

The opening of the file, as written. The whole thing — 372 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Quick References

Shared Documentation (see agents/references/):

IRON LAW: User Specifications Are Sacred

THIS LAW IS ABSOLUTE AND ADMITS NO EXCEPTIONS.

  1. Every word the user says is a specification - follow verbatim, no errors, no exceptions
  2. Never modify user specs without explicit discussion - if you identify a potential issue, STOP and discuss with the user FIRST
  3. Never take initiative to change specifications - your role is to implement, not to reinterpret
  4. If you see an error in the spec, you MUST:
    • Stop immediately
    • Explain the potential issue clearly
    • Wait for user guidance before proceeding
  5. No silent "improvements" - what seems like an improvement to you may break the user's intent

Violation of this law invalidates all work produced.

Background Agent Boundaries

When running as a background agent, you may ONLY write to:

  • The project directory and its subdirectories
  • The parent directory (for sub-git projects)
  • ~/.claude (for plugin/settings fixes)
  • /tmp

Do NOT write outside these locations.


Settings Awareness

Check .claude/ghe.local.md for project settings:

  • enabled: If false, skip all GitHub Elements operations
  • enforcement_level: strict (block) / standard (warn) / lenient (advise)
  • serena_sync: Whether to spawn memory-sync agent
  • notification_level: verbose/normal/quiet

Defaults if no settings file: enabled=true, enforcement=standard, serena_sync=true, notification=normal


GHE_REPORTS Rule (MANDATORY)

ALL reports MUST be posted to BOTH locations:

  1. GitHub Issue Thread - Full report text (NOT just a link!)
  2. GHE_REPORTS/ - Same full report text (FLAT structure, no subfolders!)

Read the full file on GitHub · 372 lines

Changes

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.

  1. 3d ago First seen · 372 lines · 0 tokens per session scan A 3ffb7186ec7c

Subscribe to this mod's changes

github-elements-orchestrator is an agent published in the GitHub repository Emasoft/ghe-marketplace (4 stars, last pushed 8mo ago), licensed MIT. It adds 133 tokens to every session and 3,287 once invoked, about $0.0007 per session on Opus 5. 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.