Skip to content
TrustedSkillsbeta
Back to all skills

Typo3 Security

Checked
dirnbauer·vlatest·backend

Identifies and remediates common Typo3 vulnerabilities, improving site security based on dirnbauer's expertise.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add dirnbauer/webconsulting-skills --skill typo3-security -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

dirnbauer

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned dirnbauer/webconsulting-skills at 98b562d70f.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
98b562d70f
Manifest
skills/typo3-security/SKILL.md
Scanned
3 files, 546 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill, "Typo3 Security," helps AI agents harden Typo3 websites by applying security best practices based on dirnbauer’s expertise. It focuses on configuring critical settings within the config/system/settings.php file to improve backend and frontend security. The skill is compatible with TYPO3 version 14.x and emphasizes utilizing existing TYPO3 APIs rather than creating custom solutions.

When to use it

  • When securing a new Typo3 v14 installation.
  • During routine security audits of an existing Typo3 website.
  • To enforce stricter password policies on backend user accounts.
  • To disable debug mode in production environments.

Key capabilities

  • Disables debugging in production (BE.debug and FE.debug).
  • Configures session locking based on IP address (BE.lockIP, BE.lockIPv6, FE.lockIP).
  • Sets session timeouts for both backend and frontend users (BE.sessionTimeout, FE.sessionTimeout).
  • Enforces HTTPS requirements for the backend (BE.lockSSL).
  • Implements Argon2id password hashing for improved security.
  • Provides guidance on enforcing HTTPS at the web server/proxy level using HSTS.

Example prompts

  • "Harden the Typo3 backend security settings."
  • "Disable debug mode in the Typo3 frontend configuration."
  • "Set the backend session timeout to 1 hour."
  • “Apply Argon2id password hashing for all TYPO3 users.”

Tips & gotchas

  • This skill is specifically designed for Typo3 version 14.x. Compatibility with other versions is not guaranteed.
  • FE.lockSSL has been removed in v12; enforce HTTPS at the web server/proxy level instead, using HSTS headers.
  • Always consult the official TYPO3 documentation to verify API availability and avoid deprecated methods.