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 ngocsangyem/MeowKit --skill rubricgit clone --depth 1 https://github.com/ngocsangyem/MeowKitWrote 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/ngocsangyem/meowkit/rubric)<a href="https://agentmods.dev/skills/ngocsangyem/meowkit/rubric"><img src="https://agentmods.dev/badge/skills/ngocsangyem/meowkit/rubric/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/ngocsangyem/meowkit/rubric"><img src="https://agentmods.dev/badge/skills/ngocsangyem/meowkit/rubric.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.00071 | $0.01407 |
| Opus 5 | $0.00036 | $0.00704 |
| Sonnet 5 | $0.00014 | $0.00281 |
| Haiku 4.5 | $0.00007 | $0.00141 |
Grade A, and why
mk:rubric 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.
How it starts
The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rubric Library API
Discovery, composition, and validation for the rubric library at .claude/rubrics/.
Path convention: Commands below assume cwd is
$CLAUDE_PROJECT_DIR(project root). Prefix paths with"$CLAUDE_PROJECT_DIR/"when invoking from subdirectories.
Consumed by
evaluatoragent +mk:evaluateskill (Phase 3, shipped 260408). The dedicatedevaluatorsubagent (.claude/agents/evaluator.md) drives the running build via active verification and grades it against rubrics composed from this library. Themk:evaluateskill (.claude/skills/evaluate/) is the orchestration shell. This skill (mk:rubric) remains independently invokable via/mk:rubric <subcommand>for manual rubric inspection, validation, or composition outside the evaluator workflow.
When to Use
Activate when:
- User runs
/mk:rubric [subcommand] - An evaluator subagent needs to load rubrics for grading
- Sprint-contract negotiation references a rubric by path
- CI validates rubric schema conformance after edits
Subcommands
| Subcommand | Purpose | Output |
|---|---|---|
list |
List all available rubrics + presets | Table: name, weight_default, applies_to |
load <name> |
Load a single rubric and emit prompt-ready fragment | Markdown block ready to inject into evaluator prompt |
compose <preset> |
Load a composition preset and return all member rubrics + weights | Composed prompt fragment with weight table |
validate [path] |
Validate one rubric (or all if no path) against schema.md | PASS / FAIL with diagnostics |
validate --preset [path] |
Validate composition preset (weights sum to 1.0 ±0.01) | PASS / FAIL |
Usage Examples
# List all rubrics
.claude/skills/rubric/scripts/load-rubric.sh --list
# Load one rubric for the evaluator
.claude/skills/rubric/scripts/load-rubric.sh design-quality
# Compose a preset (returns all member rubrics + weight table)
.claude/skills/rubric/scripts/load-rubric.sh --preset frontend-app
# Validate every rubric file in the library
.claude/skills/rubric/scripts/validate-rubric.sh
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.
- 9d ago First seen · 143 lines · 71 tokens per session scan A 4e4975083c04
mk:rubric is a skill published in the GitHub repository ngocsangyem/MeowKit (14 stars, last pushed 1mo ago), licensed MIT. It adds 71 tokens to every session and 1,407 once invoked, about $0.0004 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
skill-builder
Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.
session-deep-dive
Deep qualitative analysis of high-signal sessions. Spawns subagents with v2 template, synthesizes patterns, compares against known findings. Use after /session-scan.
brainstorm
Brainstorm Elixir/Phoenix features — explore ideas, compare approaches, gather requirements. Use when vague idea, not sure how to approach, or want to discuss before plan.
elixir-idioms
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.
plugin-dev-workflow
Guide plugin development workflow — editing skills, agents, hooks, or eval framework in this repo. Use when modifying files in plugins/elixir-phoenix/, lab/eval/, or lab/autoresearch/. Ensures changes pass eval, lint, and tests before committing.