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.
git clone --depth 1 https://github.com/Jedeiah/agent-critterWrote 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/plugins/jedeiah/agent-critter/marketplace)<a href="https://agentmods.dev/plugins/jedeiah/agent-critter/marketplace"><img src="https://agentmods.dev/badge/plugins/jedeiah/agent-critter/marketplace/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/plugins/jedeiah/agent-critter/marketplace"><img src="https://agentmods.dev/badge/plugins/jedeiah/agent-critter/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
agent-critter marketplace 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 1mo 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": "agent-critter",
"description": "Agent Critter — Claude Code 桌面宠物插件，兼容 Petdex 2700+ 精灵",
"owner": {
"name": "chj"
},
"plugins": [
{
"name": "agent-critter",
"description": "一只桌宠小精灵，实时展示 Claude Code 工作状态。支持 Petdex 社区 2700+ 精灵。",
"source": {
"source": "url",
"url": "https://github.com/Jedeiah/agent-critter.git",
"sha": "8d3c02707ac29016deb1361e488b47ef1dac9f84"
},
"homepage": "https://github.com/Jedeiah/agent-critter"
}
]
}
The plugins it lists here
This marketplace lists 1 plugin kept in the same repository. Each has its own page, its own measurements and its own install command.
What ships with it
1 file beside marketplace.json 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.
- 1mo ago First seen · 20 lines scan A 4554dd84a8ae
agent-critter marketplace is a plugin published in the GitHub repository Jedeiah/agent-critter (3 stars, last pushed 4mo 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
odin-bigquery
ODIN workflows for BigQuery data work and cost-aware queries.
odin-code-advanced
Advanced ODIN workflows for complex code changes and technical audits.
odin-core
Core ODIN gates every session runs: intent, scope, verification, and hand-off checks.
odin-create-advanced
Advanced ODIN workflows for ambitious, multi-part creative work.
odin-formal
ODIN workflows for formal methods: model checking, SMT solving, deductive verification, and proof assistants.
odin-git
ODIN workflows for commits, branches, pull requests, review feedback, and issue tracking.