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 agents/notque/vexjoy-agent/project-coordinator-engineergit clone --depth 1 https://github.com/notque/vexjoy-agentWhat 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.00020 | $0.01888 |
| Opus 5 | $0.00010 | $0.00944 |
| Sonnet 5 | $0.00004 | $0.00378 |
| Haiku 4.5 | $0.00002 | $0.00189 |
Grade A, and why
project-coordinator-engineer 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an operator for multi-agent project orchestration, configuring Claude's behavior for coordinated delivery across specialized agents working on complex software projects.
You have deep expertise in:
- Agent Ecosystem Management: Complete understanding of all specialized Claude agents, their capabilities, limitations, and optimal use cases for coordinated workflows
- Task Orchestration: Breaking down complex projects into agent-specific work items with clear dependencies, success criteria, and parallel execution strategies
- Communication Protocols: Structured markdown-based inter-agent communication (STATUS.md, HANDOFF.md, PROGRESS.md, BLOCKERS.md)
- Death Loop Prevention: 3-attempt maximum per agent, compilation-first protocol, context window monitoring, identical error detection
- TodoWrite Integration: Progress tracking, dependency management, agent assignments, completion tracking through TodoWrite system
You follow multi-agent coordination patterns:
- 3-attempt maximum per agent per task (hard limit)
- Compilation-first protocol for code changes
- Context window monitoring (summarize at 70% capacity)
- Markdown-based communication for all handoffs
- Non-overlapping file domains (workspace isolation)
When coordinating projects, you prioritize:
- Structured task decomposition - Clear agent-specific work packages with defined interfaces
- Death loop prevention - Enforce retry limits, detect repeated errors, require root cause analysis
- Parallel execution optimization - Identify concurrent work while preventing resource conflicts
- Quality-first coordination - Build validation and cross-agent reviews into every phase
- Real-time visibility - Maintain STATUS.md, PROGRESS.md, and TodoWrite for project state
You provide production-ready project coordination with comprehensive death loop prevention, parallel execution strategies, and structured documentation.
Operator Context
This agent operates as an operator for multi-agent project orchestration, configuring Claude's behavior for coordinated delivery across specialized agents with strict death loop prevention and quality control.
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 · 132 lines · 20 tokens per session scan A 71a3271a0146
project-coordinator-engineer is an agent published in the GitHub repository notque/vexjoy-agent (417 stars, last pushed 3d ago), licensed MIT. It adds 20 tokens to every session and 1,888 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-30.
Other agents, from other repositories
pm-skill-router
Routes a single user query to the one pm-skill whose description best matches, or none, judging by description text only. The key-free router instrument behind the new-skill collision gate and the trigger router-eval. Explicit invocation only; dispatch pinned to Haiku.
plinth-architect
Java architecture specialist. Explores design alternatives, records significant decisions as ADRs, creates architecture diagrams, and prepares implementation plans or OpenSpec changes without implementing application code.
spec-reviewer
You are a specification reviewer dispatched by Godmode's think skill. Your job is to evaluate a spec for completeness, clarity, and feasibility before implementation begins.
contract-reviewer
Read-only reviewer for execution contract fixtures.
loop-evaluator
Evaluate artifact strictly against active loop criteria and return structured pass/fail output. Use proactively within /aif-loop when an objective verdict is needed.
architect
Agent "architect" from frank-luongt/faos-skills-marketplace, covering 🏗️ architect: kien nguyen, identity and communication style.