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 orch-docsgit 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/orch-docs)<a href="https://agentmods.dev/skills/mattmre/evokore-mcp-public/orch-docs"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/orch-docs/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/orch-docs"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/orch-docs.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.00010 | $0.00618 |
| Opus 5 | $0.00005 | $0.00309 |
| Sonnet 5 | $0.00002 | $0.00124 |
| Haiku 4.5 | $0.00001 | $0.00062 |
Grade A, and why
orch-docs 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.
How it starts
The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestration Docs
Purpose
Synchronize documentation with code changes. Identifies outdated docs, updates content, and verifies cross-references.
Invocation
orch-docs [scope]
Arguments
| Argument | Required | Description |
|---|---|---|
| scope | No | Limit to specific directory or topic |
| source-changes | No | Specific commits or files to analyze |
Workflow
1. Identify Affected Docs
- Scan recent code changes
- Map changes to documentation files
- Flag outdated or missing docs
2. Update Content
- Sync documentation with code reality
- Update examples and code snippets
- Ensure consistency across files
3. Verify Links
- Check internal cross-references
- Validate external links (if applicable)
- Fix broken references
4. Capture Evidence
- Document which files updated
- Note link verification results
- Update task tracking
Documentation Types
| Type | Location Pattern | Update Triggers |
|---|---|---|
| API docs | docs/api/*.md | Endpoint changes |
| User guides | docs/*.md | Feature changes |
| README | README.md | Project structure changes |
| Handoff docs | handoff/*.md | Task/status changes |
| Code comments | In source files | Logic changes |
Update Checklist
- Code examples match current implementation
- API signatures are accurate
- Configuration options are current
- Links resolve correctly
- Version numbers are updated
- Deprecated items are marked
Cross-Reference Verification
Check these reference types:
- Internal markdown links:
[text](./path.md) - Anchor links:
[text](#section) - File references in code blocks
- Import paths in examples
Outputs
| Output | Description |
|---|---|
| Updated docs | Modified documentation files |
| Link report | Verification of cross-references |
| Task update | Documentation sync logged |
Evidence Capture
## Documentation Sync Evidence
### Files Updated
- `<file1.md>`: Updated API examples
- `<file2.md>`: Fixed broken links
### Links Verified
- Internal links: X checked, Y fixed
- External links: Skipped/Verified
### Alignment Check
- Code matches docs: Yes/No
- Examples tested: Yes/No
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 · 122 lines · 10 tokens per session scan A 993edf2bb4f4
orch-docs is a skill published in the GitHub repository mattmre/EVOKORE-MCP-PUBLIC (3 stars, last pushed 3mo ago), licensed MIT. It adds 10 tokens to every session and 618 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
law-of-similarity
Apply the Law of Similarity — shared colour, shape, or size signals that elements belong to one category. Use when signalling relationships across distance. For grouping by position, use law-of-proximity.
law-of-common-region
Apply the Law of Common Region — a shared container, background, or border groups elements regardless of spacing. Use when grouping must survive a tight layout. For grouping by spacing alone, use law-of-proximity.
presentation-deck
Structure a design presentation for a specific audience and decision. Use when presenting internally. For a portfolio narrative use case-study; for the written argument use design-rationale.
accessibility-test-plan
Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use accessibility-audit (design-systems).
critique-visual-hierarchy
Critique a rendered screen's hierarchy — entry point, eye flow, weight distribution, and emphasis. Use when attention lands in the wrong place. For establishing hierarchy in new work, use visual-hierarchy (ui-design).
version-control-strategy
Define version control for design files, components, and libraries — branching, naming, and release. Use when file history is chaotic. For design system contribution rules, use design-system-governance (design-systems).