sticky-and-fixed-elements

sticky-and-fixed-elements is a skill for Claude Code, Codex from dembrandt/dembrandt-skills. It costs 66 tokens per session (1,312 once invoked), scanned A, original, MIT.

A guide to keeping selected interface elements visible while the page scrolls, using fixed or sticky positioning. Fixed elements stay attached to the viewport, while sticky elements stay in their section after reaching a scroll position.

In plain words
What is it for?
Use it for navigation headers, mobile bottom toolbars, floating action buttons, table headers, section headings, and in-page toolbars. It explains when a persistent element should apply to the whole screen or only one section.
Why use it?
It helps users reach important navigation or actions without scrolling back, while warning that too many persistent layers can reduce space and create clutter. It also helps choose the appropriate scrolling behaviour.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 54repo +2 2d ago A scan Socket: passSnyk: passSkillSpector: pass 66 tokens original MIT

Good fit Use it for navigation headers, mobile bottom toolbars, floating action buttons, table headers, section headings, and in-page toolbars. It explains when a persistent element should apply to the whole screen or only one section.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/dembrandt/dembrandt-skills/sticky-and-fixed-elements
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.

Any agent
npx skills add dembrandt/dembrandt-skills --skill sticky-and-fixed-elements
Clone the repo
git clone --depth 1 https://github.com/dembrandt/dembrandt-skills

Made for: Claude Code, Codex.

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 sticky-and-fixed-elements

README.md
[![agentmods](https://agentmods.dev/badge/skills/dembrandt/dembrandt-skills/sticky-and-fixed-elements/github.svg)](https://agentmods.dev/skills/dembrandt/dembrandt-skills/sticky-and-fixed-elements)
Your own site
<a href="https://agentmods.dev/skills/dembrandt/dembrandt-skills/sticky-and-fixed-elements"><img src="https://agentmods.dev/badge/skills/dembrandt/dembrandt-skills/sticky-and-fixed-elements/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.

agentmods 80×15 button for sticky-and-fixed-elements

Your own site · 80×15
<a href="https://agentmods.dev/skills/dembrandt/dembrandt-skills/sticky-and-fixed-elements"><img src="https://agentmods.dev/badge/skills/dembrandt/dembrandt-skills/sticky-and-fixed-elements.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 66 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,312 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Socket pass 19 Apr 2026
  • Snyk pass 19 Apr 2026
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.1 $0.00066 $0.01312
Opus 5 $0.00033 $0.00656
Sonnet 5 $0.00013 $0.00262
Haiku 4.5 $0.00007 $0.00131

Measured 12d ago against content hash 484c924371ee, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

sticky-and-fixed-elements 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 12d 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.

skills/sticky-and-fixed-elements/SKILL.md · 146 lines

How it starts

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

Sticky and Fixed Elements

position: fixed vs position: sticky

Property Behaviour Use for
position: fixed Removed from document flow. Always stays at the same viewport position regardless of scroll or parent. Global navigation header, bottom toolbar, floating action button
position: sticky Stays in document flow until it hits its scroll threshold, then locks in place. Returns to flow when parent scrolls past. Table column headers, section headings in a long list, in-page toolbars within a scroll container

Prefer sticky over fixed when the element belongs to a specific section or scroll context. Fixed elements sit above everything and affect the entire viewport — use them only for truly global UI.

Top — Navigation Header

The global navigation header is the most common fixed element. It should:

  • Remain visible at all times so the user can always navigate away
  • Be as thin as possible to maximise content area — 48–64px is a common range
  • Have a background and shadow so content scrolling beneath it does not bleed through
  • On scroll, a subtle shadow (--shadow-sm) signals that content is behind it
.site-header {
  position: fixed;
  top: 0;
  left: 0;
  right: 0;
  height: var(--header-height);
  background: var(--color-surface);
  box-shadow: var(--shadow-sm);
  z-index: var(--z-header);
}

Compensate for the fixed header with matching top padding on the page body:

body { padding-top: var(--header-height); }

Bottom — Toolbar on Mobile

On mobile, the bottom of the screen is the most reachable area with one thumb. A persistent bottom toolbar is the natural home for:

  • Primary navigation (bottom tab bar — iOS and Android convention)
  • Contextual actions for the current view (edit, share, delete)
  • A floating action button (FAB) for the single most important action

Bottom toolbars should:

  • Respect the safe area inset on devices with a home indicator: padding-bottom: env(safe-area-inset-bottom)
  • Be visually separated from content (background fill, top border, or shadow)
  • Contain 3–5 items maximum — more than 5 should move to a menu or a different pattern
  • Use icons with labels for navigation tabs, or icons alone for contextual toolbars (with tooltips)

Read the full file on GitHub · 146 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. 12d ago First seen · 146 lines · 66 tokens per session scan A 484c924371ee

Subscribe to this mod's changes

sticky-and-fixed-elements is a skill published in the GitHub repository dembrandt/dembrandt-skills (54 stars, last pushed 2d ago), licensed MIT. It adds 66 tokens to every session and 1,312 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

indian-gov-web-ui

A set of design and accessibility rules for Indian government websites, portals, and administrative panels, including required standards such as GIGW and WCAG.

Yashraj00700/indian-gov-ui-skills · 95 tokens

ux4g-design-system

Use when building or reviewing UI with UX4G — India's official government design system (ux4g.gov.in, cdn.ux4g.gov.in, ux4g-web-components). Covers the v3.0.18 token API, the 52 components, install paths for HTML/React/Angular/Flutter, and the interop hazards. Triggers include "UX4G", "ux4g-web-components"…

Yashraj00700/indian-gov-ui-skills · 147 tokens

extract-design-system

Extract design primitives from a public website and generate starter token files for your project.

arvindrk/extract-design-system · 20 tokens

vois-tokens

Rules and patterns for building UI with shadcn/ui, Tailwind v4 or StyleX, and Motion against a Vois design token set. Use when building components, pages, or any UI that should conform to the workspace design system. Covers spacing, typography, color tokens, component architecture, animation, accessibility, and modern…

ommakes/Skills · 77 tokens

absolute-ui

Build polished, intentional UIs with concrete CSS/Tailwind values — typography, color, layout, spacing, dark mode, accessibility, animations, components. Encodes specific, opinionated rules with exact values, not vague advice. Covers buttons, cards, forms, tables, navigation, dashboards, landing pages, onboarding, and…

maddhruv/absolute · 121 tokens

ng-blatui

Use the ng-blatui Angular UI library in an app — install, import components (bui-prefixed, signal-based, zoneless, SSR-safe), theme with Tailwind v4 + oklch tokens, localize dates/numbers/labels, and discover the full catalog via the registry, api.json, llms.txt or the ng-blatui-mcp MCP server. Invoke when building…

anousss007/ng-blatui · 108 tokens