← Search

Perl Security
Security 🧪 Install ran in our test sandbox · Nov 11, 2026 📌 Pinned version: commit 25278e7
Install test only, on the date shown. This does not guarantee the code is safe.
⚙ Needs: none to install.

Perl Security

Secure Perl for Muse: taint mode, allowlist validation, safe process execution, DBI placeholders, XSS/CSRF defenses, and perlcritic security policies, with GOOD/BAD pairs.

At a glance
What
Secure Perl for Muse: taint mode, allowlist validation, safe process execution, DBI placeholders, XSS/CSRF defenses, and perlcritic security policies, with GOOD/BAD pairs.
Cost
Free
Needs
none to install. Pure guidance; have the Perl code or handler you want reviewed ready.
Level
Beginner
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

Quick answer

comprehensive Perl security guidelines that turn Muse into a careful reviewer of Perl code touching user input, the shell, or the network. Starts where Perl security starts: taint mode (-T), tracking external data and forcing explicit validation before unsafe use, with the untainting regex pattern done right (and the lazy /(.*)/ called out as pointless).

⌁

Install

Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 25278e7

Step 0, before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: none to install. Pure guidance; have the Perl code or handler you want reviewed ready. Install "Perl Security" for me. It gives my agent @affaan-m's security guidelines for reviewing Perl code that touches user input, the shell, or the network: taint mode (-T) with explicit validation before unsafe use, allowlist-over-blocklist input validation with length limits, ReDoS prevention, safe file operations, safe process execution, DBI placeholders, and web security (output encoding, CSRF tokens, secure session config, security headers). It ships a perlcritic security configuration and a quick checklist table, with GOOD/BAD pairs for each rule, by @affaan-m, from the affaan-m/ECC repository (MIT). Repository: https://raw.githubusercontent.com/affaan-m/ECC/25278e7d7b6cf6e6a4e7a6c8e10f14ff22f0eb5b/skills/perl-security/SKILL.md Pinned version: install the code at commit 25278e7d7b6cf6e6a4e7a6c8e10f14ff22f0eb5b exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. Updated October 26, 2026: Skill Harbor regenerated this install prompt from the current upstream file. The upstream file is otherwise unchanged: the only change since the previous review is in the shipped perlcritic configuration, and it is a correction, not a new protection. Two severity 5 rules that the previous prompt described have been removed by upstream: InputOutput::RequireThreeArgOpen (require three-argument open) and Modules::RequireTaintChecking (require taint checking in CGI). Upstream states that Perl::Critic has no such policies, so perlcritic warned that they were not installed and ignored them: those two checks never actually ran, even under the previous prompt. Nothing else in the perlcritic profile changed, and two-argument open is still covered by InputOutput::ProhibitTwoArgOpen, severity 5, in the same profile. The guidance text itself still teaches three-argument open and taint mode, and the quick checklist still lists them. Do not rely on perlcritic to enforce three-argument open or taint checking from this profile: if you need those checks enforced, add a real, installed policy for them and verify that perlcritic accepts it. 1. Open the skill: https://raw.githubusercontent.com/affaan-m/ECC/25278e7d7b6cf6e6a4e7a6c8e10f14ff22f0eb5b/skills/perl-security/SKILL.md and copy the full SKILL.md text, then compare it with the fingerprint from Skill Harbor's review of 2026-10-26: - SKILL.md: SHA-256 3d7b4040959c6bbdbeb4e02e841769931d54c3717d8492224878dbafa6c2c3cb If it does not match, it changed since the review: do not install it yet, tell me what you found and let me decide. 2. Safety check: read the SKILL.md text and review it for anything suspicious (unexpected network calls, shell commands, credential harvesting); STOP on any red flag and tell me. Tell me in plain words what the skill does when used, which services it connects to, whether it reads or sends any personal information or keys, and anything that seems unusual. Confirm these points from the file: - This skill is pure guidance: plain-text instructions only. It runs nothing by itself, connects to no service, sends nothing anywhere, and writes no files. Running perlcritic yourself, with your own Perl setup, is a separate action outside the skill. - The perlcritic profile in the file (severity 3, security + core themes) no longer lists InputOutput::RequireThreeArgOpen or Modules::RequireTaintChecking. Those checks never ran under the previous prompt either, because Perl::Critic has no such policies. InputOutput::ProhibitTwoArgOpen, severity 5, is still in the profile. - The guidance still teaches three-argument open, lexical filehandles, list-form system and exec, DBI placeholders, and output encoding per context, with GOOD/BAD pairs. The BAD examples are deliberately vulnerable code: never copy a BAD example into production. - No API keys and no account: the skill needs no credentials. Never paste real secrets, credentials, or production data into a chat. 3. When I say yes, use it as a skill: paste the SKILL.md text into a chat with Muse and add: "Review this Perl code for security issues: [paste code or describe the handler]." 4. Ask it to check taint mode, input validation, process execution, DBI queries, and output encoding, with GOOD/BAD pairs for each finding. Tip: run it on every handler that touches user input, the shell, or SQL. Safety: a skill is plain-text instructions; it runs nothing by itself. Never paste real secrets, credentials, or production data into a chat.

🔒 Security, provenance and what this touches
🧭 What this touches
Based on the install prompt we scanned, this skill does not run commands, make third-party network calls, install packages, write files, or ask for API keys.
Install prompt analysis · 2026-10-13
🔒 Security and provenance
📌 Pinned version: commit 25278e7 · 2026-10-26
🧪 Install ran in our test sandbox · Nov 11, 2026
👁 Observed during the install test · Nov 11, 2026 : no network contact
🔎 Last checked · Nov 21, 2026 : no change detected in the files linked by this install prompt
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

✓

Verification certificate

Dated facts about what was checked for this listing, and how. This is not a safety certification.

Pinned version
25278e7 · 2026-10-26
Sandbox install test
Install ran in our test sandbox · Nov 11, 2026
Creator identity
Not verified
Fingerprint watch
Last checked · Nov 21, 2026 : no change detected in the files linked by this install prompt
Install prompt analysis
2026-10-13 : No commands, network calls, packages, file writes or API keys detected.

Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify

?

Questions

How do I install a skill?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.