eos-decide

A tool for recording lasting engineering decisions, including the situation, chosen approach, reasons, alternatives, and tags. Engineering decisions are documented choices about how software should be designed or built.

In plain words
What is it for?
Use it to document and preserve architecture or implementation decisions for later work with coding agents and development tools.
Why use it?
It keeps important technical choices available for future coding sessions instead of leaving them only in chat history.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/engineering-os/engineering-os/eos-decide
Any agent
npx skills add engineering-os/engineering-os --skill eos-decide
Clone the repo
git clone --depth 1 https://github.com/engineering-os/engineering-os

Made for: Claude Code, Codex.

Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 214 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00024 $0.00214
Opus 5 $0.00012 $0.00107
Sonnet 5 $0.00005 $0.00043
Haiku 4.5 $0.00002 $0.00021

Measured 2d ago against content hash 167f8d19c8cc, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

eos-decide 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.

.agents/skills/eos-decide/SKILL.md · 29 lines

What it actually says

EOS Decide

Use this skill when the user wants to record, document, or preserve an engineering decision for future Codex, Cursor, Claude, or MCP sessions.

Workflow

  1. Extract the decision title, context, chosen option, rationale, alternatives, and tags from the user's message.
  2. If any required part is missing, ask concise follow-up questions.
  3. Call eos_decide.
  4. Confirm what was recorded and where future agents should recall it.

Tool Pattern

eos_decide {
  "title": "<decision title>",
  "context": "<why this decision is needed>",
  "decision": "<chosen option>",
  "rationale": "<why this option was chosen>",
  "alternatives": [{ "option": "<alternative>", "proscons": "<tradeoffs>" }],
  "tags": ["<area>", "<topic>"]
}
Changes

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.

  1. 2d ago First seen · 29 lines · 24 tokens per session scan A 167f8d19c8cc

Subscribe to this mod's changes

eos-decide is a skill published in the GitHub repository engineering-os/engineering-os (35 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 24 tokens to every session and 214 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

architecture-feature-first

Use when creating a feature, designing folder structure, adding repositories/services/view models, wiring dependency injection, or deciding which layer owns logic.

evanca/flutter-ai-rules · 31 tokens

generate-images-with-firebase-ai

Use when generating or editing images from Flutter/Dart with Firebase AI Logic and a Gemini image model (Nano Banana), making the first call work, choosing Gemini Developer API vs Vertex AI, hitting quota, billing or App Check failures, getting empty or image-only responses, sending a user photo as input, controlling…

evanca/flutter-ai-rules · 84 tokens

firebase-analytics

Use when logging analytics events, setting user properties, configuring default event parameters, building funnels, or adding screen-view tracking.

evanca/flutter-ai-rules · 28 tokens

firebase-remote-config

Use when implementing feature flags, running A/B tests, setting parameter defaults, fetching/activating config, or enabling real-time config updates.

evanca/flutter-ai-rules · 33 tokens

flutter-errors

Use when hitting layout errors (RenderFlex overflow, unbounded constraints, RenderBox not laid out), scroll errors, or setState-during-build errors.

evanca/flutter-ai-rules · 34 tokens

promptscript

PromptScript language expert for reading, writing, modifying, and troubleshooting .prs files. Use when working with PromptScript syntax, creating or editing .prs files, adding blocks like @identity, @standards, @restrictions, @shortcuts, @skills, or @agents, configuring promptscript.yaml, resolving compilation errors…

mrwogu/promptscript · 135 tokens