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.
git 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/commands/mattmre/evokore-mcp-public/talent-scan)<a href="https://agentmods.dev/commands/mattmre/evokore-mcp-public/talent-scan"><img src="https://agentmods.dev/badge/commands/mattmre/evokore-mcp-public/talent-scan/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/commands/mattmre/evokore-mcp-public/talent-scan"><img src="https://agentmods.dev/badge/commands/mattmre/evokore-mcp-public/talent-scan.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.00016 | $0.00121 |
| Opus 5 | $0.00008 | $0.00060 |
| Sonnet 5 | $0.00003 | $0.00024 |
| Haiku 4.5 | $0.00002 | $0.00012 |
Grade A, and why
talent-scan 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 11d 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.
This is a copy
100% identical to talent-scan — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Use the recruiter subagent to perform a talent market scan for: $ARGUMENTS
Analyze and report on:
- Talent availability in target markets
- Competitive salary ranges
- Required skills and experience levels
- Estimated time to hire
- Recommended sourcing channels
- Top candidate profiles (if using GitHub)
Provide specific recommendations on:
- Senior vs. junior hiring mix
- Remote vs. in-office strategy
- Compensation packages
- Interview process optimizations
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.
- 11d ago First seen · 20 lines · 16 tokens per session scan A cd1dbf8b1457
talent-scan is a command published in the GitHub repository mattmre/EVOKORE-MCP-PUBLIC (3 stars, last pushed 3mo ago), licensed MIT. It adds 16 tokens to every session and 121 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to talent-scan, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
strategize
Develop a complete UX strategy for a product or feature area.
help
Display the following help text to the user.
eg-new-feature
Build a new feature using the elephant/goldfish workflow — design doc, goldfish design check, implement, review, validate.
aim-task
Create, view, edit, list, or check off tasks in the AIM workspace.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.