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.
npx skills add Raffa-jarrl/Lictor-AI --skill lictor-rotategit clone --depth 1 https://github.com/Raffa-jarrl/Lictor-AIWrote 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-rotate)<a href="https://agentmods.dev/skills/raffa-jarrl/lictor-ai/lictor-rotate"><img src="https://agentmods.dev/badge/skills/raffa-jarrl/lictor-ai/lictor-rotate/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-rotate"><img src="https://agentmods.dev/badge/skills/raffa-jarrl/lictor-ai/lictor-rotate.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.00080 | $0.03048 |
| Opus 5 | $0.00040 | $0.01524 |
| Sonnet 5 | $0.00016 | $0.00610 |
| Haiku 4.5 | $0.00008 | $0.00305 |
Grade A, and why
lictor-rotate 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 12d 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.
8. **Verify rotation worked:** try the old key with `curl How it starts
The opening of the file, as written. The whole thing — 290 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lictor Rotate — guided key rotation
A key got leaked. The user needs to rotate it. You walk them through the exact steps for their specific provider, without making them dig through documentation.
How invocation works
The user typed /lictor-rotate (with or without a provider name). Three
shapes:
/lictor-rotatealone — ask which provider/lictor-rotate stripe— go straight to the Stripe runbook/lictor-rotate openai sk-...— they pasted the leaked key
If a key string is pasted into the chat: redact it in your reply.
Don't echo sk_live_AAAA...EFGH back at them. Say "your sk_live_*... EFGH key" using only the prefix and last 4 chars. The full key
shouldn't end up in chat logs more times than necessary.
What you do (general flow)
- Confirm urgency. Is the key already in a public repo or a deployed site? If yes, this is "do it in the next hour" urgent. If no (e.g. they found it in a private repo and want to clean up), it's "do it today" urgent.
- Walk them through the provider's rotation flow. Use the provider-specific runbook below. Be specific: the exact URL, the exact button label.
- Tell them what to do with the new key. Replace the old key in
their
.env, restart their dev server, redeploy. - Help them check for damage. Some providers (Stripe, OpenAI) have usage logs they should review for unauthorized activity.
- Confirm the old key is dead. Most providers let you test by trying to use the old key — it should return 401.
Provider runbooks
Stripe
- Open https://dashboard.stripe.com/apikeys
- Find the live secret key (starts with
sk_live_) — match on the prefix the user gave you - Click the
···menu next to it → Roll key - Stripe asks: "How long should the old key remain active?" Pick 0 seconds (immediate revocation) unless they have automated systems they need to update first
- Stripe shows the new key once — copy it now, you can't see it again
- Where to put the new key:
.env.local(or.env.productionfor deployed environment)- Variable name:
STRIPE_SECRET_KEY(or whatever they used) - Restart their dev server
- Redeploy to production (Vercel/Netlify environment variables UI)
- Check for damage:
- https://dashboard.stripe.com/payments — look for charges you don't recognize since the leak
- https://dashboard.stripe.com/logs — API requests; look for IPs you don't recognize
- Verify rotation worked: try the old key with
curl https://api.stripe.com/v1/charges -u <OLD_KEY>:— should return 401 Unauthorized
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.
- 12d ago First seen · 290 lines · 80 tokens per session scan A f2de6c832cf6
lictor-rotate is a skill published in the GitHub repository Raffa-jarrl/Lictor-AI (18 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 80 tokens to every session and 3,048 once invoked, about $0.0004 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
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…
contacts
Manage contacts, communication channels, access control, and invite links.
gmail
Manage Gmail email — drafting, sending, organizing, filters, vacation replies, and inbox analysis.
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…
guardian-verify-setup
Set up channel verification for phone, Telegram, Slack, Discord, or email channels via outbound verification flow.