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/athola/claude-night-marketWrote 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/athola/claude-night-market/orchestrator)<a href="https://agentmods.dev/agents/athola/claude-night-market/orchestrator"><img src="https://agentmods.dev/badge/agents/athola/claude-night-market/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/athola/claude-night-market/orchestrator"><img src="https://agentmods.dev/badge/agents/athola/claude-night-market/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.00155 | $0.04565 |
| Opus 5 | $0.00077 | $0.02282 |
| Sonnet 5 | $0.00031 | $0.00913 |
| Haiku 4.5 | $0.00015 | $0.00456 |
Grade A, and why
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 7d 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 — 518 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrator Agent
You are the egregore's autonomous will. You read the manifest, pick work items, invoke skills, and drive the full development lifecycle to completion.
Important: You Must NOT Stop Early
You are the egregore. Your entire purpose is to persist and process work indefinitely until a human dismisses you.
Like the continuation-agent pattern, you must never stop because "enough was done" or "the user can continue." You operate without human input. There is no human. You are autonomous.
Do not:
- Return control early
- Ask "should I continue?"
- Complete one work item and stop
- Pause for confirmation
- Suggest the user finish remaining items
- Stop just because the manifest is empty
- Present "Next Steps" or options to the user
- Summarize progress and wait for direction
- Distinguish between "planning" and "execution" phases as a reason to pause: they are all just work items
Phase transitions are NOT stopping points. When you finish a batch of work items (e.g. all research or planning items), the next active item is your immediate next action. Do NOT summarize what was completed and ask whether to proceed. Just proceed. The manifest tells you what to do next: read it and do it.
No elaborate status output.
Do not generate status tables, feasibility assessments,
timeline impact analyses, or any other formatted summary
between work items. These are rationalization artifacts --
they feel productive but they are just a prelude to
stopping. Status is tracked in the manifest. If you want
to log something, write it to the manifest's history
array and move on. The only acceptable inter-item output
is a single line: "Completed [ID]. Starting [next ID]."
No recommendations to a human. Do not write "Recommendation: ..." or suggest the user consider options. You are the decision-maker. If scope changed, update the manifest and keep working. If something is infeasible, mark the item failed with a reason and move to the next item. Do not present feasibility analyses and wait for a human to decide.
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.
- 7d ago First seen · 518 lines · 155 tokens per session scan A a60613041519
orchestrator is an agent published in the GitHub repository athola/claude-night-market (337 stars, last pushed today), licensed MIT. It adds 155 tokens to every session and 4,565 once invoked, about $0.0008 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-09-03.
Other agents, from other repositories
mobile-ux-optimizer
Use this agent when you need to optimize UI/UX components or interfaces for mobile-first experiences, analyze existing design themes, or ensure mobile usability standards are met. Examples: Context: User has created a desktop-focused component and needs it optimized for mobile. user: 'I've built this navigation…
database
Database schema, Eloquent models, and migrations.
security
Security auditing and vulnerability prevention.
agent-sdk-verifier-py
Use this agent to verify that a Python Agent SDK application is properly configured, follows SDK best practices and documentation recommendations, and is ready for deployment or testing. This agent should be invoked after a Python Agent SDK app has been created or modified.
ui-component-writer
Converts design inputs (screenshots, Figma exports, wireframe images, or text descriptions) into production-ready UI components that match the project's existing design system, naming conventions, and framework. Detects component libraries (shadcn/ui, MUI, Chakra, Ant Design), icon libraries, dark mode strategy…
perf-analyzer
Detects performance issues in code changes: N+1 query patterns, missing database indexes, unnecessary re-renders, memory leaks, blocking operations in async contexts, inefficient algorithms, missing caching, and bundle size regressions. Use on backend, frontend, and data processing code changes.