lms-front: Skill for Claude Code

.agents/skills/security-review/SKILL.md

security-review is a skill for Claude Code, Codex from guillermoscript/lms-front. It costs 61 tokens per session (2,839 once invoked), scanned A, a copy of security-review, MIT.

A code-review process focused on finding security vulnerabilities that attackers could actually exploit. It checks issues such as injection, cross-site scripting, login controls, permissions, and cryptography.

In plain words
What is it for?
Reviewing a specified file, code change, or codebase for high-confidence security issues, with severity and supporting evidence.
Why use it?
It reduces false alarms by tracing user-controlled data through the code and checking existing protections before reporting a problem.

Skill for Claude CodeCodex

Written for Claude Code: allowed-tools in frontmatter. Also seen: installed under .agents/ (shared by several agents).

This is guillermoscript/lms-front's own configuration. It tells Claude Code and Codex how to work on lms-front 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 lms-front configures →

Reuse

Borrowing it

Nothing to install: this file belongs to guillermoscript/lms-front. 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/guillermoscript/lms-front/master/.agents/skills/security-review/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/guillermoscript/lms-front

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 security-review

README.md
[![agentmods](https://agentmods.dev/badge/skills/guillermoscript/lms-front/security-review/github.svg)](https://agentmods.dev/skills/guillermoscript/lms-front/security-review)
Your own site
<a href="https://agentmods.dev/skills/guillermoscript/lms-front/security-review"><img src="https://agentmods.dev/badge/skills/guillermoscript/lms-front/security-review/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 security-review

Your own site · 80×15
<a href="https://agentmods.dev/skills/guillermoscript/lms-front/security-review"><img src="https://agentmods.dev/badge/skills/guillermoscript/lms-front/security-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 61 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,839 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 2 findings. 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.00061 $0.02839
Opus 5.5 $0.00024 $0.01136
Sonnet 5.5 $0.00012 $0.00568
Haiku 4.5 $0.00006 $0.00284

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

Security

Grade A, and why

security-review scanned grade A with 2 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 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.

response = requests.get(f"{settings.SEER_AUTOFIX_URL}{path}")

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

child_process.exec(user) # Node.js
Origin

This is a copy

100% identical to security-review — 0 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.

.agents/skills/security-review/SKILL.md · 313 lines

How it starts

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

Security Review Skill

Identify exploitable security vulnerabilities in code. Report only HIGH CONFIDENCE findings—clear vulnerable patterns with attacker-controlled input.

Scope: Research vs. Reporting

CRITICAL DISTINCTION:

  • Report on: Only the specific file, diff, or code provided by the user
  • Research: The ENTIRE codebase to build confidence before reporting

Before flagging any issue, you MUST research the codebase to understand:

  • Where does this input actually come from? (Trace data flow)
  • Is there validation/sanitization elsewhere?
  • How is this configured? (Check settings, config files, middleware)
  • What framework protections exist?

Do NOT report issues based solely on pattern matching. Investigate first, then report only what you're confident is exploitable.

Confidence Levels

Level Criteria Action
HIGH Vulnerable pattern + attacker-controlled input confirmed Report with severity
MEDIUM Vulnerable pattern, input source unclear Note as "Needs verification"
LOW Theoretical, best practice, defense-in-depth Do not report

Do Not Flag

General Rules

  • Test files (unless explicitly reviewing test security)
  • Dead code, commented code, documentation strings
  • Patterns using constants or server-controlled configuration
  • Code paths that require prior authentication to reach (note the auth requirement instead)

Server-Controlled Values (NOT Attacker-Controlled)

These are configured by operators, not controlled by attackers:

Source Example Why It's Safe
Django settings settings.API_URL, settings.ALLOWED_HOSTS Set via config/env at deployment
Environment variables os.environ.get('DATABASE_URL') Deployment configuration
Config files config.yaml, app.config['KEY'] Server-side files
Framework constants django.conf.settings.* Not user-modifiable
Hardcoded values BASE_URL = "https://api.internal" Compile-time constants

Read the full file on GitHub · 313 lines

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 · 313 lines · 61 tokens per session scan A 6d36fa39ada8

Subscribe to this mod's changes

security-review is a skill published in the GitHub repository guillermoscript/lms-front (40 stars, last pushed today), licensed MIT. It adds 61 tokens to every session and 2,839 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 2 findings (makes network calls, runs shell commands). It is 100% identical to security-review, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

review-animations

Reviews animation and motion code against a high craft bar derived from Emil Kowalski's design engineering philosophy. Default to flagging; approval is earned.

classroomio/classroomio · 34 tokens

ship-feature

End-to-end feature delivery — implement a feature, verify builds/tests pass, open a fully-filled draft PR, then automatically push every feedback round and review iteration to the same PR. Use when the user asks to implement or build a feature, fix-and-ship a change, or iterate on an existing feature PR.

classroomio/classroomio · 66 tokens

cross-model-review

A second-opinion code review that asks a different AI model to independently inspect a change, then compares both reviews. It focuses on logic, security, consistency, and omissions.

hashgraph-online/awesome-codex-plugins · 56 tokens

review-system-design

Review a system design someone else provided - screenshot, drawio, Mermaid, slides, doc, or IaC - by extracting it into a confirmed fact sheet, then scoring it on the nine axes.

HoangNguyen0403/agent-skills-standard · 44 tokens

review-ticket

Review a ticket or PR through focused specialist lenses: scope, architecture, security, tests, AC coverage, and PR metadata.

HoangNguyen0403/agent-skills-standard · 28 tokens

common-feedback-reporter

Pre-write audit for skill violations: checks planned code against loaded skill anti-patterns before any file write. Use when writing Flutter/Dart/TS code or editing SKILL.md files with active project skills. Load as composite; on auto-fixed violation, also load +common/common-learning-log.

HoangNguyen0403/agent-skills-standard · 63 tokens