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 AmadeusITGroup/otter --skill logic-placementgit clone --depth 1 https://github.com/AmadeusITGroup/otterWrote 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/amadeusitgroup/otter/logic-placement)<a href="https://agentmods.dev/skills/amadeusitgroup/otter/logic-placement"><img src="https://agentmods.dev/badge/skills/amadeusitgroup/otter/logic-placement/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/amadeusitgroup/otter/logic-placement"><img src="https://agentmods.dev/badge/skills/amadeusitgroup/otter/logic-placement.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00046 | $0.01604 |
| Opus 5.5 | $0.00018 | $0.00642 |
| Sonnet 5.5 | $0.00009 | $0.00321 |
| Haiku 4.5 | $0.00005 | $0.00160 |
Grade A, and why
logic-placement 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 1mo 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Logic placement — design mode
Decide where a piece of logic belongs before it is written. This skill holds the order of the decisions, the rules for halting, and the output format. The criteria for each decision live in a sub-skill: read it before answering, do not answer from memory.
To assess code that already exists, use logic-review.
Out of scope
Stop and redirect when the question is really about:
| Question | Handled by |
|---|---|
| A configuration flag, feature toggle, or CMS-editable value | otter-new-config |
| Behaviour that should be runtime-conditional rather than coded | otter-rules-engine |
| Which reactive primitive to express the logic with | rxjs-vs-signals |
| How to run the generator once the shape is decided | otter-schematics |
| Reimplementing localization, forms, or analytics | the corresponding Otter package, not a new service or store |
Otter machinery already owns state in those areas, so adding a service or store beside it creates a second source of truth.
Deciding which half of a split wires that machinery up is still in scope — the container owns the data and business-logic access, the presenter only displays, per logic-component-shape.
Decision order
| # | Decision | Read | Returns |
|---|---|---|---|
| 1 | Component shape | logic-component-shape |
single component, or container + presenter |
| 2 | Logic layer | logic-state-layer |
component class, service, or store |
| 3 | Store implementation | logic-store-type |
one of the four ng g store* variants |
The store implementation decision runs only if the logic layer decision returned "store". Never start there: most state that feels store-shaped is service-shaped, and most components that feel split-shaped are not.
When to settle each decision
| Decision | Settle it | Cost of changing later |
|---|---|---|
| Component shape | Before ng g component |
Low — rerun the schematic, or add the display half later with --componentStructure=presenter |
| Logic layer | Before scaffolding | Low — extract or inline before anything consumes it |
| Store implementation | Before ng g store* |
High — reshapes state, selectors, and every consumer |
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.
- 1mo ago First seen · 160 lines · 46 tokens per session scan A 4c7dd1f23705
logic-placement is a skill published in the GitHub repository AmadeusITGroup/otter (59 stars, last pushed today), licensed BSD-3-Clause. It adds 46 tokens to every session and 1,604 once invoked, about $0.0002 per session on Opus 5.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
agent-upkeep
Perform one small, scoped maintenance improvement to the Elements monorepo and open a single reviewable pull request. Use this skill for scheduled or unattended upkeep runs that improve unit test coverage for one file, fix one behavioral bug in one module, or move one off ESLint rule toward enforcement to reduce…
agent-dependencies
Perform one conservative dependency or toolchain upgrade in the Elements monorepo and open a validated pull request. Use for nightly or unattended dependency maintenance, outdated package checks, first-party actions/ GitHub Actions updates, and pinned mise tool updates. Use the github-dependabot skill instead when the…
agent-debug-ci
Investigate failed scheduled or nightly GitHub Actions runs on the default branch, determine whether the failure is reproducible and repository-owned, implement the smallest evidence-backed fix, validate it, and open a pull request. Use when a failed nightly CI event starts an agent, or when the standard CI or…
audit-ci
Run and analyze Elements cold CI performance profiles and propose evidence-backed build, test, lint, and dependency-graph improvements. Use whenever asked to profile or benchmark pnpm run ci, rerun ci:profile, create a CI performance audit, compare CI timings, find bottlenecks or the completion path, investigate a CI…
authoring-projects
Author a new standalone NVIDIA Elements workspace project containing a Lit component, including package files, the five test types, Wireit tasks, workspace and CI registration, metadata generation, documentation-site integration, dependency-lint configuration, and generated lock/notice files. Use when creating or…
audit-simplification
Audit an Elements project, directory, or component for mechanisms that may not need to exist, including redundant state, attribute reflection, forwarding indirection, lifecycle plumbing, per-instance allocations, and custom synchronization that duplicates browser or Lit behavior. Use when the user says code feels…