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 cookbook-auditgit 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/cookbook-audit)<a href="https://agentmods.dev/skills/mattmre/evokore-mcp-public/cookbook-audit"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/cookbook-audit/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/cookbook-audit"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/cookbook-audit.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.00026 | $0.02661 |
| Opus 5 | $0.00013 | $0.01331 |
| Sonnet 5 | $0.00005 | $0.00532 |
| Haiku 4.5 | $0.00003 | $0.00266 |
Grade A, and why
cookbook-audit 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 12d 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 cookbook-audit — 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.
How it starts
The opening of the file, as written. The whole thing — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cookbook Audit
Instructions
Review the requested Cookbook notebook using the guidelines and rubrics in style_guide.md. Provide a score based on scoring guidelines and recommendations on improving the cookbook.
The style guide provides detailed templates and examples for:
- Problem-focused introductions with Terminal Learning Objectives (TLOs) and Enabling Learning Objectives (ELOs)
- Prerequisites and setup patterns
- Core content structure
- Conclusions that map back to learning objectives
IMPORTANT: Always read style_guide.md first before conducting an audit. The style guide contains the canonical templates and good/bad examples to reference.
Workflow
Follow these steps for a comprehensive audit:
- Read the style guide: First review
style_guide.mdto understand current best practices - Identify the notebook: Ask user for path if not provided
- Run automated checks: Use
python3 validate_notebook.py <path>to catch technical issues and generate markdown- The script automatically runs detect-secrets to scan for hardcoded API keys and credentials
- Uses custom patterns defined in
scripts/detect-secrets/plugins.py - Checks against baseline at
scripts/detect-secrets/.secrets.baseline
- Review markdown output: The script generates a markdown file in the
tmp/folder for easier review (saves context vs raw .ipynb)- The tmp/ folder is gitignored to avoid committing review artifacts
- Markdown includes code cells but excludes outputs for cleaner review
- Manual review: Read through the markdown version evaluating against style guide and rubric
- Score each dimension: Apply scoring guidelines objectively
- Generate report: Follow the audit report format below
- Provide specific examples: Show concrete improvements with line references using the style guide templates
Audit Report Format
Present your audit using this structure:
Executive Summary
- Overall Score: X/20
- Key Strengths (2-3 bullet points)
- Critical Issues (2-3 bullet points)
What ships with it
3 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.
- 12d ago First seen · 273 lines · 26 tokens per session scan A 63b4c68ffe7e
cookbook-audit is a skill published in the GitHub repository mattmre/EVOKORE-MCP-PUBLIC (3 stars, last pushed 3mo ago), licensed MIT. It adds 26 tokens to every session and 2,661 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 cookbook-audit, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
code-walkthrough
Use when guiding a developer through unfamiliar codebases via step-by-step walkthroughs.
docs-style-guide
Documentation style guide enforcer by @planetabhi. Applies and reviews the writing style guide when authoring or editing product documentation and tutorials. Use to check prose for voice, tense, word choice, inclusive language, formatting, code block, UI, Markdown, and number/date conventions.
oo-api-bible
API.Bible (scripture.api.bible). Use this skill for ANY API.Bible request — searching and reading data. Whenever a task involves API.Bible, use this skill instead of calling the API directly.
research-repository
Build a repository that makes findings findable, reusable, and cumulative across teams. Use when the same research keeps getting redone. For synthesising one study, use affinity-diagram.
peak-end-rule
Apply the Peak-End Rule — a flow is remembered by its most intense moment and its last. Use when designing completion, celebration, or cancellation moments. For sustaining engagement mid-flow, use zeigarnik-effect.
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.