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 MacareuxDigital/concretecms-skills --skill building-themesgit clone --depth 1 https://github.com/MacareuxDigital/concretecms-skillsWrote 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/macareuxdigital/concretecms-skills/building-themes)<a href="https://agentmods.dev/skills/macareuxdigital/concretecms-skills/building-themes"><img src="https://agentmods.dev/badge/skills/macareuxdigital/concretecms-skills/building-themes/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/macareuxdigital/concretecms-skills/building-themes"><img src="https://agentmods.dev/badge/skills/macareuxdigital/concretecms-skills/building-themes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00047 | $0.01625 |
| Opus 5 | $0.00023 | $0.00813 |
| Sonnet 5 | $0.00009 | $0.00325 |
| Haiku 4.5 | $0.00005 | $0.00162 |
Grade A, and why
building-themes 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.
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Building Themes
Overview
This skill enables the development of professional, feature-rich themes for Concrete CMS. It covers the essential components like page_theme.php, page templates, asset registration, and advanced features such as grid support and containers.
For the most up-to-date best practices and implementation examples, refer to the concrete/themes/atomik directory in the core. It serves as the primary reference for modern theme development in Concrete CMS.
Workflow
1. Setup Theme Directory
Themes should be placed within a package for better portability. Otherwise, they can be stored in the application directory.
- Path:
packages/your_package_handle/themes/your_theme_handle/ - Path:
application/themes/your_theme_handle/
2. Create Core Files
Every theme requires at least:
page_theme.php: The main configuration class for the theme.default.php: The default page template.view.php: Required for single pages. Should include thesystem_errorselement and$innerContent.elements/header.php&elements/footer.php: Shared header and footer.- Recommended: Sub-divide elements for simplicity (e.g.,
elements/header_top.php,elements/header.php,elements/footer.php,elements/footer_bottom.php).
3. Configure page_theme.php
- Define namespace:
Concrete\Package\YourPackageHandle\Theme\YourThemeHandle - Required Methods:
getThemeName(): Return the localized name of the theme.getThemeDescription(): Return the localized description of the theme.
- Implement
getThemeSupportedFeatures()to optimize asset loading.- JS Library Themes: If the theme includes a full-featured JavaScript library (e.g., Bootstrap 5 JS, jQuery), list all supported features (e.g.,
FeatureConstants::NAVIGATION,FeatureConstants::FORMS) to avoid conflicts with Concrete's internal asset loading. - No-JS Themes: If the theme does not include any JavaScript, it is recommended not to implement this method.
- JS Library Themes: If the theme includes a full-featured JavaScript library (e.g., Bootstrap 5 JS, jQuery), list all supported features (e.g.,
- Configure grid support via
$pThemeGridFrameworkHandle.- Core Frameworks: If using a supported framework (e.g.,
bootstrap5,bootstrap4), set this property to the corresponding handle. - Custom Frameworks: If the theme uses a custom or unsupported CSS framework (e.g., Tailwind, Bulma), do not set this property.
- Supported Handles: Find available frameworks in
concrete/src/Page/Theme/GridFramework/Type(e.g.,bootstrap5,foundation,nine_sixty).
- Core Frameworks: If using a supported framework (e.g.,
What ships with it
1 file 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.
- 12d ago First seen · 87 lines · 47 tokens per session scan A c92229e538bf
building-themes is a skill published in the GitHub repository MacareuxDigital/concretecms-skills (9 stars, last pushed 3mo ago), licensed MIT. It adds 47 tokens to every session and 1,625 once invoked, about $0.0002 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-31.
Other skills, from other repositories
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ultragoal with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
animation-principles
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.
refactoring-ui
Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off" (or amateur/unprofessional), "fix the design", "Tailwind styling", "color palette", "visual hierarchy", "design system", "spacing scale", or "component styling". Also trigger when building consistent…