new-section

A command that creates a reusable website section component in Astro, following the project's documented patterns.

In plain words
What is it for?
Use it to create sections such as team grids or pricing tables, with optional titles, subtitles, and layout variants.
Why use it?
It avoids starting each section from scratch and helps keep section structure and styling consistent.

Command for Claude Code

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 commands/holger1411/astrodeck/new-section
Clone the repo
git clone --depth 1 https://github.com/holger1411/astrodeck

Made for: Claude Code.

Per session 6 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 571 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.00006 $0.00571
Opus 5 $0.00003 $0.00285
Sonnet 5 $0.00001 $0.00114
Haiku 4.5 $0.00001 $0.00057

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

Security

Grade A, and why

new-section 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.

.claude/commands/new-section.md · 83 lines

How it starts

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

Create New Section

Create a new section component following AstroDeck patterns from @AGENTS.md.

Arguments provided by the user: $ARGUMENTS

Gather Information

Parse the arguments above. Only ask for what is still missing:

  1. Section name (PascalCase, e.g., "TeamGrid", "PricingTable")
  2. Purpose — what content will it display?
  3. Variants needed — default | centered | wide | compact (default: just default)

If name and purpose are given, proceed without further questions.

Template

---
// src/components/sections/[Name].astro
interface Props {
  title?: string;
  subtitle?: string;
  variant?: 'default' | 'centered' | 'wide';
}

const { 
  title = "Default Title",
  subtitle,
  variant = 'default'
} = Astro.props;

const variantClasses = {
  default: 'max-w-7xl',
  centered: 'max-w-4xl text-center',
  wide: 'max-w-none'
};
---

<section class="py-20 px-6">
  <div class={`mx-auto ${variantClasses[variant]}`}>
    {title && (
      <div class="mb-12">
        <h2 class="text-4xl font-bold mb-4">{title}</h2>
        {subtitle && (
          <p class="text-lg text-muted-foreground">{subtitle}</p>
        )}
      </div>
    )}
    <slot />
  </div>
</section>

Skills

For patterns, consult the astro and ui-design skills (.claude/skills/astro/SKILL.md, .claude/skills/ui-design/SKILL.md).

Placement

A section that isn't on a page is invisible. After creating the component:

  1. Ask the user where to place it — or add it to the most logical page with example data
  2. Never leave a new section unplaced without explicitly telling the user
  3. If placing on an existing page, import the component and add it in a sensible position

Checklist Before Done

  • File created in src/components/sections/[Name].astro
  • Props interface with TypeScript types
  • CSS variables for colors (no hardcoded values)
  • Responsive classes (mobile-first)
  • Supports light and dark mode
  • Uses <slot /> for flexible content
  • Section placed on a page (or user explicitly told where/why not)

Read the full file on GitHub · 83 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. 2d ago First seen · 83 lines · 0 tokens per session scan A f5a3d9f01e60

Subscribe to this mod's changes

new-section is a command published in the GitHub repository holger1411/astrodeck (72 stars, last pushed 26d ago), licensed MIT. It adds 6 tokens to every session and 571 once invoked, about $0.0000 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.