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.
npx agentmods add skills/brsbl/ottonomous/specnpx skills add brsbl/ottonomous --skill specgit 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/skills/brsbl/ottonomous/spec)<a href="https://agentmods.dev/skills/brsbl/ottonomous/spec"><img src="https://agentmods.dev/badge/skills/brsbl/ottonomous/spec.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00088 | $0.01291 |
| Opus 5 | $0.00044 | $0.00646 |
| Sonnet 5 | $0.00018 | $0.00258 |
| Haiku 4.5 | $0.00009 | $0.00129 |
Grade A, and why
spec 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Input: $ARGUMENTS
Create or revise one product specification. The caller may provide the idea or draft inline, as a file reference, or through the surrounding conversation.
Resolve the invocation
Identify these inputs from the caller's request:
- Source: product idea, inline draft, or existing spec reference
- Working location: codebase or context to research
- Output destination: caller-selected file or external destination
- Format constraints: optional template, frontmatter, note system, or style
Ask only for information that blocks useful progress. An existing spec file can serve as its own destination. Otherwise, if the caller omits an output destination, ask for one before drafting. Never invent a spec registry, fixed directory, hidden state file, duplicate copy, or symlink. Use exactly the caller-selected destination and keep any supporting assets beside it or in a caller-selected asset location.
When revising an existing file, read it completely before editing. Preserve user-authored content, required metadata, comments, links, and layout unless a requested change requires otherwise.
1. Gather product and codebase context
For a new idea, ask whether reference products or examples matter. For an existing draft, treat its decided requirements as constraints rather than reopening them without evidence.
Inspect the supplied working location:
- Find the relevant files, interfaces, data models, and product surfaces.
- Trace the current behavior and name important architectural constraints.
- Search repository history when the proposal changes a public contract or a previously decided behavior.
- Separate observed facts from assumptions and open decisions.
If no working location is supplied, continue with product discovery and mark codebase-dependent claims as assumptions.
2. Research the problem
Use web research when current external evidence would improve the decision:
- Primary documentation for APIs, platforms, standards, or constraints
- Established product patterns and comparable implementations
- Known failure modes, security concerns, and accessibility expectations
What ships with it
2 files beside SKILL.md 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.
- 4d ago First seen · 170 lines · 88 tokens per session scan A 1f65c3c6c5e2
spec is a skill published in the GitHub repository brsbl/ottonomous (15 stars, last pushed 10d ago), licensed MIT. It adds 88 tokens to every session and 1,291 once invoked, about $0.0004 per session on Opus 5. 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 skills, from other repositories
investigate
Evidence-based investigation of issues, bugs, API calls, integrations, and other aspects of software development that need a deep dive to find the root cause and solutions. Use when you need to debug, troubleshoot, diagnose, or figure out why something is broken. Does not review code for quality or style — use…
code-overview-to-confluence
Produces a progressive-disclosure overview of unfamiliar code or a pull request's changes with code-overview and publishes the resulting overview to a user-specified Confluence location. Use when the user wants code or a PR explained, oriented, or made sense of AND the overview posted to a Confluence space or page.…
investigate-to-confluence
Runs an evidence-based investigation of a bug, failure, or unexpected behavior with investigate and publishes the resulting investigation report to a user-specified Confluence location. Use when the user wants something debugged, diagnosed, or root-caused AND the findings posted to a Confluence space or page. Requires…
markdown-to-confluence
Publishes a local Markdown file to a user-specified Confluence location, creating a new page or updating an existing one through the Atlassian MCP server. Use when the user wants to post, publish, push, or sync a Markdown file to a Confluence space or page. Requires a configured Atlassian MCP server. Does not write or…
edit-for-readability
Applies Han's shared Human-Readable Output Standard to a target you already have — a file on disk, text pasted into the prompt, or a draft already produced in the conversation — by dispatching the readability-editor to rewrite its prose so the main point comes first, headings are descriptive, each paragraph carries…
spike-guidance-inline
OI-3 spike harness — the INLINE (non-forked) readability-guidance variant. Surfaces the shared readability standard into the calling skill's own context. Use only when a spike consumer skill invokes it.