mcp-plesk-dev-docs: Skill for Claude Code

.github/skills/best-practices/SKILL.md

best-practices is a skill for Claude Code, Codex from barateza/mcp-plesk-dev-docs. It costs 49 tokens per session (3,016 once invoked), scanned A, a copy of best-practices, MIT.

A checklist and guidance set for reviewing modern web code, including security, browser compatibility, and code quality.

In plain words
What is it for?
Use it for security audits, vulnerability checks, code-quality reviews, and modernizing web projects.
Why use it?
It helps find common web risks and compatibility problems before they affect users. It also gives patterns for addressing issues such as insecure connections and missing security policies.

Skill for Claude CodeCodex

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

This is barateza/mcp-plesk-dev-docs's own configuration. It tells Claude Code and Codex how to work on mcp-plesk-dev-docs itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything mcp-plesk-dev-docs configures →

Reuse

Borrowing it

Nothing to install: this file belongs to barateza/mcp-plesk-dev-docs. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/barateza/mcp-plesk-dev-docs/main/.github/skills/best-practices/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/barateza/mcp-plesk-dev-docs

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 best-practices

README.md
[![agentmods](https://agentmods.dev/badge/skills/barateza/mcp-plesk-dev-docs/best-practices/github.svg)](https://agentmods.dev/skills/barateza/mcp-plesk-dev-docs/best-practices)
Your own site
<a href="https://agentmods.dev/skills/barateza/mcp-plesk-dev-docs/best-practices"><img src="https://agentmods.dev/badge/skills/barateza/mcp-plesk-dev-docs/best-practices/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 best-practices

Your own site · 80×15
<a href="https://agentmods.dev/skills/barateza/mcp-plesk-dev-docs/best-practices"><img src="https://agentmods.dev/badge/skills/barateza/mcp-plesk-dev-docs/best-practices.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,016 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod 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.00049 $0.03016
Opus 5.5 $0.00020 $0.01206
Sonnet 5.5 $0.00010 $0.00603
Haiku 4.5 $0.00005 $0.00302

Measured 1mo ago against content hash d744beb8723d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

best-practices scanned grade A with 1 finding 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 1mo 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

const response = await fetch(url);
Origin

This is a copy

100% identical to best-practices — 217 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.github/skills/best-practices/SKILL.md · 605 lines

How it starts

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

Best practices

Modern web development standards based on Lighthouse best practices audits. Covers security, browser compatibility, and code quality patterns.

Security

HTTPS everywhere

Enforce HTTPS:

<!-- ❌ Mixed content -->
<img src="http://example.com/image.jpg" />
<script src="http://cdn.example.com/script.js"></script>

<!-- ✅ HTTPS only -->
<img src="https://example.com/image.jpg" />
<script src="https://cdn.example.com/script.js"></script>

<!-- ✅ Protocol-relative (will use page's protocol) -->
<img src="//example.com/image.jpg" />

HSTS Header:

Strict-Transport-Security: max-age=31536000; includeSubDomains; preload

Content Security Policy (CSP)

<!-- Basic CSP via meta tag -->
<meta
  http-equiv="Content-Security-Policy"
  content="default-src 'self';
               script-src 'self' https://trusted-cdn.com;
               style-src 'self' 'unsafe-inline';
               img-src 'self' data: https:;
               connect-src 'self' https://api.example.com;"
/>

<!-- Better: HTTP header -->

CSP Header (recommended):

Content-Security-Policy:
  default-src 'self';
  script-src 'self' 'nonce-abc123' https://trusted.com;
  style-src 'self' 'nonce-abc123';
  img-src 'self' data: https:;
  connect-src 'self' https://api.example.com;
  frame-ancestors 'self';
  base-uri 'self';
  form-action 'self';

Using nonces for inline scripts:

<script nonce="abc123">
  // This inline script is allowed
</script>

Security headers

# Prevent clickjacking
X-Frame-Options: DENY

# Prevent MIME type sniffing
X-Content-Type-Options: nosniff

# Enable XSS filter (legacy browsers)
X-XSS-Protection: 1; mode=block

# Control referrer information
Referrer-Policy: strict-origin-when-cross-origin

# Permissions policy (formerly Feature-Policy)
Permissions-Policy: geolocation=(), microphone=(), camera=()

No vulnerable libraries

# Check for vulnerabilities
npm audit
yarn audit

# Auto-fix when possible
npm audit fix

# Check specific package
npm ls lodash

Read the full file on GitHub · 605 lines

Files

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.

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. 1mo ago First seen · 605 lines · 49 tokens per session scan A d744beb8723d

Subscribe to this mod's changes

best-practices is a skill published in the GitHub repository barateza/mcp-plesk-dev-docs (2 stars, last pushed 2mo ago), licensed MIT. It adds 49 tokens to every session and 3,016 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to best-practices, differing in 217 lines, and is treated as a copy.

Related

Other skills, from other repositories

code-review

Review code for quality, maintainability, and correctness.

PrefectHQ/fastmcp · 10 tokens

reviewing-update-sets

Reviewing, analyzing, and comparing ServiceNow update sets before promotion, singly or in batches. Shows changes, risks, dependencies, and conflicts. Use when the user mentions update sets, customizations, promotion, code review, change tracking, pre-deployment review, sysupdatexml, customer updates, 'what changed in…

jschuller/mcp-server-servicenow · 82 tokens

differential-review

Performs security-focused differential review of code changes (PRs, commits, diffs). Adapts analysis depth to codebase size, uses git history for context, calculates blast radius, checks test coverage, and generates comprehensive markdown reports. Automatically detects and prevents security regressions.

msradam/theodosia · 61 tokens

release-pr-review

Review pass on an open release PR (release/ → main) — the step between git-wrapup and release-and-publish when a project releases in gated release PR mode. Reads the PR's commit range through the code-simplifier lens plus a correctness review, verifies whatever an automated reviewer left on the PR, lands fixes as…

cyanheads/obsidian-mcp-server · 136 tokens

review

Adversarial review of an increment before it ships, by a fresh context or another model family; every finding cites path:line and is re-verified. Use for "review", "qa", "critique this".

anton-abyzov/specweave · 45 tokens

guidance

Authoritative guidance for building Claude Code skills, agents, and plugins, vendored into this repository. Use when you need the rules or best practices for a skill, agent, hook, or plugin — designing, reviewing, hardening, or checking one against the guidance. Does not run an interview to build a new skill or agent…

testdouble/han · 95 tokens