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 atman-33/workhubnpx agentmods add plugins/atman-33/workhub/agent-opsgit clone --depth 1 https://github.com/atman-33/workhubWrote 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/atman-33/workhub/agent-ops)<a href="https://agentmods.dev/plugins/atman-33/workhub/agent-ops"><img src="https://agentmods.dev/badge/plugins/atman-33/workhub/agent-ops.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
agent-ops 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 yesterday.
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-ops",
"version": "0.1.0",
"description": "Run agents in a terminal multiplexer: herdr and Zellij setup, handoff between agents, role-based teams, persistent sidekicks, and the WSL/VS Code launch doctor. Install at user scope to make it available across all projects.",
"author": {
"name": "atman-33",
"url": "https://github.com/atman-33"
}
}
What it installs
The manifest is a name and a version. 8 skills travel with it, and installing the plugin installs all of them — 397 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.
- yesterday First seen · 10 lines scan A 5e985a6fde8b
agent-ops is a plugin published in the GitHub repository atman-33/workhub (2 stars, last pushed today), 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-09-03.
Other plugins, from other repositories
obsidian-vfs
Resolve @obs: mentions, and /obs: Skills from your Obsidian vault into Claude.
obsidian-chronicle
Auto-records Claude Code sessions as structured Obsidian notes + Daily Note entries (via the SessionEnd/PreCompact hooks and /done), and ships the obsidian-vault agent — the unified handler for all Obsidian vault work (create, edit, search, organize notes, tasks, canvases, bases). Configure with…
obsidian-cli
Automate Obsidian vault operations via CLI: note migration, property management, Bases, templates, search, and bulk file operations.
dding-dong
Claude Code 알림 플러그인 - 작업 완료, 오류, 입력 필요 시 소리와 OS 알림으로 알려줍니다.
claude-bedrock
Second Brain automation for Obsidian vaults — entity management, ingestion, compression, and sync via Claude Code skills.
hush
Trims command output, logs, and Claude's play-by-play before they pile up in the session, so long, noisy work stays quiet and readable. Install and forget — nothing to configure. Short questions with nothing to run cost a little more.