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 agentmods add skills/outlinedriven/odin-codex-plugin/templatenpx skills add OutlineDriven/odin-codex-plugin --skill templategit clone --depth 1 https://github.com/OutlineDriven/odin-codex-pluginWhat 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 | $0.00069 | $0.00897 |
| Opus 5 | $0.00034 | $0.00449 |
| Sonnet 5 | $0.00014 | $0.00179 |
| Haiku 4.5 | $0.00007 | $0.00090 |
Grade A, and why
{skill_name} 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- {skill_name} — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{skill_name}
{skill_name} is a personal taste skill. It encodes observed taste through 5 evidence-derived anchors, each with a load-bearing concept, canonical exemplar, and two-sided failure boundary.
Posture
{posture_statement}
Conviction with restraint. The anchors are the positive frame; the two-sided charter is the negative space. Side A blocks slop/default convergence. Side B blocks overkill/compensatory excess. Both sides fail by refusing to commit.
Modes [LOAD-BEARING]
Two modes share the auto-clarity exception.
Mode-selection
Auto-detect from invoking-context phrasing, with slash-arg override:
- "is this slop?", "overkill?", "taste-test", "audit this", "review for taste", "what's wrong with this" -> audit.
- "shape this before writing", "load taste", "anchor mode", "before I write" -> anchor.
- Anything else -> audit by default.
- Explicit override:
/{skill_name} audit,/{skill_name} anchor. Override always wins.
audit mode
Walk the 5 anchors against the artifact in hand. For each anchor: verdict (pass / warn / fail), Side A or Side B citation when violated, and concrete fix. Surface tensions when anchors imply conflicting fixes; do not auto-pick a hidden precedence. Close with top-3 ranked fixes.
anchor mode
Load the 5 anchors and two-sided charter as imperatives for subsequent responses. Persistence is best-effort: applies until the user signals "stop taste" or "normal mode" OR context is compacted, whichever comes first. Re-invoke anchor mode if drift is observed.
Two-sided charter
Side A — slop: {side_a_summary}
Side B — overkill: {side_b_summary}
See references/charter.md for the full charter.
Anchors
| Anchor | Influence | Concept |
|---|---|---|
| {anchor_1_name} | {anchor_1_influence} | {anchor_1_concept_short} |
| {anchor_2_name} | {anchor_2_influence} | {anchor_2_concept_short} |
| {anchor_3_name} | {anchor_3_influence} | {anchor_3_concept_short} |
| {anchor_4_name} | {anchor_4_influence} | {anchor_4_concept_short} |
| {anchor_5_name} | {anchor_5_influence} | {anchor_5_concept_short} |
What ships with it
2 files 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.
- 2d ago First seen · 94 lines · 69 tokens per session scan A 9516ce285c61
{skill_name} is a skill published in the GitHub repository OutlineDriven/odin-codex-plugin (15 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 69 tokens to every session and 897 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.
Other skills, from other repositories
devx-ux
Activate when designing or modifying CLI command surfaces, command help text, install/init/run flows, error wording, or first-run experience in the APM CLI -- even when the user does not say "UX" explicitly.
implement-ui-interaction
기존 프론트엔드에 키보드·포커스·터치·포인터·제스처가 정확한 widget 상호작용을 구현하고 검증한다. 사용자가 Dialog, Popover, Tooltip, Menu, Combobox, Carousel, drag·swipe·pinch 또는 floating positioning을 실제 코드로 만들어 달라고 할 때 사용한다. 요청·스트림·background job·batch의 중복 실행, 취소·재시도·부분 성공 같은 비동기 작업 수명주기가 주 결과면 implement-async-ui-state를, 시간 기반 모션 자체가 주 결과면…
compose-creative-ui
기존 프론트엔드의 정체성과 디자인 시스템을 보존하면서 shadcn/ui registry, Magic UI, Aceternity UI, React Bits, Radix, Base UI, React Aria, Ark UI 등 호환 가능한 컴포넌트·시각 효과 도구를 선별해 화면 구성 자체를 구현·검증한다. 사용자가 랜딩 페이지, hero, 배경, 카드, bento, 텍스트 효과나 밋밋한 화면의 시각적 조합 개선을 요청할 때 사용한다. 시간·공간 변화는 implement-ui-motion을, 키보드·포커스·제스처·상태 동작은 implement-ui-interaction을…
implement-ui-motion
기존 프론트엔드에서 시간·공간 변화의 표현 자체가 주된 결과물인 모션과 마이크로인터랙션을 설계하고 CSS, Web Animations API, View Transition API, Anime.js, Motion 또는 GSAP 중 가장 단순한 기술로 구현·검증한다. 사용자가 애니메이션 적용, 버튼·카드의 시각 피드백, 페이지·레이아웃 전환, 스크롤·타임라인·SVG 모션, 라이브러리 선택, reduced-motion 또는 모션 성능 수정을 요청할 때 사용한다. 키보드·포커스·터치·제스처 입력은 implement-ui-interaction을, 요청·작업의 비동기 상태…
uiux-advisor
근거 기반 한국어 UI/UX 가이드를 검색해 개념 설명, 대안 비교, 컴포넌트·제품 명세와 리서치·검증 계획을 작성한다. 접근성, 콘텐츠, 상호작용 상태, 윤리, 반응형, 디자인 시스템, QA와 성능을 다룰 때 사용한다. 스크린샷·URL·코드·사용자 흐름 감사는 uiux-auditor를 사용한다. 키보드·포커스·제스처 구현은 implement-ui-interaction, 요청·작업의 비동기 상태 구현은 implement-async-ui-state, 모션 구현은 implement-ui-motion, 차트 구현은 build-data-visualization…
uiux-auditor
스크린샷, URL, 프로토타입, 코드, 제품 화면과 다단계 사용자 흐름을 증거 기반으로 감사해 심각도, 근거 확실도, 사용자 영향, 수정 우선순위와 검증 방법을 제시한다. 사용자가 UI/UX 감사, 화면·흐름 리뷰, 휴리스틱 평가, 접근성·상태·콘텐츠·반응형·성능·윤리 점검이나 출시 전 품질 검토를 요청할 때 사용한다. 일반 개념 설명·명세는 uiux-advisor를 사용하며, widget 상호작용·비동기 작업 상태·모션·차트·화면 조합·디자인 시스템의 실제 구현이 목적이면 각각 implement-ui-interaction…