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 policy-pack-v1git 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/policy-pack-v1)<a href="https://agentmods.dev/skills/mattmre/evokore-mcp-public/policy-pack-v1"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/policy-pack-v1/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/policy-pack-v1"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/policy-pack-v1.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.00021 | $0.00628 |
| Opus 5 | $0.00010 | $0.00314 |
| Sonnet 5 | $0.00004 | $0.00126 |
| Haiku 4.5 | $0.00002 | $0.00063 |
Grade A, and why
policy-pack-v1 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Policy Pack v1
A comprehensive, model-agnostic policy pack that defines how agents should operate in any repository. It provides governance for agent behavior, evidence capture requirements, risk assessment, and modular rules that can be selectively adopted per project.
Overview
Policy Pack v1 establishes baseline standards for:
- Agent behavior: Core principles and autonomy boundaries
- Evidence capture: Minimum evidence requirements for changes
- Risk assessment: Triggers that require review before completion
- Acceptance checks: Default checks per change type
- Promotion criteria: Rules for promoting assets to shared libraries
Documents
Core Policies
| Document | Purpose |
|---|---|
| AGENTS.md | Core principles and autonomy baseline for agents |
| ORCHESTRATION.md | Standard handoff protocol and AEP workflow |
| EVIDENCE.md | Minimum evidence requirements for changes |
| ACCEPTANCE_CHECKS.md | Default acceptance checks per change type |
| RISK_TRIGGERS.md | Changes that require review before completion |
| PROMOTION_GUIDE.md | Rules for promoting reusable assets |
Modular Rules
Rules are organized in the rules/ subdirectory for selective adoption:
| Rule | Domain |
|---|---|
| rules/security.md | Secrets, input validation, injection prevention |
| rules/testing.md | TDD workflow, coverage, verification evidence |
| rules/git-workflow.md | Commits, branches, PRs, reviews |
| rules/coding-style.md | File organization, immutability, documentation |
| rules/agents.md | Agent delegation and coordination |
| rules/patterns.md | API response formats, error handling, logging |
| rules/performance.md | Context management, scope creep prevention |
What ships with it
14 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.
- ACCEPTANCE_CHECKS.md 418 B
- AGENTS.md 1.5 KB
- EVIDENCE.md 385 B
- ORCHESTRATION.md 638 B
- PROMOTION_GUIDE.md 434 B
- RISK_TRIGGERS.md 1.2 KB
- rules/agents.md 2.8 KB
- rules/coding-style.md 5.2 KB
- rules/git-workflow.md 3.9 KB
- rules/patterns.md 3.9 KB
- rules/performance.md 3.8 KB
- rules/README.md 3.8 KB
- rules/security.md 4.2 KB
- rules/testing.md 3.8 KB
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 · 60 lines · 21 tokens per session scan A 811eb13538de
policy-pack-v1 is a skill published in the GitHub repository mattmre/EVOKORE-MCP-PUBLIC (3 stars, last pushed 3mo ago), licensed MIT. It adds 21 tokens to every session and 628 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
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.
critique-visual-hierarchy
Critique a rendered screen's hierarchy — entry point, eye flow, weight distribution, and emphasis. Use when attention lands in the wrong place. For establishing hierarchy in new work, use visual-hierarchy (ui-design).
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.
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).