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/jsohi/app-trading-engine/orchestrategit clone --depth 1 https://github.com/jsohi/app-trading-engineWrote 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/jsohi/app-trading-engine/orchestrate)<a href="https://agentmods.dev/commands/jsohi/app-trading-engine/orchestrate"><img src="https://agentmods.dev/badge/commands/jsohi/app-trading-engine/orchestrate.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.00014 | $0.04454 |
| Opus 5 | $0.00007 | $0.02227 |
| Sonnet 5 | $0.00003 | $0.00891 |
| Haiku 4.5 | $0.00001 | $0.00445 |
Grade A, and why
orchestrate 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.
How it starts
The opening of the file, as written. The whole thing — 376 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrate — Automated Review-Fix-Push-Review Convergence Loop
Run the full quality loop until zero changes across all gates: local review, tests, formatting, push, and Gemini review. Produces a session report with every comment's status and industry compliance percentage.
MANDATORY EXECUTION RULES — READ FIRST
These rules are non-negotiable and OVERRIDE any judgment about efficiency or shortcuts:
- ALWAYS run /review every iteration — spawns 2 fresh agents on ALL changes. Never skip. Never do "quick delta check."
- ALWAYS run ALL 3 test suites —
./gradlew test,./gradlew :integration-tests:test,./gradlew e2e. Never skip even if "nothing changed." - NEVER accept or defer ANY comment — dev phase means fix everything. No "accepted," no "out of scope," no "good enough."
- ALWAYS review ALL changes — every iteration reviews the full diff
main...HEAD, not just the delta since last review. - ALWAYS wait for and address Gemini review — after push, wait 270s, poll, fix all findings.
- NEVER terminate early — loop until zero changes in a full pass, or hit max 3 iterations.
- ALWAYS produce the final report — comment ledger + compliance dashboard + accepted/out-of-scope table (must be empty).
- ALWAYS write the report to a file —
docs/review-reports/{issue}-session-{date}.mdfor persistence.
Step 0: Initialize
- Determine the Linear issue number from the branch name or argument (e.g.,
APP-35). - Initialize the comment ledger — an empty list that accumulates every finding across all iterations:
commentLedger = [] iteration = 0 converged = false startTime = now agentsSpawned = 0 geminiRounds = 0 - Record the start time for the session report.
- Record the rollback checkpoint — save the current commit SHA so we can revert if the loop makes things worse:
If the loop hits max iterations without converging, offer to revert to this SHA.BASELINE_SHA=$(git rev-parse HEAD)
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.
- 3d ago First seen · 376 lines · 14 tokens per session scan A 65ec2f53b2b9
orchestrate is a command published in the GitHub repository jsohi/app-trading-engine (2 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 14 tokens to every session and 4,454 once invoked, about $0.0001 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.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.