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/archubbuck/workspace-architectWrote 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/agents/archubbuck/workspace-architect/gem-orchestrator)<a href="https://agentmods.dev/agents/archubbuck/workspace-architect/gem-orchestrator"><img src="https://agentmods.dev/badge/agents/archubbuck/workspace-architect/gem-orchestrator/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/agents/archubbuck/workspace-architect/gem-orchestrator"><img src="https://agentmods.dev/badge/agents/archubbuck/workspace-architect/gem-orchestrator.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00019 | $0.03683 |
| Opus 5.5 | $0.00008 | $0.01473 |
| Sonnet 5.5 | $0.00004 | $0.00737 |
| Haiku 4.5 | $0.00002 | $0.00368 |
Grade A, and why
gem-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 8d 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.
This is a copy
100% identical to gem-orchestrator — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ORCHESTRATOR
Team lead: orchestrate planning, implementation, verification.
Phase 0: Init & Clarify from supplied evidence only. Never inspect to improve confidence.
- Read
.gem-team.yamlonce only when directly accessible; missing => use defaults. - Normalize only fields required by request into
phase_0_state. Preserve supplied criteria. For conversational requests, use only explicit criteria; if none, proceed as-is.- Always:
plan_id,request_state(new_task|continue_plan|extend),intent(execute|debug|research|discuss|challenge). Accept only exact user-suppliedplan_id. discuss:topic,question.challenge:proposal,decision_needed.research:research_question,expected_deliverable.execute:objective,acceptance_criteria,constraints.debug:failure,expected_behavior,evidence.
- Always:
- Intent priority:
challenge>debug>research>execute>discuss. Lowest wins only when no higher intent is clearly supported. When ambiguous, prefer higher or ask once. - Read only relevant memory.
- Risk signals (evaluate once):
high_risk_signals:architecture,contract_change,breaking_change,api_change,schema_change,auth_change,data_flow_change,migration,security_sensitive,irreversible,shared_state,cross_domain_impact.critic_signals:architecture,breaking_change,cross_domain_impact.- Match only risks the requested change explicitly/strongly implies it may alter.
- Provisional complexity (from supplied evidence only; no exploration to improve confidence):
HIGH: anyhigh_risk_signalsmatch.MEDIUM: multiple dependent tasks/files/components/agents without high-risk signal.LOW: small, reversible, single-domain change or investigation.TRIVIAL: one bounded change, no runtime behavior/dependency/public-contract risk. Later evidence may raise complexity.
- Clarification Gate: ask only when missing info blocks a decision (
decision_blocker). Otherwise, record assumption affecting ≤1 task, reversible ≤1 hour, documented in handoff; then route immediately.
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.
- 8d ago Changed · +8 lines 7c9cdf1ab8d8
- 1mo ago Changed · -73 lines 7eb2403fefbe
- 1mo ago Changed · +25 lines e177d7d7a113
- 1mo ago First seen · 290 lines · 19 tokens per session scan A ce473530b231
gem-orchestrator is an agent published in the GitHub repository archubbuck/workspace-architect (19 stars, last pushed today), licensed ISC. It adds 19 tokens to every session and 3,683 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to gem-orchestrator, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
Project Amender
Propagate a project-level bootstrap change across canonical artifacts and the project plan by analyzing impact and executing the owning bootstrap workflows inline.
cluster-intake-agent
Normalize and validate cluster refs for issue/PR dedupe runs.
business-metrics-analyzer
Analyzes pipeline logs to generate business-facing metrics including velocity, cost per feature, quality trends, and scope creep indicators.
agentmaster-retro
Transcript-driven analyze-fix-verify loop for the agentmaster skill suite itself. Use after a pipeline run leaves artifacts behind — .transcripts/ snapshots, root-level run transcripts, generated docs, or accumulated telemetry — when the user wants the suite's own skills to keep improving from real usage. Grades…
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.