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 reflygit 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/refly)<a href="https://agentmods.dev/skills/mattmre/evokore-mcp-public/refly"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/refly/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/refly"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/refly.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.00094 | $0.01831 |
| Opus 5 | $0.00047 | $0.00915 |
| Sonnet 5 | $0.00019 | $0.00366 |
| Haiku 4.5 | $0.00009 | $0.00183 |
Grade A, and why
refly 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 10d 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refly
Rules
- CLI only - Use
refly <command>, never call API directly. - Trust JSON - Only trust CLI JSON (
ok,payload,error,hint). - No fabricated IDs - Never invent workflow/run/node IDs.
- No tokens - Never print or request auth tokens.
- Stop on error - If
ok=false, stop and showhint.
Available Commands
| Command | ID Format | Description |
|---|---|---|
refly status |
- | Check authentication and connection status |
refly login |
- | Authenticate with Refly |
refly skill list |
- | List all available skills in the marketplace |
refly skill installations |
- | List your installed skills (get installationId here) |
refly skill run --id <installationId> --input '<json>' |
skpi-xxx | Run an installed skill, returns runId (we-xxx) |
refly workflow status <runId> --watch |
we-xxx | Watch workflow execution status |
refly workflow detail <runId> |
we-xxx | Get workflow run details |
refly workflow toolcalls <runId> --files --latest |
we-xxx | Get files from latest toolcall |
refly file download <fileId> -o <path> |
df-xxx | Download a file |
Tip: Get installationId (skpi-xxx) from refly skill installations.
Command Options
| Command | Option | Description |
|---|---|---|
workflow status |
--watch |
Poll until workflow completes |
workflow status |
--interval <ms> |
Polling interval in milliseconds (default: 5000) |
workflow toolcalls |
--files |
Return simplified output with only files and content |
workflow toolcalls |
--latest |
With --files, return only files from the most recent toolcall |
workflow toolcalls |
--raw |
Disable output sanitization (show full tool outputs) |
Recommended: Use --files --latest to get files from the final output without processing all toolcalls.
Skill Categories & Execution Patterns
Choose the execution pattern based on the skill's output type:
What ships with it
5 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.
- 10d ago First seen · 171 lines · 94 tokens per session scan A 412c86e09d64
refly is a skill published in the GitHub repository mattmre/EVOKORE-MCP-PUBLIC (3 stars, last pushed 3mo ago), licensed MIT. It adds 94 tokens to every session and 1,831 once invoked, about $0.0005 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-08-31.
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).
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).
diary-study-plan
Design a diary study — prompts, cadence, duration, participant criteria, and analysis frame. Use when behaviour unfolds over days or weeks. For a single-session study, use usability-test-plan.