logic-store-type

logic-store-type is a skill for Claude Code, Codex from AmadeusITGroup/otter. It costs 54 tokens per session (1,215 once invoked), scanned A, original, BSD-3-Clause.

A decision guide for choosing an NgRx store, a shared application-data container, based on whether the data is one value or a keyed collection and whether it comes from local code or a remote call.

In plain words
What is it for?
Use it to select one of four store designs: simple or entity, combined with sync or async. Entity stores fit individually addressable records; simple stores fit data handled as one value.
Why use it?
It prevents choosing a more complex store than the data requires. The guide assumes that using a store has already been justified.

Skill for Claude CodeCodex

Part of the otter plugin — 11 skills, 3 agents, 3 MCP servers shipped together

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/amadeusitgroup/otter/logic-store-type
Any agent
npx skills add AmadeusITGroup/otter --skill logic-store-type
Clone the repo
git clone --depth 1 https://github.com/AmadeusITGroup/otter

Made for: Claude Code, Codex.

Or install otter, the plugin that ships this one along with the rest of its 11 skills, 3 agents, 3 MCP servers.

Wrote 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.

agentmods badge for logic-store-type

README.md
[![agentmods](https://agentmods.dev/badge/skills/amadeusitgroup/otter/logic-store-type.svg)](https://agentmods.dev/skills/amadeusitgroup/otter/logic-store-type)
Your own site
<a href="https://agentmods.dev/skills/amadeusitgroup/otter/logic-store-type"><img src="https://agentmods.dev/badge/skills/amadeusitgroup/otter/logic-store-type.svg" alt="Measured on agentmods" height="20"></a>
Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,215 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.00054 $0.01215
Opus 5 $0.00027 $0.00607
Sonnet 5 $0.00011 $0.00243
Haiku 4.5 $0.00005 $0.00121

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

Security

Grade A, and why

logic-store-type 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 5d 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.

tools/llm/plugins/otter/skills/logic-store-type/SKILL.md · 104 lines

How it starts

The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Decision tree — store implementation

Returns: one of store-entity-async, store-entity-sync, store-simple-async, store-simple-sync.

Precondition: a store is already justified by the application-scoped step of logic-state-layer. If it is not, stop and go back — a store chosen here for state that only needs sharing is the most expensive mistake in this area.

Answer two questions — what shape is the state, and what fills it — and read the variant off this table:

Sync: filled by local code Async: filled by a remote call
Simple: holds one value store-simple-sync store-simple-async
Entity: holds a keyed collection store-entity-sync store-entity-async

"Collection" means records that are individually addressable: each carries an id and can be updated, removed, or marked pending on its own. An array that is always read and written as a whole counts as one value, so it is simple, not entity.

Collection shape — entity or simple

ASK  are the items individually addressable and independently updatable?

YES -> ENTITY
       a list of bookings, passengers, or search results, where one item can be
       updated, removed, or marked pending on its own
       state extends EntityState<Model> from @ngrx/entity: an adapter, normalized
       ids/entities, generated selectAll/selectEntities/selectIds/selectTotal
       requires an id property (modelIdPropName) — the practical test is that each
       item already carries something that identifies it

NO  -> SIMPLE
       one value, held as a single `model`: the current user session, active search
       criteria, a configuration blob
       also an array always read and written as one unit, such as destination codes.
       There is no meaningful id to key on, and EntityState would force you to invent
       one — holding such an array in a simple store is correct, not a workaround

The distinction matters most for async stores, where entity gives each record its own pending and failure status. A list of strings has nothing to track per item, so that machinery buys nothing.

Read the full file on GitHub · 104 lines

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. 5d ago First seen · 104 lines · 54 tokens per session scan A b8ff37bab287

Subscribe to this mod's changes

logic-store-type is a skill published in the GitHub repository AmadeusITGroup/otter (57 stars, last pushed today), licensed BSD-3-Clause. It adds 54 tokens to every session and 1,215 once invoked, about $0.0003 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

integrated-browser

Use this when working on the VS Code integrated browser ("browserView") to understand its architecture and mental model. Covers the embedded Chromium browser, its editor tab, navigation, overlay/layout, sessions, and agent browser tools under src/vs/platform/browserView and src/vs/workbench/contrib/browserView.

microsoft/vscode · 68 tokens

policy-and-managed-settings

Use whenever adding, modifying, or reviewing any Copilot, agent, LLM, AI, tool, permission, sandbox, MCP, model, telemetry, feature-gate, setting, configuration, or enterprise control—especially anything an organization or administrator may need to manage. Start here to decide whether it belongs in runtime managed…

microsoft/vscode · 112 tokens

adev-writing-guide

Comprehensive writing guide for Angular documentation (adev). Covers Google Technical Writing standards, Angular-specific markdown extensions, code blocks, and components. You MUST use this skill any time you plan to create, edit, or review documentation files in adev/ or adev/src/content.

angular/angular · 60 tokens

reference-signal-forms

Explains the mental model and architecture of the code under packages/forms/signals. You MUST use this skill any time you plan to work with code in packages/forms/signals.

angular/angular · 43 tokens

angular-developer

Generates Angular code and provides architectural guidance. Trigger when creating projects, components, services, or HTTP communication, or for best practices on reactivity (signals, linkedSignal, resource, httpResource), forms, dependency injection, routing, SSR, accessibility (ARIA), animations, styling (component…

angular/angular · 77 tokens

reference-compiler-cli

Explains the mental model and architecture of the code under packages/compiler-cli. You MUST use this skill any time you plan to work with code in packages/compiler-cli.

angular/angular · 40 tokens