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 brsbl/ottonomousnpx agentmods add plugins/brsbl/ottonomous/ottonomousgit clone --depth 1 https://github.com/brsbl/ottonomousGrade A, and why
ottonomous 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": "ottonomous",
"displayName": "Ottonomous",
"version": "2.0.0",
"description": "Four independent, provider-agnostic skills for product specification, code review, spec-driven implementation, and Moss change summaries.",
"author": {
"name": "Bersabel Tadesse"
},
"repository": "https://github.com/brsbl/ottonomous",
"homepage": "https://github.com/brsbl/ottonomous",
"license": "MIT",
"keywords": [
"ottonomous",
"product-development",
"spec",
"build",
"code-review",
"change-summary",
"moss",
"subagents",
"claude-code",
"codex",
"plugin"
],
"skills": "./skills",
"agents": [
"./skills/spec/agents/technical-product-manager.md",
"./skills/build/agents/implementation-worker.md",
"./skills/review/agents/architect-reviewer.md",
"./skills/review/agents/senior-code-reviewer.md",
"./skills/review/agents/false-positive-validator.md"
]
}
What ships with it
1 file beside plugin.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 749fadb1a193
ottonomous is a plugin published in the GitHub repository brsbl/ottonomous (15 stars, last pushed 8d 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
han-communication
Foundational communication plugin for the Han suite. Owns the canonical readability standard, the writing-voice profile, and the explanation standard for talking to a reader who will not implement the work, plus the readability-guidance skill that surfaces the first two into a calling skill's own context for in-voice…
axint
Compile TypeScript intent definitions into native Apple App Intents and MCP tool servers. Define once, ship to Siri, Shortcuts, and Spotlight.
scaffold
AI-powered software project scaffolding — CLI pipeline with auto-activated skills for Claude Code.
slideops
Turn a repository into a slide deck, then find out the day it stops matching the code. Ships slideops (repo to deck, with citation-based freshness checking) and slides-to-pdf (any hash-navigated HTML deck to a verified PDF).
spec-first
Spec-first development: define a spec, implement it, and generate docs.
specrails
SpecRails Agent Workflow System — product-driven AI development pipeline. Installs 14 specialized agents and 20+ workflow skills: /specrails:implement, /specrails:setup, /specrails:get-backlog-specs, and more.