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 repo-ingestorgit 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/repo-ingestor)<a href="https://agentmods.dev/skills/mattmre/evokore-mcp-public/repo-ingestor"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/repo-ingestor/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/repo-ingestor"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/repo-ingestor.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.00031 | $0.00350 |
| Opus 5 | $0.00015 | $0.00175 |
| Sonnet 5 | $0.00006 | $0.00070 |
| Haiku 4.5 | $0.00003 | $0.00035 |
Grade A, and why
repo-ingestor 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 9d 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.
What it actually says
Repo Ingestor
This skill orchestrates the ingestion of external repositories, frameworks, and benchmarks to iteratively evolve and improve our own workflows and feature sets.
Core Workflows
1. Adaptive Learning Cycles (General Ingestion)
When analyzing external tools (e.g., theonlyhennygod/zeroclaw, alibaba/zvec, etc.):
- Perform a fulsome analysis of the tool.
- Adapt all features we lack, while maintaining and integrating our own existing identified features.
- Ensure our core identity remains, but consume and absorb functional improvements.
- Research Scope: Features, libraries, best use cases, security issues, permanence, runtime security, iterative improvements, and adaptation ability.
- Analysis Report: Do a comprehensive analysis of their feature set and vision versus ours. Identify which features and functions are best and need to be adapted for our improvement.
2. Benchmarks and LLM Test Repos
When incorporating testing repos (e.g., Snowflake-Labs/agent-world-model):
- Iteratively improve or aim for improvement on future repo ingestions.
- Do not overfit just to pass the tests. Philosophically understand the conditional improvements that come from future analytical perspective improvements.
- Investigate: Loop and escape paradigms, confrontational analysis schemes, and benchmark improvements over time.
3. Deep Swarm Research
- Use multiple agents to analyze multiple new repos and research papers.
- Absorb knowledge and functionality to enhance our own ecosystem.
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.
- 9d ago First seen · 30 lines · 31 tokens per session scan A 21920c089f13
repo-ingestor is a skill published in the GitHub repository mattmre/EVOKORE-MCP-PUBLIC (3 stars, last pushed 3mo ago), licensed MIT. It adds 31 tokens to every session and 350 once invoked, about $0.0002 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.
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).
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.
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.
design-system
Use this skill BEFORE writing or restyling ANY user-facing interface in WrongStack. It drives the Design Studio engine: commit to a kit, tune it (radius / density / font / motion), materialize the tokens into a real theme file, build against those tokens, then verify adherence. Trigger it whenever the user asks to…