grove

grove is a skill for Claude Code, Codex from aimeos/pagible. It costs 45 tokens per session (1,112 once invoked), scanned A, original, MIT.

A visual design guide for gardeners, landscapers, garden designers, and garden-maintenance companies. It defines the layout, colours, typography, imagery, and content priorities for a garden-services website.

In plain words
What is it for?
Use it when building or styling a gardening or landscaping website, including project galleries, service and care-plan sections, team details, reviews, and quote requests.
Why use it?
It creates a consistent presentation and puts quotes, services, projects, care plans, trust details, and service areas where visitors can find them.

Skill for Claude CodeCodex

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

Good fit Use it when building or styling a gardening or landscaping website, including project galleries, service and care-plan sections, team details, reviews, and quote requests.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/aimeos/pagible/grove
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 aimeos/pagible --skill grove
Clone the repo
git clone --depth 1 https://github.com/aimeos/pagible

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 grove

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/aimeos/pagible/grove"><img src="https://agentmods.dev/badge/skills/aimeos/pagible/grove.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,112 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.
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.00045 $0.01112
Opus 5.5 $0.00018 $0.00445
Sonnet 5.5 $0.00009 $0.00222
Haiku 4.5 $0.00005 $0.00111

Measured 5d ago against content hash 6cf533ef5763, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

grove 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 5d 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.

themes/grove/SKILL.md · 47 lines

How it starts

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

Grove Theme Design System

Direction

Use a calm, warm and trustworthy layout that feels like a well-kept garden: cream paper, deep greens, terracotta pots and soft curves. Put the free quote, the phone number, the services, recent projects and the care plans first, followed by what builds trust: insurance and accreditations, the plant guarantee, the same gardener on every visit, reviews, the team and the areas covered. Show finished gardens, lush borders, lawns, patios, ponds, planting hands and gardeners at work; avoid bare soil without context, brown dead lawns, chemical sprays, heavy machinery and stock handshakes.

Foundations

  • Use only the markup and classes supplied by ./theme/views/.
  • Use system fonts (serif display headings with italic accents, sans-serif body) and the existing --pico-* variables.
  • Keep page content within a 1280px maximum width.
  • Use the cream (#F6F2EA, #FFFDF8) background, forest green (#1F3A2C, #2D4E3C) for headings, heroes, the highlighted care plan and the footer, moss green (#3F6B3A) for links, filled buttons and accents in headings, terracotta (#A0532D) for eyebrows and leaf marks, and chartreuse (#C5D86D) only on dark green.
  • Use soft 1rem corners, pill-shaped buttons, tags and badges, leaf-shaped team images, round avatars, leaf marks before section headings and curved edges below heroes and above the footer.

Components

  • Hero: a 16:9 garden photo in background with the text on a leaf-shaped translucent green panel, an eyebrow naming the services and region, a short headline with an accent in *...* and two actions ("Get a free quote" and "See our projects"). Nest service pages (garden design, landscaping, garden maintenance, lawns and hedges) below a top-level page so the header keeps about six links next to the phone number and "Free quote".
  • Figures and badges: cards in the figures layout for rating, gardens in care, founding year and plant guarantee, and in the badges layout with white line icons for insurance, accreditation, plant guarantee, the same gardener and peat-free gardening.
  • Services: cards in three columns with a photo, the service as title, a link to its page and a bold first line as eyebrow ("Design", "Build", "Care").
  • Process: a horizontal timeline with four steps from the free garden visit to regular care.
  • Projects: cards in three columns with a photo, the project as title and the place and year as inline code, plus a before-after element with two photos of the same size.
  • Care plans: a pricing element with three plans priced per visit, how often in the text, features as list items with inline code for the season or frequency, the most popular plan highlighted, followed by a table of seasonal jobs and questions about contracts, access and green waste.
  • Team: cards in four columns with 4:5 portraits, the name as title and a bold first line with the role.
  • Journal: blog pages below the journal page (status 2, hidden in navigation), each with an article, key figures, a vertical step timeline, questions and a call to action.
  • Contact: a hero, cards for the areas covered, a map with directions and a contact form; a hidden quote page with a form asking for postcode, service, garden size and budget.
  • Footer: service, customer and company links and a seasonal newsletter card; the layout adds the address, office hours, service areas and notice from the garden config below it.
  • Garden details: the garden config adds the local business JSON-LD with the service area, the top bar with the announcement and towns served, the phone number and "Free quote" button in the header, the footer address, hours, areas and notice and the action bar for phones.

Read the full file on GitHub · 47 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. 5d ago First seen · 47 lines · 45 tokens per session scan A 6cf533ef5763

Subscribe to this mod's changes

grove is a skill published in the GitHub repository aimeos/pagible (596 stars, last pushed today), licensed MIT. It adds 45 tokens to every session and 1,112 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-10-13.

Related

Other skills, from other repositories

api-designer

Designs production-grade APIs — REST, GraphQL, gRPC, and AsyncAPI patterns including pagination, versioning, error handling, rate limiting, and API governance. Use when the user asks to design APIs, create endpoints, build an API layer, write OpenAPI specs, or needs help with REST/GraphQL/gRPC service design.

buiphucminhtam/forgewright · 73 tokens

api-design-first

Design-first API development skill. Generates OpenAPI 3.1 specifications, enforces REST design best practices, validates endpoints, handles versioning, pagination, error formatting, authentication patterns, rate limiting, and idempotency. Activates when users say "design an API", "create OpenAPI spec", "API endpoint"…

JPeetz/agent-skills · 117 tokens

strapi-cms

Customisable headless CMS with Strapi.

bidewio/better-openclaw · 13 tokens

api-design

Applies REST and GraphQL design principles to produce or review an API contract.

MarieLynneBlock/arcanum-artifex · 19 tokens

api-integration-architect

Design, implement, debug, and optimize API integrations with expert-level patterns for REST, GraphQL, webhooks, and authentication flows.

sickn33/agentic-awesome-skills · 33 tokens

scalar-design-system

Scalar's design system — design tokens, theming (@scalar/themes), CSS variables, and the @scalar/components library. Use when designing or implementing Scalar UI, especially with Paper (code-to-design / design-to-code), so output matches real Scalar tokens, colors, typography, spacing, and components instead of…

scalar/scalar · 68 tokens