Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Raffa-jarrl/Lictor-AInpx agentmods add skills/raffa-jarrl/lictor-ai/lictor-security-checkWrote 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.
[](https://agentmods.dev/skills/raffa-jarrl/lictor-ai/lictor-security-check)<a href="https://agentmods.dev/skills/raffa-jarrl/lictor-ai/lictor-security-check"><img src="https://agentmods.dev/badge/skills/raffa-jarrl/lictor-ai/lictor-security-check/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.
<a href="https://agentmods.dev/skills/raffa-jarrl/lictor-ai/lictor-security-check"><img src="https://agentmods.dev/badge/skills/raffa-jarrl/lictor-ai/lictor-security-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00135 | $0.04397 |
| Opus 5 | $0.00068 | $0.02198 |
| Sonnet 5 | $0.00027 | $0.00879 |
| Haiku 4.5 | $0.00014 | $0.00440 |
Grade A, and why
lictor-security-check 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 10d 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.
30. [CI/CD & update integrity](./checks/cicd-pipeline-integrity.md) — unpinned Actions, `curl|bash`, unsigned auto-update How it starts
The opening of the file, as written. The whole thing — 312 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lictor Security Check — pre-release audit
You're running a final pre-launch check on someone's AI-built web app. The person who ran this skill is most likely a founder, designer, or hobbyist who built their app with Lovable, Bolt, v0.dev, Cursor, or by prompting Claude/ChatGPT directly. They are about to deploy or have just deployed.
They are not security people. They will not understand "CORS misconfiguration" or "improper RBAC." Talk to them like you're a friend who happens to know security, not like a pentest report.
This is a read-only audit. You do not modify their code. You analyze
and report. If they want fixes applied, they invoke /lictor-fix-it
separately.
Works on any OS — use your built-in tools, not a specific shell
This skill runs identically on macOS, Windows, and Linux. A founder on a Windows laptop is just as likely as a Mac developer — never assume Bash, WSL, or git-bash is installed.
The example commands in this file and in every check file are written in
bash for readability, but they describe intent — they are not literal
commands to paste. Run each check with your own built-in, cross-platform
tools. They behave the same on every OS and never depend on the user's
shell:
| When a check shows… | Use your built-in tool |
|---|---|
grep -r "pattern" (search file contents) |
Grep |
find … / ls (which files exist, by glob) |
Glob — e.g. **/*.env, **/package.json |
cat / head / tail (read a file) |
Read |
test -f X (does X exist?) |
Glob for X — a non-empty result means it exists |
Only reach for the Bash tool when something genuinely needs a shell
(e.g. npm audit, git remote -v), and prefer commands that exist on
every platform. On Windows the Bash tool may be backed by Git Bash or be
absent entirely, so never rely on a Unix command to decide whether a
finding exists — confirm with Grep/Glob/Read first.
What to do
Step 1 — Look around
Figure out what you're working with by detecting which manifest files
exist. Use Glob for the file checks and Read for package.json — this
works on every OS (the bash below just shows the intent; don't depend on
a shell). Glob for each of these and note which stack each match implies:
What ships with it
60 files 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.
- benchmark/BENCHMARK.md 7.4 KB
- benchmark/corpus-owasp/cases/BenchmarkTest00006/BenchmarkTest00006.java 2.7 KB
- benchmark/corpus-owasp/cases/BenchmarkTest00007/BenchmarkTest00007.java 2.6 KB
- benchmark/corpus-owasp/cases/BenchmarkTest00008/BenchmarkTest00008.java 2.6 KB
- benchmark/corpus-owasp/cases/BenchmarkTest00013/BenchmarkTest00013.java 2.1 KB
- benchmark/corpus-owasp/cases/BenchmarkTest00014/BenchmarkTest00014.java 2.1 KB
- benchmark/corpus-owasp/cases/BenchmarkTest00015/BenchmarkTest00015.java 2.8 KB
- benchmark/corpus-owasp/cases/BenchmarkTest00017/BenchmarkTest00017.java 2.6 KB
- benchmark/corpus-owasp/cases/BenchmarkTest00018/BenchmarkTest00018.java 2.6 KB
- benchmark/corpus-owasp/cases/BenchmarkTest00024/BenchmarkTest00024.java 2.7 KB
- benchmark/corpus-owasp/cases/BenchmarkTest00025/BenchmarkTest00025.java 2.7 KB
- benchmark/corpus-owasp/cases/BenchmarkTest00026/BenchmarkTest00026.java 3.0 KB
- benchmark/corpus-owasp/cases/BenchmarkTest00030/BenchmarkTest00030.java 2.0 KB
- benchmark/corpus-owasp/cases/BenchmarkTest00036/BenchmarkTest00036.java 2.4 KB
- benchmark/corpus-owasp/cases/BenchmarkTest00041/BenchmarkTest00041.java 2.0 KB
- benchmark/corpus-owasp/cases/BenchmarkTest00051/BenchmarkTest00051.java 2.5 KB
- benchmark/corpus-owasp/cases/BenchmarkTest00052/BenchmarkTest00052.java 2.7 KB
- benchmark/corpus-owasp/cases/BenchmarkTest00077/BenchmarkTest00077.java 4.0 KB
- benchmark/corpus-owasp/cases/BenchmarkTest00090/BenchmarkTest00090.java 3.5 KB
- benchmark/corpus-owasp/cases/BenchmarkTest00093/BenchmarkTest00093.java 3.7 KB
- benchmark/corpus-owasp/cases/BenchmarkTest00104/BenchmarkTest00104.java 3.7 KB
- benchmark/corpus-owasp/cases/BenchmarkTest00105/BenchmarkTest00105.java 3.5 KB
- benchmark/corpus-owasp/cases/BenchmarkTest00107/BenchmarkTest00107.java 4.7 KB
- benchmark/corpus-owasp/cases/BenchmarkTest00110/BenchmarkTest00110.java 4.7 KB
- benchmark/corpus-owasp/cases/BenchmarkTest00147/BenchmarkTest00147.java 2.4 KB
- benchmark/corpus-owasp/cases/BenchmarkTest00151/BenchmarkTest00151.java 2.4 KB
- benchmark/corpus-owasp/cases/BenchmarkTest00158/BenchmarkTest00158.java 2.9 KB
- benchmark/corpus-owasp/cases/BenchmarkTest00171/BenchmarkTest00171.java 3.4 KB
- benchmark/corpus-owasp/cases/BenchmarkTest00275/BenchmarkTest00275.java 3.5 KB
- benchmark/corpus-owasp/cases/BenchmarkTest00277/BenchmarkTest00277.java 3.4 KB
- benchmark/corpus-owasp/cases/BenchmarkTest00278/BenchmarkTest00278.java 2.1 KB
- benchmark/corpus-owasp/LICENSE 18 KB
- benchmark/corpus-owasp/manifest.jsonl 5.0 KB
- benchmark/corpus-owasp/README.md 1.2 KB
- benchmark/corpus/cases/env-clean/config.js 203 B runs code
- benchmark/corpus/cases/hardcoded-key-vulnerable/config.js 442 B runs code
- benchmark/corpus/cases/idor-ownership-clean/handler.js 527 B runs code
- benchmark/corpus/cases/idor-vulnerable/handler.js 442 B runs code
- benchmark/corpus/cases/prompt-injection-vulnerable/agent.py 901 B runs code
- benchmark/corpus/cases/sqli-clean/app.js 528 B runs code
- benchmark/corpus/cases/sqli-vulnerable/app.js 505 B runs code
- benchmark/corpus/cases/ssrf-allowlist-clean/fetch.js 645 B runs code
- benchmark/corpus/cases/ssrf-metadata-vulnerable/fetch.js 546 B runs code
- benchmark/corpus/cases/taint-multistep-vulnerable/handler.js 751 B runs code
- benchmark/corpus/cases/taint-sanitized-clean/Comment.jsx 469 B
- benchmark/corpus/manifest.jsonl 2.3 KB
- benchmark/corpus/sample-findings.jsonl 697 B
- benchmark/RESULTS.md 4.9 KB
- benchmark/run_benchmark.py 5.9 KB runs code
- benchmark/runs/2026-06-26-owasp-blind.jsonl 901 B
- checks/admin-paths.md 5.2 KB
- checks/agent-tool-permissions.md 19 KB
- checks/ai-agent.md 6.2 KB
- checks/ai-keys.md 14 KB
- checks/api-auth.md 4.3 KB
- checks/api-inventory.md 20 KB
- checks/audit-logging-gaps.md 16 KB
- checks/authn-session.md 32 KB
- checks/business-flow-automation.md 17 KB
- checks/CHECKS.md 8.5 KB
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.
- 10d ago First seen · 312 lines · 135 tokens per session scan A 2b5ae35f296b
lictor-security-check is a skill published in the GitHub repository Raffa-jarrl/Lictor-AI (18 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 135 tokens to every session and 4,397 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
contacts
Manage contacts, communication channels, access control, and invite links.
gmail
Manage Gmail email — drafting, sending, organizing, filters, vacation replies, and inbox analysis.
guardian-verify-setup
Set up channel verification for phone, Telegram, Slack, Discord, or email channels via outbound verification flow.
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…
schedule
Reminders, automations, and recurring page, dashboard, or status monitoring (cron, RRULE, or fire-at).
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…