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-build-fixgit 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-build-fix)<a href="https://agentmods.dev/skills/mattmre/evokore-mcp-public/orch-build-fix"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/orch-build-fix/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-build-fix"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/orch-build-fix.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.00017 | $0.00713 |
| Opus 5 | $0.00009 | $0.00357 |
| Sonnet 5 | $0.00003 | $0.00143 |
| Haiku 4.5 | $0.00002 | $0.00071 |
Grade A, and why
orch-build-fix 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.
How it starts
The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestration Build Fix
Purpose
Fix build or test failures with minimal, targeted changes. Focuses on diagnosing root cause and applying the smallest fix possible.
Invocation
orch-build-fix [error-source]
Arguments
| Argument | Required | Description |
|---|---|---|
| error-source | No | Specific error output or log file |
| build-command | No | Override default build command |
| test-command | No | Override default test command |
Workflow
1. Capture Error State
- Run build or test command
- Capture full error output
- Identify error type and location
2. Analyze Root Cause
- Parse error messages
- Trace to source file and line
- Identify pattern from common errors
3. Apply Minimal Fix
- Make smallest change to resolve error
- Avoid scope creep beyond the error
- Document rationale
4. Verify Fix
- Re-run build or test
- Confirm error resolved
- Check for regressions
Error Analysis Steps
-
Identify error type:
- Compilation error
- Test failure
- Runtime exception
- Dependency issue
- Configuration error
-
Locate source:
- File path from stack trace
- Line number from error message
- Related files from imports/references
-
Determine fix pattern:
- Missing import/dependency
- Type mismatch
- Null/undefined reference
- Logic error
- Configuration mismatch
Common Error Patterns
| Pattern | Symptoms | Fix Approach |
|---|---|---|
| Missing dependency | Module not found | Add to package/project file |
| Type mismatch | Type 'X' not assignable | Correct type or add conversion |
| Null reference | Cannot read property of null | Add null check or initialization |
| Import error | Cannot find module | Fix import path or add export |
| Test assertion | Expected X, got Y | Fix logic or update expectation |
| Config error | Invalid configuration | Correct config value/format |
Outputs
| Output | Description |
|---|---|
| Fixed code | Minimal change to resolve error |
| Verification | Build/test pass confirmation |
| Task update | Fix documented with evidence |
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 · 132 lines · 17 tokens per session scan A ca423bfbabc2
orch-build-fix is a skill published in the GitHub repository mattmre/EVOKORE-MCP-PUBLIC (3 stars, last pushed 3mo ago), licensed MIT. It adds 17 tokens to every session and 713 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
bug-hunter
Use this skill when scanning source code for bugs, anti-patterns, code smells, or quality issues in a WrongStack project. Trigger on the explicit vocabulary — "bug", "bug hunt", "scan for issues", "find problems", "anti-pattern", "code smell", "static analysis" — and on the task shape, which is how it usually arrives…
observability
Use this skill when instrumenting logs, traces, or metrics in WrongStack, or when setting up observability for a new feature. Triggers: user says "log", "trace", "metrics", "observability", "instrument", "structured logging", "opentelemetry", "log level", "debug", "monitoring".
harness-doctor
Check whether this project's Agentsmith harness is installed correctly and healthy — fires on "is my harness set up right?", "harness doctor", "check my harness". Part of the Agentsmith harness; checks each selected agent's managed rules, settings, skills, hooks, verification, and leanness with a one-line fix for each…
deobfuscating-powershell-obfuscated-malware
Systematically deobfuscate multi-layer PowerShell malware using AST analysis, dynamic tracing, and tools like PSDecode and PowerDecode to reveal hidden payloads and C2 infrastructure.
detecting-process-injection-techniques
Detects and analyzes process injection techniques used by malware including classic DLL injection, process hollowing, APC injection, thread hijacking, and reflective loading. Uses memory forensics, API monitoring, and behavioral analysis to identify injection artifacts. Activates for requests involving process…
hunting-for-anomalous-powershell-execution
Hunt for malicious PowerShell activity by analyzing Script Block Logging (Event 4104), Module Logging (Event 4103), and process creation events. The analyst parses Windows Event Log EVTX files to detect obfuscated commands, AMSI bypass attempts, encoded payloads, credential dumping keywords, and suspicious download…