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 skills add BoSMark/BoS_OS_Start --skill agent-os-rungit clone --depth 1 https://github.com/BoSMark/BoS_OS_StartWrote 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/bosmark/bos_os_start/agent-os-run)<a href="https://agentmods.dev/skills/bosmark/bos_os_start/agent-os-run"><img src="https://agentmods.dev/badge/skills/bosmark/bos_os_start/agent-os-run.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.1 | $0.00219 | $0.10361 |
| Opus 5 | $0.00110 | $0.05181 |
| Sonnet 5 | $0.00044 | $0.02072 |
| Haiku 4.5 | $0.00022 | $0.01036 |
Grade A, and why
agent-os-run 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 7d 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 — 783 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent OS — Run
Version: 2.4.0
Status: ACTIVE
Author: Tim Barker, Mark Littlewood and Business of Software
The coordination layer for operating your BoS OS day to day.
Use this after you've run Bootstrap and Workshop. You have a strategy layer and refined agent roles. This is how you put them to work.
Source of frameworks, when they help: Business of Software's talk library at https://businessofsoftware.org/talks/ has 400+ talks, case studies, and frameworks from founders who've faced the same shaping, staffing, and delivery problems this pipeline works through. None of the three agents below should lead with a framework or use one to answer a question the human hasn't wrestled with yet — that undercuts the coaching model this whole layer is built on. But where a person is stuck, or names a problem that maps to a known pattern, a relevant talk or speaker is a legitimate tool to offer. Each agent's section below notes where that fits.
"Where am I?" — Session Opener (always do this first)
Read the CLAUDE.md header to confirm which company's BoS OS this is: # CLAUDE.md — BoS OS, built with [Name].
Before doing anything else, orient yourself to the current pipeline state. Read the following files if they exist:
01_STATE/session_summary.md— what was decided last session and what's open01_STATE/decisions.md— recent decisions (last 10–15 entries) for context- Any
04_MISSIONS/MISSION-NNN_*/MISSION-BRIEF.mdfiles — to understand what missions are active
Then determine which stage the user is in:
| What you find | Where they are | What to do next |
|---|---|---|
| No missions folder / no MISSION-BRIEF.md files | Pre-mission — haven't shaped anything yet | Offer to run the Mission Shaper |
| MISSION-BRIEF.md exists, no agent specs or todo.md | Brief is shaped, not yet staffed | Offer to run the Agent Planner |
| Agent specs and todo.md exist, todo has open items | Staffed and in delivery | Offer to run the Delivery Manager (operate mode stand-up) |
| todo.md depleted, done.md has entries | Mission may be complete | Offer retro or new mission |
What ships with it
11 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.
- agent-specs/agent-planner.md 11 KB
- agent-specs/delivery-manager.md 11 KB
- agent-specs/mission-shaper.md 27 KB
- mission-templates/blocked.md 821 B
- mission-templates/done.md 419 B
- mission-templates/in-progress.md 406 B
- mission-templates/mission-brief.md 4.0 KB
- mission-templates/todo.md 543 B
- README.md 4.5 KB
- references/agent_spec_examples.md 9.8 KB
- skills/agent-spec-builder/SKILL.md 8.2 KB
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.
- 7d ago First seen · 783 lines · 219 tokens per session scan A 29618baa8b1f
agent-os-run is a skill published in the GitHub repository BoSMark/BoS_OS_Start (20 stars, last pushed 25d ago), licensed MIT. It adds 219 tokens to every session and 10,361 once invoked, about $0.0011 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
forbotsake
Marketing skills for Claude Code. From zero marketing knowledge to published content. Run /forbotsake to set up all marketing skills, check installation health, or get routed to the right skill. Use when: "forbotsake", "install forbotsake", "marketing skills", "how should I market this", "help me sell this".
ti-founder
Founder profile template, creation questions, section definitions, and fit question guidance for TweakIdea evaluations.
ti-report
Jinja2 templates + CSS + data contract for TweakIdea evaluation reports.
forbotsake-cron
Autopilot mode for forbotsake. Installs a cron job that auto-posts reviewed content on schedule using Claude Code + Chrome. Content-calendar.md drives the timing. Subcommands: install, status, uninstall, pause, resume, doctor, run-now. Use when: "auto-post", "schedule posts", "autopilot", "cron", "forbotsake-cron"…
ti-hnparse
Python scripts for fetching a single HN post (hnparse.py) and searching HN posts via Algolia (hnsearch.py).
define-done
Generate a branded HTML accountability tracker for the next N days using the "Define Done" ritual. Takes 3 outcomes per day max (binary, shippable, no fluff), applies Walid's prompting principles for Claude Code, and outputs a self-contained HTML file ready to pin in a browser tab. Use when the user says "define…