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 mittwald/typo3-smart-extension-builder --skill typo3-sitepackagegit clone --depth 1 https://github.com/mittwald/typo3-smart-extension-builderWrote 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/mittwald/typo3-smart-extension-builder/typo3-sitepackage)<a href="https://agentmods.dev/skills/mittwald/typo3-smart-extension-builder/typo3-sitepackage"><img src="https://agentmods.dev/badge/skills/mittwald/typo3-smart-extension-builder/typo3-sitepackage/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/mittwald/typo3-smart-extension-builder/typo3-sitepackage"><img src="https://agentmods.dev/badge/skills/mittwald/typo3-smart-extension-builder/typo3-sitepackage.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.00020 | $0.01671 |
| Opus 5 | $0.00010 | $0.00835 |
| Sonnet 5 | $0.00004 | $0.00334 |
| Haiku 4.5 | $0.00002 | $0.00167 |
Grade A, and why
typo3-sitepackage 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 — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TYPO3 Site Package Development Skill
This skill guides you through creating a TYPO3 site package - a special extension that contains all site-specific templates, configuration, and assets.
Prerequisites
Before starting, gather the following information from the user:
- Extension key - lowercase with underscores (e.g.,
my_site) - PHP vendor namespace - PascalCase (e.g.,
MyCompany) - Author information - name, email, company (retrieve from git config if not provided)
- Base package type - which template base to use:
site_package_tutorial- Minimal setup for learningbootstrap_package- Based on Bootstrap frameworkfluid_styled_content- Based on TYPO3's default content rendering
- Required extensions - any additional TYPO3 extensions to include as dependencies (e.g., news, form)
Workflow
Step 1: Create Site Package
Use typo3_create_sitepackage to create the site package structure.
DO NOT make any assumptions about the authorship information. Either ask the user for it or retrieve it from git config. Always ensure the extension key and PHP vendor namespace are provided by the user. You are allowed to make suggestions.
Tool: typo3_create_sitepackage
Parameters:
- extensionKey: (from user, e.g., "my_site")
- phpVendorNamespace: (from user, e.g., "MyCompany")
- title: (e.g., "My Company Website")
- description: (1-2 sentences about the site)
- author: (from user or git config)
- authorEmail: (from user or git config)
- authorCompany: (company name)
- type: (one of: site_package_tutorial, bootstrap_package, fluid_styled_content)
- homepage: (optional, company website URL)
Step 2: Configure Composer
If the user provided additional required extensions, add them as dependencies in the composer.json of the site package.
Step 3: Create Site Set
Site sets are TYPO3's modern way to configure sites. Create one for your site package.
Use typo3_create_site_set:
Tool: typo3_create_site_set
Parameters:
- extensionKey: (from step 1)
- identifier: (composer package name, e.g., "mycompany/my-site")
- path: (directory name, e.g., "my-site")
- label: (human readable, e.g., "My Company Site")
- dependencies: (optional array, e.g., ["typo3/fluid-styled-content"])
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 · 216 lines · 20 tokens per session scan A 3d10054a7316
typo3-sitepackage is a skill published in the GitHub repository mittwald/typo3-smart-extension-builder (11 stars, last pushed 4mo ago), licensed MIT. It adds 20 tokens to every session and 1,671 once invoked, about $0.0001 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
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.
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
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.
menu-transitions-rtl
Animate react-horizontal-scrolling-menu scrolling and build right-to-left menus: noPolyfill defaults to true since v8, so transitionDuration (default 500), a custom-easing-function transitionBehavior, and per-call ScrollOptions { duration, boundary } on scrollToItem/scrollNext/scrollPrev are silently ignored unless…