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/TevvvB/termagitchiWrote 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/tevvvb/termagitchi/plugin)<a href="https://agentmods.dev/plugins/tevvvb/termagitchi/plugin"><img src="https://agentmods.dev/badge/plugins/tevvvb/termagitchi/plugin/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/tevvvb/termagitchi/plugin"><img src="https://agentmods.dev/badge/plugins/tevvvb/termagitchi/plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
pets 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 2mo 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": "pets",
"version": "0.2.9",
"description": "A creature for every agent session, in a den for every git worktree. Its mood tracks how tidy that worktree is, so several agents at once stay tellable apart at a glance.",
"author": {
"name": "TevvvB",
"url": "https://github.com/TevvvB"
},
"homepage": "https://github.com/TevvvB/termagitchi",
"repository": "https://github.com/TevvvB/termagitchi",
"license": "MIT",
"keywords": [
"statusline",
"worktree",
"parallel-agents",
"collection",
"fun"
]
}
What it installs
The manifest is a name and a version. 2 skills travel with it, and installing the plugin installs all of them — 65 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 2mo ago First seen · 20 lines scan A dc376310502d
pets is a plugin published in the GitHub repository TevvvB/termagitchi (18 stars, last pushed 20d 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-30.
pets compared with plugins from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| petsTevvvB/termagitchi | Plugin | 18 | 20d ago | MIT | A | — | Claude Code |
| jkavivsinai/jenkins-cli | Plugin | 98 | today | MIT | A | — | Claude Code |
| b2c-cliSalesforceCommerceCloud/b2c-developer-tooling | Plugin | 58 | today | Apache-2.0 | A | — | Claude Code |
| sipcodeAnuj7411/sipcode | Plugin | 46 | 24d ago | MIT | A | — | Claude Code |
| rudderRudderCode/Rudder | Plugin | 24 | 28d ago | Apache-2.0 | A | — | Claude Code |
| tree-ring-memoryTerminallyLazy/Tree-Ring-Memory | Plugin | 22 | 1mo ago | MIT | A | — | Claude Code |
| humanizerblader/humanizer | Plugin | 67k | 13d ago | MIT | A | — | Claude Code |