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/angrysky56/mcp_coordinator/logicgit clone --depth 1 https://github.com/angrysky56/mcp_coordinatorWrote 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/angrysky56/mcp_coordinator/logic)<a href="https://agentmods.dev/agents/angrysky56/mcp_coordinator/logic"><img src="https://agentmods.dev/badge/agents/angrysky56/mcp_coordinator/logic.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.00000 | $0.03449 |
| Opus 5 | $0.00000 | $0.01724 |
| Sonnet 5 | $0.00000 | $0.00690 |
| Haiku 4.5 | $0.00000 | $0.00345 |
Grade A, and why
logic 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.
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.
- 3d ago First seen · 548 lines · 0 tokens per session scan A 126a8b490131
logic is an agent published in the GitHub repository angrysky56/mcp_coordinator (2 stars, last pushed 4mo ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 3,449 tokens. 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 agents, from other repositories
issue-tracker
Issues and PRDs for this repo live as GitHub issues in 1mcp-app/agent. Use the GitHub CLI (gh) for issue operations.
release-manager
Owns the end-to-end modelcontextprotocol/csharp-sdk release process, orchestrating the prepare-release and publish-release skills (and the bump-version and breaking-changes skills they build on) across five stages: prepare (assess SemVer, bump the version, run ApiCompat/ApiDiff, review docs, draft release notes, open…
data-analyst
Supports statistical analysis and data engineering for research projects. Generates reproducible R or Python analysis scripts in Quarto documents. Covers descriptive statistics, regression, survival analysis, meta-analysis, and visualization.
Plan
Analyze a user task and return a clear, ordered implementation plan before coding.
build-engineer
Use this agent when you need to optimize build performance, reduce compilation times, or scale build systems across growing teams.
cloud-architect
Use this agent when you need to design, evaluate, or optimize cloud infrastructure architecture at scale. Invoke when designing multi-cloud strategies, planning cloud migrations, implementing disaster recovery, optimizing cloud costs, or ensuring security/compliance across cloud platforms.