lookup-liberty91

lookup-liberty91 is a skill for Claude Code, Codex from Liberty91LTD/cti-skills. It costs 0 tokens per session (5,274 once invoked), scanned A, original, MIT.

A connector to Liberty91, a threat-intelligence platform that links real-world cyber incidents with their reports, sources, reliability, and affected organisations. It can also manage intelligence and organisation data, including actions that publish changes to your account.

In plain words
What is it for?
Use it to find deduplicated threat events, inspect their source reports and verification status, check whether an indicator is known to your account, and manage intelligence packages or organisation profiles.
Why use it?
It distinguishes one underlying incident from the many reports about it and shows how well the information is supported.

Skill for Claude CodeCodex

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

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python3 tools/clis/liberty91.py quota.

Good fit Use it to find deduplicated threat events, inspect their source reports and verification status, check whether an indicator is known to your account, and manage intelligence packages or organisation profiles.

Compare 6 skills from other repositories ↓
Install

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.

Clone the repo
git clone --depth 1 https://github.com/Liberty91LTD/cti-skills
agentmods
npx agentmods add skills/liberty91ltd/cti-skills/lookup-liberty91

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 lookup-liberty91

README.md
[![agentmods](https://agentmods.dev/badge/skills/liberty91ltd/cti-skills/lookup-liberty91/github.svg)](https://agentmods.dev/skills/liberty91ltd/cti-skills/lookup-liberty91)
Your own site
<a href="https://agentmods.dev/skills/liberty91ltd/cti-skills/lookup-liberty91"><img src="https://agentmods.dev/badge/skills/liberty91ltd/cti-skills/lookup-liberty91/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 lookup-liberty91

Your own site · 80×15
<a href="https://agentmods.dev/skills/liberty91ltd/cti-skills/lookup-liberty91"><img src="https://agentmods.dev/badge/skills/liberty91ltd/cti-skills/lookup-liberty91.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,274 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00000 $0.05274
Opus 5 $0.00000 $0.02637
Sonnet 5 $0.00000 $0.01055
Haiku 4.5 $0.00000 $0.00527

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

Security

Grade A, and why

lookup-liberty91 scanned grade A with 0 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 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.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/lookup-liberty91/SKILL.md · 249 lines

How it starts

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

lookup-liberty91

Two-way bridge to the Liberty91 platform — the pack's only first-party integration. Where VirusTotal or Shodan answer "what is known about this indicator", Liberty91 answers "what happened, who reported it, how well corroborated is it, and which of my organizations does it touch".

Like /lookup-misp and /lookup-opencti, this skill also writes: it ingests your own reports, queues intelligence packages, and manages organization profiles. Writes publish into your Liberty91 account and are metered — confirm with the user before invoking any write command, and never run one inside an autonomous enrichment loop.

The two-layer model — read this first

Everything else follows from it.

  • A Threat Event is a real-world occurrence: one breach, one exploitation campaign, one leak. Deduplicated, with every source you are entitled to attached.
  • An Event is one report about an occurrence. A breach covered by a vendor write-up, three news articles and a leak-site post is five Events and one Threat Event.
You want Command
What happened, deduplicated, with all its sources threat-events
The individual documents — who published what events

Default to threat-events. Drop to events only when the question is genuinely about documents ("what did vendor X publish this week", "poll my ingested report until enrichment completes"). Every Event carries threat_event_id so you can move between layers.

When to invoke

Read:

  • The user asks what has happened — to a sector, a country, an organization, in a date window (threat-events)
  • An indicator surfaced elsewhere and you want to know whether the platform already holds it (ioc-lookup)
  • An actor / malware family / CVE needs its canonical record, aliases, ATT&CK TTPs, linked occurrences or co-occurring entities (library, entity)
  • A vendor's name for an actor needs resolving to the canonical entry (library threat-actors --alias "…")
  • The user wants their alert rules' matches, or a saved search re-run (alert-matches, run-search)
  • A TIP (MISP, OpenCTI) needs parented STIX for an occurrence (threat-event <id> --section iocs-export)
  • The user asks which of their customer organizations is affected, or about an org's assets/suppliers (threat-event --section detail, orgs, org)

Read the full file on GitHub · 249 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. 12d ago First seen · 249 lines · 0 tokens per session scan A 64605cdfc306

Subscribe to this mod's changes

lookup-liberty91 is a skill published in the GitHub repository Liberty91LTD/cti-skills (18 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,274 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.