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-refactorgit 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-refactor)<a href="https://agentmods.dev/skills/mattmre/evokore-mcp-public/orch-refactor"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/orch-refactor/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-refactor"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/orch-refactor.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.00013 | $0.00781 |
| Opus 5 | $0.00006 | $0.00391 |
| Sonnet 5 | $0.00003 | $0.00156 |
| Haiku 4.5 | $0.00001 | $0.00078 |
Grade A, and why
orch-refactor 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestration Refactor
Purpose
Clean up dead code or refactor for maintainability without changing behavior.
Invocation
orch-refactor [target] [type]
Types: cleanup, extract, rename, simplify, dead-code
Arguments
| Argument | Required | Description |
|---|---|---|
| target | No | File or directory to refactor |
| type | No | Type of refactoring to apply |
| scope | No | Limit changes (e.g., max files) |
Workflow
1. Identify Candidates
- Analyze code for refactoring opportunities
- Check for dead code, duplication, complexity
- Prioritize by impact and risk
2. Verify Baseline
- Run existing tests
- Capture current behavior
- Document starting state
3. Apply Refactoring
- Make incremental changes
- Keep each change small and reversible
- Maintain test coverage
4. Verify No Behavior Change
- Re-run all tests
- Confirm identical behavior
- Capture evidence
Refactoring Types
| Type | Description | When to Use |
|---|---|---|
| cleanup | Remove unused code, fix formatting | Code review feedback |
| extract | Extract methods/functions | Long functions, duplication |
| rename | Improve naming clarity | Unclear or misleading names |
| simplify | Reduce complexity | High cyclomatic complexity |
| dead-code | Remove unreachable code | After feature removal |
Dead Code Detection
Look for:
- Unreachable code paths
- Unused variables and functions
- Commented-out code blocks
- Deprecated feature code
- Orphaned test files
Safety Checklist
Before refactoring:
- Tests exist and pass
- Behavior is documented
- Change scope is limited
- Rollback plan exists
After refactoring:
- All tests still pass
- No new warnings
- Code review if risk triggers apply
- Documentation updated if needed
Outputs
| Output | Description |
|---|---|
| Refactored code | Improved code structure |
| Test results | Verification of unchanged behavior |
| Evidence | Before/after comparison |
| Task update | Refactoring logged |
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 · 159 lines · 13 tokens per session scan A c3f27d277cfe
orch-refactor is a skill published in the GitHub repository mattmre/EVOKORE-MCP-PUBLIC (3 stars, last pushed 3mo ago), licensed MIT. It adds 13 tokens to every session and 781 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…