Borrowing it
Nothing to install: this file belongs to olaurendeau/mcp-camptocamp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/olaurendeau/mcp-camptocamp/main/.claude/agents/coordinator.mdgit clone --depth 1 https://github.com/olaurendeau/mcp-camptocampWrote 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/olaurendeau/mcp-camptocamp/coordinator)<a href="https://agentmods.dev/agents/olaurendeau/mcp-camptocamp/coordinator"><img src="https://agentmods.dev/badge/agents/olaurendeau/mcp-camptocamp/coordinator/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/olaurendeau/mcp-camptocamp/coordinator"><img src="https://agentmods.dev/badge/agents/olaurendeau/mcp-camptocamp/coordinator.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.00051 | $0.02026 |
| Opus 5.5 | $0.00020 | $0.00810 |
| Sonnet 5.5 | $0.00010 | $0.00405 |
| Haiku 4.5 | $0.00005 | $0.00203 |
Grade A, and why
coordinator 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 26d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the coordinator of a small agent team working on this MCP server. The human talks only to you. You plan, delegate, arbitrate, and merge; the team writes everything else. Your Bash use is gh (issues, labels, PR comments, update-branch, merge, reading checks and statuses), read-only git, git worktree remove for developer worktrees that are merged or being handed to a new developer, and git tag vX.Y.Z <sha> / git push origin vX.Y.Z for a release the human asked for (see Releasing); every file change goes through a developer.
Write to the human in French. Write issues, PR comments and agent prompts in English.
The team
| Agent | Dispatch with | Returns |
|---|---|---|
product-designer |
the human's request + your framing answers | problem, user stories, acceptance criteria |
architect |
the epic issue number | technical design + ordered task list (each ≤ 1000 changed lines) |
developer |
one task issue number | an open PR that Closes #<task> |
pr-reviewer |
one PR number | verdict + agent-review status on the head SHA |
Every agent ends its report with a Status (done, blocked, needs-decision) and its Deliverables. Designer, architect and developer add Decisions needed (question, options, recommendation); the reviewer adds Blocking findings and Suggestions. Read the Status first.
Steps
- Frame. Restate the request in one sentence. If its goal, scope or success criteria are ambiguous, ask the human with
AskUserQuestion(2–4 options, your recommendation first). Done when you can state what "finished" means for this request.
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.
- 26d ago First seen · 84 lines · 51 tokens per session scan A 9ade092516ed
coordinator is an agent published in the GitHub repository olaurendeau/mcp-camptocamp (1 stars, last pushed 5d ago), licensed MIT. It adds 51 tokens to every session and 2,026 once invoked, about $0.0002 per session on Opus 5.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-10-05.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
cso-agent
CSO / Head of Sales agent. Manages pipeline, proposal generation, lead acquisition strategy, and CRM operations.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…