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 tanya-ok/engineering-os --skill plangit clone --depth 1 https://github.com/tanya-ok/engineering-osWrote 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/tanya-ok/engineering-os/plan)<a href="https://agentmods.dev/skills/tanya-ok/engineering-os/plan"><img src="https://agentmods.dev/badge/skills/tanya-ok/engineering-os/plan.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.00049 | $0.00339 |
| Opus 5 | $0.00024 | $0.00169 |
| Sonnet 5 | $0.00010 | $0.00068 |
| Haiku 4.5 | $0.00005 | $0.00034 |
Grade A, and why
plan 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 6d 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
plan
engineering-os tracks work in two places that answer different questions:
- beads (
bd) - the agent's task graph: what has been queued, what is blocked, and what is ready right now. - the vault (
_Index/Open Loops.md) - the human narrative: the loops you are trying to close, with owners and next steps.
This skill puts both in front of you at once so planning starts from the real state instead of a guess.
Run
./standards/skills/plan/plan.sh
It prints bd ready (or a setup hint if beads is not installed yet) followed by
the vault's open loops. Then the loop is:
- Pick a ready bead whose
domain:label matches an open loop you care about. - Claim it:
bd update <id> --claim, and announce the claim. - When done:
bd close <id> --reason "...", and update the open loop.
Conventions
See standards/canonical/work-tracking.md for the full beads conventions
(titles, domain: labels, priorities, the ready queue, and the announcement
protocol). The short version: agents write beads, humans write the vault (and
Linear later), and reading is unified across both.
What ships with it
1 file 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.
- 6d ago First seen · 37 lines · 49 tokens per session scan A 7065086662d7
plan is a skill published in the GitHub repository tanya-ok/engineering-os (2 stars, last pushed today), licensed MIT. It adds 49 tokens to every session and 339 once invoked, about $0.0002 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-31.
Other skills, from other repositories
forward-plan
Use when turning Brigade's native ready set, outcome rank, and ROADMAP.md into a dependency-filed plan artifact under .brigade/work/plans/ - propose GraphTrail-derived edges (blocks from def/use, conflicts-with from write overlap) marked derived and requiring confirmation. Degrade cleanly when GraphTrail is…
handoff-inbox-drain
Use when draining a Brigade handoff review inbox - triage drafts with allowlist-bound Brigade handoff commands, grounded edits that cite on-disk content, archive-only retention, and reinforce-in-place when ingest already matched a known fact (#724). Never delete, remove, or prune.
capture-task
Capture a new task — create a draft or pending Task record from a rough idea or detailed spec. Use when asked to "add a task", "log a bug", "create a task", or "add to backlog".
refine-backlog
Refine the backlog — screen drafts, remove duplicates, fill in missing details, classify, link, and move to pending.
implement-task
Pick up and work on a binder Task — investigate bugs, discuss open questions, design solutions, write tests, or implement code. Use when asked to "work on", "pick up", "implement", or "fix" a task.
prd-review-framework
Use when reviewing a PRD for goal clarity, scope, assumptions, and implementation readiness.