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 OdinMB/ops-workflownpx agentmods add plugins/odinmb/ops-workflow/marketplacegit clone --depth 1 https://github.com/OdinMB/ops-workflowGrade A, and why
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 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": "ops",
"owner": {
"name": "OdinMB",
"url": "https://github.com/OdinMB"
},
"metadata": {
"description": "Structured non-code project management for Claude Code"
},
"plugins": [
{
"name": "ops",
"source": "./",
"description": "Structured non-code project management: planning, execution, knowledge persistence, and autonomous work loops for research, strategy, and content projects. 9 skills, 5 agents, 7 commands.",
"author": {
"name": "OdinMB"
},
"homepage": "https://github.com/OdinMB/ops-workflow",
"repository": "https://github.com/OdinMB/ops-workflow",
"license": "MIT",
"keywords": [
"project-management",
"ops",
"research",
"strategy",
"content",
"autonomous",
"knowledge-management",
"workflow-automation"
]
}
]
}
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.
- 2d ago First seen · 34 lines scan A 21921b301e06
ops is a plugin published in the GitHub repository OdinMB/ops-workflow (7 stars, last pushed 15d 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
vp-plugins
Knowledge graph management and sprint workflow automation for Claude Code.
vp-beads
Sprint workflow automation: backlog grooming, retrospectives, upstream vendor tracking, cross-project synergy tracking, swarm wave orchestration, vendor sync, and bilateral sibling reconciliation for projects using beads and Basic Memory.
onsails-skills
Plugin marketplace listing 3 plugins: rust-dev, sprint, mimo-code.
visionclaw-agent
VisionClaw Agent — multi-tenant agentic AI platform exposing 243 production tools, 16 specialist personas, hybrid-search Skill-RAG, and a self-improving skill registry over MCP. One-click access to project management, Drive/email/calendar, web research, code execution, multi-channel messaging, schema-aware databases…
linear-claude-skill
Managing Linear issues, projects, and teams for issue tracking, status updates, querying projects, and managing team workflows.
iterative-development
An iterative implementation methodology that pairs with superpowers. Extracts requirements with proof obligations from large spec collateral, defines a walking skeleton that closes a real journey, then loops through audited sprints building a behavior evidence corpus until an auditor confirms the product matches the…