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/brsbl/ottonomousWrote 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/brsbl/ottonomous/ottonomous)<a href="https://agentmods.dev/plugins/brsbl/ottonomous/ottonomous"><img src="https://agentmods.dev/badge/plugins/brsbl/ottonomous/ottonomous/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/brsbl/ottonomous/ottonomous"><img src="https://agentmods.dev/badge/plugins/brsbl/ottonomous/ottonomous.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade 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 1mo 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 it installs
The manifest is a name and a version. 2 skills, 3 agents travel with it, and installing the plugin installs all of them — 291 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 1mo ago First seen · 34 lines scan A 749fadb1a193
ottonomous is a plugin published in the GitHub repository brsbl/ottonomous (16 stars, last pushed yesterday), 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-atlassian
Atlassian-facing extensions to the Han suite. Adds markdown-to-confluence, which publishes a local Markdown file to a user-specified Confluence page; project-documentation-to-confluence, which runs the han-documentation project-documentation skill and then publishes the result there; investigate-to-confluence, which…
han-coding
Coding-facing skills for the Han suite: writing, reviewing, testing, investigating, and standardizing code. Home of the tdd skill, which drives a feature or behavior through a BDD-framed red-green-refactor loop with an enforced observed-failure gate, and the refactor skill, which restructures existing code without…
han-planning
Planning-facing skills for the Han suite: specifying, planning, sequencing, breaking down, and stress-testing work before implementation. Home of plan-a-feature (build a feature specification from scratch through a relentless, evidence-based interview that walks the design tree), plan-a-change (plan an…
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…
han-core
The shared foundation of the Han suite: the specialist agent roster the other plugins dispatch (adversarial reviewers, analysts, architects, investigators, and the plan synthesizer), the project-discovery skill with its project-scanner agent, and the canonical evidence and YAGNI rule files. The documentation skills…
han-documentation
Documentation skills for the Han suite: writing down what the team built and decided. Home of project-documentation (create and maintain documentation for features, systems, and components), architectural-decision-record (create, extract, or convert ADRs), and runbook (create or update a runbook for a single…