lookup-sentinel

lookup-sentinel is a skill for Claude Code, Codex from Liberty91LTD/cti-skills. It costs 149 tokens per session (3,067 once invoked), scanned A, original, MIT.

A read-only search tool for an organisation’s Microsoft Sentinel security workspace, which stores logs from its systems. It checks whether indicators or attack behaviours appear in the organisation’s own data.

In plain words
What is it for?
Use it to search for suspicious IP addresses, domains, file hashes, URLs, or accounts; run KQL searches; look for behaviours described by MITRE ATT&CK; and inspect available or active log tables.
Why use it?
It helps distinguish a known threat from one that has actually reached your environment. It first checks which log tables contain data, avoiding searches against unavailable or irrelevant sources.

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/sentinel.py check.

Good fit Use it to search for suspicious IP addresses, domains, file hashes, URLs, or accounts; run KQL searches; look for behaviours described by MITRE ATT&CK; and inspect available or active log tables.

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-sentinel

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-sentinel

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/liberty91ltd/cti-skills/lookup-sentinel"><img src="https://agentmods.dev/badge/skills/liberty91ltd/cti-skills/lookup-sentinel.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 149 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,067 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.00149 $0.03067
Opus 5 $0.00075 $0.01533
Sonnet 5 $0.00030 $0.00613
Haiku 4.5 $0.00015 $0.00307

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

Security

Grade A, and why

lookup-sentinel 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-sentinel/SKILL.md · 160 lines

How it starts

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

lookup-sentinel

Query bridge to the organisation's own Microsoft Sentinel (Azure Log Analytics) workspace. Every other lookup in this pack asks the world about an indicator; this one asks your own telemetry: has this indicator been seen in our environment? Is this ATT&CK technique's behaviour present in our logs? It is scoping/exposure-checking, not enrichment — chain it after external lookups have told you what an indicator is, to establish whether it touched you.

Read-only. The CLI can only run queries and list schema — it cannot modify the workspace, close incidents, or create analytics rules.

The cardinal rule: discover before you query

No two Sentinel workspaces have the same tables. Table availability follows deployed connectors (Defender for Endpoint brings Device*, Entra ID brings SigninLogs, AMA/CEF brings CommonSecurityLog, …). A query referencing an absent table fails outright; worse, a hunt written for tables the environment doesn't ingest silently proves nothing.

So, in every session, before generating any hunt KQL:

  1. Run tables (schema-known) and/or ingestion (actually receiving data) once, and reuse the result for the rest of the session.
  2. probe the specific candidate tables for the hunt — schema-known tables can be empty.
  3. Generate KQL only against tables the probe confirmed populated. When a preferred table is missing, walk the fallback ladder (below). When no suitable table exists, report the telemetry gap as a finding — do not fabricate a query, and do not quietly substitute a table that can't answer the question.

When to invoke

  • An investigation skill (/ip-investigation etc.) produced a malicious/suspicious verdict and you need the exposure answer: was it seen here?
  • The user asks to hunt for an ATT&CK technique, actor TTP set, or behaviour ("hunt for T1059 PowerShell abuse", "look for Kerberoasting")
  • The user has IOCs (from a report, a feed, /ioc-enrichment-workflow) and wants them swept across the environment
  • The user asks what telemetry/tables the Sentinel workspace has, or whether a planned detection would even have data
  • The user asks to run or adapt a KQL query against live logs

Read the full file on GitHub · 160 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 · 160 lines · 149 tokens per session scan A bdf22ce1e0af

Subscribe to this mod's changes

lookup-sentinel is a skill published in the GitHub repository Liberty91LTD/cti-skills (18 stars, last pushed 1mo ago), licensed MIT. It adds 149 tokens to every session and 3,067 once invoked, about $0.0007 per session on Opus 5. 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.