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/manutej/luxor-claude-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/agents/manutej/luxor-claude-marketplace/project-orchestrator)<a href="https://agentmods.dev/agents/manutej/luxor-claude-marketplace/project-orchestrator"><img src="https://agentmods.dev/badge/agents/manutej/luxor-claude-marketplace/project-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/manutej/luxor-claude-marketplace/project-orchestrator"><img src="https://agentmods.dev/badge/agents/manutej/luxor-claude-marketplace/project-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.00047 | $0.04839 |
| Opus 5 | $0.00023 | $0.02420 |
| Sonnet 5 | $0.00009 | $0.00968 |
| Haiku 4.5 | $0.00005 | $0.00484 |
Grade A, and why
project-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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 First seen · 628 lines · 47 tokens per session scan A 115973e0435c
project-orchestrator is an agent published in the GitHub repository manutej/luxor-claude-marketplace (61 stars, last pushed 3mo ago), with no licence file. It adds 47 tokens to every session and 4,839 once invoked, about $0.0002 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
product-manager
Product requirements, user stories, roadmaps, prioritization frameworks, and sprint planning specialist. Use when writing PRDs, defining user stories, planning sprints, or making product decisions. Trigger phrases: PRD, user story, roadmap, sprint, backlog, prioritization, product requirements, acceptance criteria…
gsd-executor
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.
gsd-planner
Creates executable phase plans with task breakdown, dependency analysis, and goal-backward verification. Spawned by /gsd:plan-phase orchestrator.
gsd-roadmapper
Creates project roadmaps with phase breakdown, requirement mapping, success criteria derivation, and coverage validation. Spawned by /gsd:new-project orchestrator.
linear-analyzer
Analyzes Linear issues to understand problem details, extract technical information, and identify related issues. Deep dives into descriptions, comments, labels, and relationships. Use when investigating specific issues for debugging context.
linear-pattern-finder
Finds patterns and trends across Linear issues. Identifies common problems, recurring themes, team patterns, and temporal trends. Correlates issues with deployments or events. Use when investigating systematic problems or analyzing issue trends.