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 skills add mattmre/EVOKORE-MCP-PUBLIC --skill fleet-statusgit clone --depth 1 https://github.com/mattmre/EVOKORE-MCP-PUBLICWrote 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/skills/mattmre/evokore-mcp-public/fleet-status)<a href="https://agentmods.dev/skills/mattmre/evokore-mcp-public/fleet-status"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/fleet-status/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/skills/mattmre/evokore-mcp-public/fleet-status"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/fleet-status.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.00025 | $0.00350 |
| Opus 5 | $0.00013 | $0.00175 |
| Sonnet 5 | $0.00005 | $0.00070 |
| Haiku 4.5 | $0.00003 | $0.00035 |
Grade A, and why
fleet-status 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.
What it actually says
/fleet-status — Fleet Status Dashboard
Reports the current status of all running agents, workers, and resource claims.
Usage
/fleet-status
What it checks
- Active claims:
claim_listtool (ClaimsManager) — shows all locked resources - Worker status:
worker_contexttool — shows running/completed workers - Trust scores:
session_trust_reporttool — shows per-agent trust tiers - Memory usage:
memory_listtool — shows active memory entries - Session analytics:
session_work_ratiotool — shows evidence/replay density
Output Format
Reports each dimension with a summary and any warnings:
=== Fleet Status ===
Claims: 2 active (none stale)
Workers: 1 running (test_run), 2 complete
Trust: 3 agents — 2 Trusted, 1 Standard
Memory: 47 entries (12 active kinds)
Work ratio: 0.21 (healthy)
Integration
- Uses 5 native MCP tools: claim_list, worker_context, session_trust_report, memory_list, session_work_ratio
- Pairs with AGT-013 (Loop Operator) for anomaly detection
- Results feed into /session-checkpoint for state snapshot
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 · 47 lines · 25 tokens per session scan A f7c4e86e7729
fleet-status is a skill published in the GitHub repository mattmre/EVOKORE-MCP-PUBLIC (3 stars, last pushed 3mo ago), licensed MIT. It adds 25 tokens to every session and 350 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-09-03.
Other skills, from other repositories
python-package-management
Guide for managing packages in the Agent Framework Python monorepo, including creating new connector packages, versioning, and the lazy-loading pattern. Use this when adding, modifying, or releasing packages.
python-code-quality
Code quality checks, linting, formatting, and type checking commands for the Agent Framework Python codebase. Use this when running checks, fixing lint errors, or troubleshooting CI failures.
verify-dotnet-samples
How to build, run and verify the .NET sample projects in the Agent Framework repository. Use this when a user wants to verify that the samples still function as expected.
regex-tester
Validate, test, and debug regular expressions by executing them against sample inputs. Use when asked to build, verify, or explain a regex pattern.
risk-scoring
Score how concentrated and risky a portfolio is on a 0-100 scale from its position weights. Use when the user asks how risky their portfolio is, whether it is too concentrated, or for a diversification check.
escalation-policy
When and how to escalate Contoso Outdoors customer-support tickets.