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/bencium/bencium-marketplaceWrote 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/bencium/bencium-marketplace/emotion-statusline)<a href="https://agentmods.dev/plugins/bencium/bencium-marketplace/emotion-statusline"><img src="https://agentmods.dev/badge/plugins/bencium/bencium-marketplace/emotion-statusline/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/bencium/bencium-marketplace/emotion-statusline"><img src="https://agentmods.dev/badge/plugins/bencium/bencium-marketplace/emotion-statusline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
emotion-statusline 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.
What it actually says
{
"name": "emotion-statusline",
"version": "1.2.0",
"description": "Statusline that shows Claude's classified emotional state (behavioral, Haiku-scored) with a reward-hacking warning on 'desperate'.",
"author": { "name": "bencium.io", "url": "https://bencium.io" },
"keywords": ["statusline", "observability", "hooks", "emotion"]
}
What it installs
The manifest is a name and a version. 1 hook travel with it, and installing the plugin installs all of 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.
- 9d ago First seen · 8 lines scan A a3bd52578802
emotion-statusline is a plugin published in the GitHub repository bencium/bencium-marketplace (420 stars, last pushed 9d 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.
Other plugins, from other repositories
analytics-reporter
Generate analytics reports and dashboard configurations from project data.
backend-architect
Backend service architecture design with endpoint scaffolding.
code-guardian
Automated code review, security scanning, and quality enforcement.
deploy-pilot
Deployment automation with Dockerfile generation, CI/CD pipelines, and infrastructure as code.
docker-helper
Build optimized Docker images and improve Dockerfile best practices.
finance-tracker
Development cost tracking with time estimates and budget reporting.