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.
/plugin marketplace add catcatcatstudio/cat-skillsnpx agentmods add plugins/catcatcatstudio/cat-skills/eatgit clone --depth 1 https://github.com/catcatcatstudio/cat-skillsGrade A, and why
eat 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 2d 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
{
"name": "eat",
"description": "Extract knowledge and frameworks from any URL — YouTube, articles, podcasts, X threads",
"version": "2.0.0",
"author": {
"name": "catcatcat",
"url": "https://catcatcat.ai"
},
"homepage": "https://github.com/catcatcatstudio/cat-skills",
"repository": "https://github.com/catcatcatstudio/cat-skills",
"license": "MIT",
"keywords": ["eat", "extract", "knowledge", "youtube", "research", "skills"]
}
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.
- 2d ago First seen · 14 lines scan A e5c632aacc4b
eat is a plugin published in the GitHub repository catcatcatstudio/cat-skills (3 stars, last pushed 5d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
bottle
Bootstrap a project with a small, file-based documentation system so Claude Code keeps context, lessons, and decisions across session restarts instead of starting cold every time.
mental-model
A Claude Code skill that builds a correct, source-grounded mental model of how code actually works — instead of a confident-sounding guess.
ab-harness
Counterfactual A/B + layered-ablation harness for Claude Code setup. Measures whether your /.claude/ stack (skills, lessons, axioms, memory) plus in-repo discipline (docs/runbooks, decisions, findings) actually helps on real tasks. Binary A/B (setup-ON vs setup-OFF) and layered ablation (strip one layer at a time, ran.
context-police
Measure, trim, and report the token cost of a runaway Claude Code skills/agents catalog (injected every turn + into every subagent) — verified per-project skillOverrides + global disable-model-invocation levers, an interactive HTML recap, and the durable root-cause fix (curate episodic lessons out of the always-on…
doc-freshness-reverse-lint
Detect stale normative guidance in project docs/ after the user adds a new "don't X / avoid Y" rule to /.claude/lessons.md, /.claude/axioms.md, or a per-project feedback.md entry. Event-driven PostToolUse hook + weekly cron audit. Lists file:line candidate stale claims — never auto-edits. Conservative guardrails: e.
memory-hygiene
Audit and clean up Claude Code's persistent memory system — MEMORY.md, memory topic files, lessons, axioms, phase templates, ADRs, and the project docs/ taxonomy.