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.
npx agentmods add commands/emasoft/ghe-marketplace/setupgit 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/commands/emasoft/ghe-marketplace/setup)<a href="https://agentmods.dev/commands/emasoft/ghe-marketplace/setup"><img src="https://agentmods.dev/badge/commands/emasoft/ghe-marketplace/setup.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00008 | $0.04016 |
| Opus 5 | $0.00004 | $0.02008 |
| Sonnet 5 | $0.00002 | $0.00803 |
| Haiku 4.5 | $0.00001 | $0.00402 |
Grade B, and why
setup scanned grade B with 1 finding 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 5d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
if ! grep -q ".claude/\*.local.md" .gitignore 2>/dev/null; then How it starts
The opening of the file, as written. The whole thing — 559 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Elements Setup Command
This command creates .claude/ghe.local.md with project configuration.
CRITICAL: repo_path Is Sacred
The repo_path field is the MOST IMPORTANT setting. All agents, hooks, and scripts use this path to find:
REQUIREMENTS/- Feature specificationsGHE_REPORTS/- Agent reports (FLAT, no subfolders)- GitHub labels, issues, branches
If repo_path is wrong, folders get created in the WRONG location.
The setup flow ensures repo_path is saved FIRST before any folder creation.
Core Principles
GHE follows these non-negotiable principles:
- No time, only order: Workflow is phase-gated (DEV->TEST->REVIEW), never time-gated
- Parallel agents: Multiple agents work simultaneously on different issues/branches
- SERENA integration: Memory bank sync is always enabled for context survival
- Auto worktrees: Always enabled - required for parallel agent isolation
Step 1: Detect Git Repositories
Find all git repositories in current directory and subdirectories:
# Find all .git directories (repos and submodules)
find . -name ".git" -type d 2>/dev/null | head -20
Parse the output to identify:
- Main repo (if
.gitexists in current directory) - Sub-projects (nested
.gitdirectories) - Submodules (
.gitfiles pointing to worktree)
For each found repo, get its remote URL:
git -C <repo-path> remote get-url origin 2>/dev/null
Step 2: Select Target Repository
If multiple repos found, ask user which one to configure:
{
"questions": [
{
"question": "Which repository should GHE track?",
"header": "Repository",
"multiSelect": false,
"options": [
{"label": "<repo-name-1>", "description": "<remote-url-1>"},
{"label": "<repo-name-2>", "description": "<remote-url-2>"}
]
}
]
}
If only one repo found, use it automatically and inform user.
Step 3: Check Existing Configuration
Check if .claude/ghe.local.md already exists in the selected repo:
- If exists, read current settings and show them
- Ask if user wants to modify or keep current settings
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.
- 5d ago First seen · 559 lines · 8 tokens per session scan B 0f00fb57664a
setup is a command published in the GitHub repository Emasoft/ghe-marketplace (4 stars, last pushed 9mo ago), licensed MIT. It adds 8 tokens to every session and 4,016 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.