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-component-shapegit 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-component-shape)<a href="https://agentmods.dev/skills/amadeusitgroup/otter/logic-component-shape"><img src="https://agentmods.dev/badge/skills/amadeusitgroup/otter/logic-component-shape/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-component-shape"><img src="https://agentmods.dev/badge/skills/amadeusitgroup/otter/logic-component-shape.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.00043 | $0.01984 |
| Opus 5.5 | $0.00017 | $0.00794 |
| Sonnet 5.5 | $0.00009 | $0.00397 |
| Haiku 4.5 | $0.00004 | $0.00198 |
Grade A, and why
logic-component-shape 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Decision tree — component shape
Returns: single component, or container + presenter, plus the componentStructure to generate and the componentType to declare.
Default to a single component. A split separates data and business-logic access from pure presentation, and the container/presenter documentation says a component interacting with external entities may be split — not that it must be.
Will something vary?
The split puts a seam between data access and presentation so one can vary without touching the other. It is worth its cost only when something on one side actually varies.
CRITERION A one data source, several UI flavours
dense table on desktop and stacked cards on mobile; an A/B variant; or a
presenter integrators swap or configure at runtime — through the CMS or
Otter's component replacement mechanism — which is just another flavour
supplied from outside, and needs the display half to be its own component
whose inputs and outputs are the contract
without the seam: the fetch is duplicated per variant, or the template
branches on display concerns
CRITERION B one UI flavour, several data sources
a passenger list rendered from a search result on one screen and from a
saved itinerary on another
without the seam: the presentation is copied, and the copies drift
IF A or B is true -> BRANCH A: container + presenter
ELSE -> BRANCH B: single component
Name what varies before splitting. If you cannot say which of data source, display, or integrator-supplied implementation will differ, there is nothing for the seam to absorb.
"The logic feels complex enough to separate" is not an additional criterion. Complexity alone is a human judgement call — see the split without variation stop-and-ask in logic-placement.
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 · 191 lines · 43 tokens per session scan A 269c98edb972
logic-component-shape is a skill published in the GitHub repository AmadeusITGroup/otter (59 stars, last pushed today), licensed BSD-3-Clause. It adds 43 tokens to every session and 1,984 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…