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 schemasgit 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/schemas)<a href="https://agentmods.dev/skills/mattmre/evokore-mcp-public/schemas"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/schemas/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/schemas"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/schemas.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.00019 | $0.00512 |
| Opus 5 | $0.00010 | $0.00256 |
| Sonnet 5 | $0.00004 | $0.00102 |
| Haiku 4.5 | $0.00002 | $0.00051 |
Grade A, and why
orchestration-schemas 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.
What it actually says
Orchestration Schemas
JSON Schema definitions for validating orchestration configuration files. These schemas provide IDE autocompletion, validation, and documentation for the orchestration framework's configuration formats.
Schemas
| Schema | Purpose |
|---|---|
| agent.schema.json | Define agent roles, capabilities, inputs/outputs, and constraints |
| workflow.schema.json | Define workflow steps, triggers, execution modes, and dependencies |
| orchestrator.schema.json | Configure the orchestration engine (incremental processing, execution, triggers, filters) |
Agent Schema
Defines the structure for agent definitions:
- Required fields:
name,version,role - Roles: orchestrator, director, worker, reviewer, researcher, validator
- Capabilities: file-read, file-write, code-execution, web-search, api-calls, orchestration, validation, research, refinement
- Constraints: max_tokens, timeout_seconds, max_retries, parallel_allowed
Workflow Schema
Defines the structure for workflow definitions:
- Required fields:
name,version,steps - Step actions: invoke-agent, run-command, validate, transform, conditional, parallel-group, wait
- Execution modes: sequential, parallel, dependency-aware
- Triggers: manual, on_change (glob patterns), schedule (cron), on_event
Orchestrator Schema
Defines configuration for the orchestration engine:
- Incremental processing: staged changes, unstaged changes, branch diff
- Execution settings: mode, parallel_limit, timeouts, fail_fast
- Triggers: full_refresh_patterns, category_triggers
- Filters: include/exclude glob patterns
- Dry run: simulate without side effects
Usage
Reference a schema in your JSON configuration:
{
"$schema": "./agent.schema.json",
"name": "my-agent",
"version": "1.0.0",
"role": "worker"
}
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 63 lines · 19 tokens per session scan A 45009a5ecd73
orchestration-schemas is a skill published in the GitHub repository mattmre/EVOKORE-MCP-PUBLIC (3 stars, last pushed 3mo ago), licensed MIT. It adds 19 tokens to every session and 512 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
design-qa-checklist
Build a QA checklist for verifying that a build matches the design. Use at implementation review. For the spec engineers build from, use handoff-spec.
testing
Use this skill when writing, reviewing, or improving tests in WrongStack. Triggers: user says "test", "unit test", "integration test", "e2e", "mock", "vitest", "coverage", "assert", "expect", "test strategy", "write tests".
autoresearch
Autonomously optimize any Claude Code skill by running it repeatedly, scoring outputs against binary evals, mutating the prompt, and keeping improvements. Based on Karpathy's autoresearch methodology. Use when: optimize this skill, improve this skill, run autoresearch on, make this skill better, self-improve skill…
hunt-race-condition
Hunting skill for race condition vulnerabilities. Built from 3 public bug bounty reports. Use when hunting race condition on any target.
browserstack
Run tests on BrowserStack. Use when user mentions "browserstack", "cross-browser", "cloud testing", "browser matrix", "test on safari", "test on firefox", or "browser compatibility".
generate
Generate Playwright tests. Use when user says "write tests", "generate tests", "add tests for", "test this component", "e2e test", "create test for", "test this page", or "test this feature".