lictor-explain

lictor-explain is a skill for Claude Code from Raffa-jarrl/Lictor-AI. It costs 56 tokens per session (4,339 once invoked), scanned A, original, Apache-2.0.

A plain-English translator for security findings, error messages, and technical warnings. It explains what a problem means, why it matters in the specific project, and what to do next.

In plain words
What is it for?
Use it to understand findings from security checks, code errors with security implications, and warnings from common development tools.
Why use it?
It removes the need to understand specialist security terms when reviewing reports from audits or tools such as GitHub Security and npm audit.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions subagents.

Part of the lictor-security-suite plugin — 4 skills shipped together

Good fit Use it to understand findings from security checks, code errors with security implications, and warnings from common development tools.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/raffa-jarrl/lictor-ai/lictor-explain
Install

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.

Any agent
npx skills add Raffa-jarrl/Lictor-AI --skill lictor-explain
Clone the repo
git clone --depth 1 https://github.com/Raffa-jarrl/Lictor-AI

Made for: Claude Code.

Or install lictor-security-suite, the plugin that ships this one along with the rest of its 4 skills.

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 lictor-explain

README.md
[![agentmods](https://agentmods.dev/badge/skills/raffa-jarrl/lictor-ai/lictor-explain/github.svg)](https://agentmods.dev/skills/raffa-jarrl/lictor-ai/lictor-explain)
Your own site
<a href="https://agentmods.dev/skills/raffa-jarrl/lictor-ai/lictor-explain"><img src="https://agentmods.dev/badge/skills/raffa-jarrl/lictor-ai/lictor-explain/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 lictor-explain

Your own site · 80×15
<a href="https://agentmods.dev/skills/raffa-jarrl/lictor-ai/lictor-explain"><img src="https://agentmods.dev/badge/skills/raffa-jarrl/lictor-ai/lictor-explain.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,339 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 original No closer match found 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.00056 $0.04339
Opus 5 $0.00028 $0.02169
Sonnet 5 $0.00011 $0.00868
Haiku 4.5 $0.00006 $0.00434

Measured 9d ago against content hash f3e54516dbfa, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

lictor-explain 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 9d 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.

Strips warnings and disclaimerslowAnti-refusal

Omitting safety caveats hides risk from the user and is a common jailbreak preamble.

open. They turn the screen to you and say "what is this?" You don't lecture.

Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.

skills/plugins/lictor-security-suite/skills/lictor-explain/SKILL.md · 345 lines

How it starts

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

Lictor Explain — security translator

You translate security speak into human speak.

The person who invoked this skill is most likely:

  • Looking at a finding from /lictor-security-check and confused
  • Looking at an error in their code that has a security implication
  • Looking at a warning from GitHub Security, Dependabot, npm audit, or a similar tool
  • Looking at a generic security article and not following

They don't have a security background. Your job is to take whatever they paste, and give them back (a) what it means in plain English, (b) why it actually matters in their specific case, and (c) what they should do about it.

The voice

Imagine you're sitting next to them in a coffee shop. Their MacBook is open. They turn the screen to you and say "what is this?" You don't lecture. You don't quote Wikipedia. You explain it the way you'd explain it to your sister who works in marketing.

Examples of the voice

Bad (jargon-heavy):

Cross-Site Scripting (XSS) is a class of code injection vulnerability wherein an attacker injects malicious scripts into trusted websites, which are then executed in the victim's browser context, potentially compromising session tokens and enabling impersonation attacks.

Good (plain English):

XSS means: someone can put bad code into your website that runs on other people's browsers. Imagine a comment form on your site. Someone writes a "comment" that's secretly JavaScript. When the next user loads the page and sees that comment, the JavaScript runs in their browser — using their logged-in session. The attacker now does things as that user without them knowing.

In your specific case: you're rendering user input directly into HTML on line 47 without escaping it. That's the door. The fix is one function call.

How to handle a few common ask shapes

"What does this audit finding mean?"

They paste a finding from /lictor-security-check. Take it apart:

  1. The plain-English version — restate the title without jargon
  2. The concrete scenario — "Here's what someone would do to exploit this..."
  3. Why it's THAT severity — explain why critical vs medium based on actual blast radius
  4. The fix — short, code-snippet if useful

Read the full file on GitHub · 345 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. 9d ago First seen · 345 lines · 56 tokens per session scan A f3e54516dbfa

Subscribe to this mod's changes

lictor-explain is a skill published in the GitHub repository Raffa-jarrl/Lictor-AI (18 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 56 tokens to every session and 4,339 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (strips warnings and disclaimers). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

contacts

Manage contacts, communication channels, access control, and invite links.

vellum-ai/vellum-assistant · 14 tokens

gmail

Manage Gmail email — drafting, sending, organizing, filters, vacation replies, and inbox analysis.

vellum-ai/vellum-assistant · 20 tokens

app-builder

Build and edit small, personal visual tools and artifacts — dashboards, trackers, calculators, data visualizations, charts, simple landing pages, and slide decks the user wants for THEMSELVES. This is the right skill whenever the user asks to "visualize this," "make a chart," or "build an artifact" for their own use…

vellum-ai/vellum-assistant · 162 tokens

assistant-migration

Migrate from ChatGPT, Claude, OpenClaw, Hermes, Manus, and other AI assistants into Vellum by inspecting their data exports, conversation archives, files, prompts, custom instructions, memory, saved memories, tools, GPTs, workflows, integrations, and relationships, then mapping as much as safely possible into Vellum…

vellum-ai/vellum-assistant · 90 tokens

guardian-verify-setup

Set up channel verification for phone, Telegram, Slack, Discord, or email channels via outbound verification flow.

vellum-ai/vellum-assistant · 26 tokens

vellum-memory-v3-migration

One-time migration of an existing memory-v2 concept corpus into the memory-v3 section-grain "wiki" — topical articles with a stand-alone lead and queryable sections — with loss-proof staging, assistant-reviewed authoring, and a retrieval-eval gate before cutover.

vellum-ai/vellum-assistant · 63 tokens