Incident Alert Tickets
langfuse/langfuse
Read and record root causes in the Linear incident-alert knowledge base.
Search a large indexed dataset (tickets, logs, incidents, maintenance records, orders, notes, any table or export) and get a few ranked, cited records instead of reading raw data.
$ npx skills add elstongun/leviathan --skill leviathan -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install elstongun/leviathan leviathan --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/elstongun/leviathan.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/leviathan .claude/skills/leviathan && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "leviathan" agent skill from https://github.com/elstongun/leviathan/tree/main/skills/leviathan into .claude/skills/leviathan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "leviathan", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/elstongun/leviathan/tree/main/skills/leviathanType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add elstongun/leviathan --skill leviathan -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install elstongun/leviathan leviathan --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/elstongun/leviathan.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/leviathan .agents/skills/leviathan && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "leviathan" agent skill from https://github.com/elstongun/leviathan/tree/main/skills/leviathan into .agents/skills/leviathan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "leviathan", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add elstongun/leviathan --skill leviathan -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install elstongun/leviathan leviathan --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/elstongun/leviathan.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/leviathan .cursor/skills/leviathan && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "leviathan" agent skill from https://github.com/elstongun/leviathan/tree/main/skills/leviathan into .cursor/skills/leviathan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "leviathan", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/elstongun/leviathan.git --path skills/leviathan--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add elstongun/leviathan --skill leviathan -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install elstongun/leviathan leviathan --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/elstongun/leviathan.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/leviathan .gemini/skills/leviathan && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "leviathan" agent skill from https://github.com/elstongun/leviathan/tree/main/skills/leviathan into .gemini/skills/leviathan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "leviathan", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install elstongun/leviathan leviathanInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add elstongun/leviathan --skill leviathan -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/elstongun/leviathan.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/leviathan .github/skills/leviathan && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "leviathan" agent skill from https://github.com/elstongun/leviathan/tree/main/skills/leviathan into .github/skills/leviathan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "leviathan", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add elstongun/leviathan --skill leviathan -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install elstongun/leviathan leviathan --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/elstongun/leviathan.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/leviathan .opencode/skills/leviathan && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "leviathan" agent skill from https://github.com/elstongun/leviathan/tree/main/skills/leviathan into .opencode/skills/leviathan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "leviathan", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
leviathanSearch a large indexed dataset (tickets, logs, incidents, maintenance records, orders, notes, any table or export) and get a few ranked, cited records instead of reading raw data.
Leviathan is an agent skill from elstongun/leviathan. Search a large indexed dataset (tickets, logs, incidents, maintenance records, orders, notes, any table or export) and get a few ranked, cited records instead of reading raw data. Use when the user asks about past records ("has this happened before", "what fixed it", "what's been going on with <customer/host/machine", "find tickets about ..."), or when data is too large to read or grep. Also use to index a new dataset for search.
Its SKILL.md is about 890 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Deep memory for agents over large datasets. Leviathan is a single static binary that turns your records (JSONL, JSON, CSV/TSV, SQLite, or anything a database CLI can export) into… The licence is Apache-2.0.
Read from SKILL.md and the folder at commit f1070fe. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
psqlFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Leviathan loads about 887 tokens when it runs. Until then it costs about 111 tokens; SKILL.md has 283 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from elstongun/leviathan at commit f1070fe, republished under its Apache-2.0 licence (© elstongun). 283 words, ~887 tokens.
.claude/skills/leviathan/SKILL.md (or your agent's skills folder).The leviathan CLI answers questions from an indexed copy of a dataset. One
call returns a handful of ranked records, usually under 1,000 tokens,
however large the data is. Prefer it to grepping, cat, or paging through
exports: those cost tokens in proportion to the data.
leviathan describeThis shows what one record and one group are called (ticket/customer,
event/host, ...), the fields that are searched, the filter fields with their
common values, the date range, and example calls. Run it once per session
before searching, and use its exact field names in --where.
leviathan search "<words as the user said them>" # ranked, everything
leviathan search -g "<group as the user said it>" "<words>" # within one customer/host/machine
leviathan search "<words>" --where status=open --where priority=high # exact filters (same field twice = either)
leviathan search "<words>" --since 2024-01 --until 2024-06 # date range, inclusive
leviathan search '"exact phrase" -excluded' # quote the whole query for -exclusions
leviathan search -g acme "<words>" --scope others # same problem, every other group
leviathan recent -g "<group>" -n 10 # newest first, no words needed
leviathan resolve "<group name>" # which groups match a name
leviathan get <id> [<id> ...] # complete recordsAdd --json for structured output, -n for more results (max 50), and
--offset to page. The index comes from --index or LEVIATHAN_INDEX
(default ./leviathan.db).
shown N of M. Zero means none found,
not none exist: retry with fewer or different words, or drop a filter.match: line from the text that matched.OTHER <GROUP> come from a different customer, host or
machine than the one asked about. Say so, and keep each result's group
visible.0 ok (including zero hits) · 1 error · 2 bad request (unknown filter
field, bad date) · 3 group unknown or ambiguous. On 3, show the listed
candidates and ask which one the user means. Never guess the group.
leviathan init <files|dir|db.sqlite> -o leviathan.toml # proposes a field mapping, with reasons
# review and edit leviathan.toml (id, title, text, group, date, filters)
leviathan index # reads source.paths from leviathan.toml
leviathan describeIf you already know the schema, write leviathan.toml directly; see
docs/CONFIG.md in the Leviathan repository. Databases are indexed from their
CLI exports through stdin, for example
psql -At -c "SELECT row_to_json(t) FROM t" | leviathan index - -c leviathan.toml.
© elstongun, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/leviathan of elstongun/leviathan.
Open the folder on GitHubat commit f1070fe
Leviathan next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Leviathan this skillelstongun/leviathan | 716 | — | ~887 | Automated safety check: Pass | Apache-2.0 | |
| Incident Alert Ticketslangfuse/langfuse | 36k | — | ~1.6k | Automated safety check: Pass | Custom licence | |
| Implementing Ticketing System For Incidentsmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~4.1k | Automated safety check: Pass | Apache-2.0 | |
| Detecting Golden Ticket Attacks In Kerberos Logsmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Indexabilitythedaviddias/Front-End-Checklist | 74k | — | ~814 | Automated safety check: Pass | MIT | |
| Conducting Cloud Incident Responsemukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~3k | Automated safety check: Pass | Apache-2.0 |
langfuse/langfuse
Read and record root causes in the Linear incident-alert knowledge base.
mukul975/Anthropic-Cybersecurity-Skills
Implements an integrated incident ticketing system connecting SIEM alerts to ServiceNow, Jira, or TheHive for structured incident tracking, SLA management, escalation workflows, and compliance…
mukul975/Anthropic-Cybersecurity-Skills
Detect Golden Ticket attacks in Active Directory using Splunk and KQL queries against domain controller event logs, looking for Kerberos TGT anomalies such as mismatched encryption types, impossible…
thedaviddias/Front-End-Checklist
A skill your agent uses when auditing a site for accidental noindex directives, investigating why important pages are not appearing in Google Search, or reviewing CMS settings that control indexing…
mukul975/Anthropic-Cybersecurity-Skills
Respond to security incidents in AWS, Azure, and GCP via identity-based containment, cloud-native log analysis (CloudTrail, Azure Activity Logs, GCP Audit Logs), resource isolation, and forensic…
davila7/claude-code-templates
Expert SRE incident responder specializing in rapid problem resolution, modern observability, and comprehensive incident management.
elstongun/leviathan
Long-term memory across sessions with the Leviathan memory store.
Search a large indexed dataset (tickets, logs, incidents, maintenance records, orders, notes, any table or export) and get a few ranked, cited records instead of reading raw data. Leviathan is an agent skill from elstongun/leviathan. Search a large indexed dataset (tickets, logs, incidents, maintenance records, orders, notes, any table or export) and get a few ranked, cited records instead of reading raw data.
Leviathan fits situations like: the user asks about past records (has this happened before; whats been going on with <customer/host/machine; find tickets about ...); data is too large to read.
Run `npx skills add elstongun/leviathan --skill leviathan -a claude-code`. Or copy the skill folder (skills/leviathan in elstongun/leviathan) into .claude/skills/leviathan in your project. Claude Code loads it when a task matches its description.
Run `npx skills add elstongun/leviathan --skill leviathan -a codex`. Or copy the skill folder (skills/leviathan in elstongun/leviathan) into .agents/skills/leviathan in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add elstongun/leviathan --skill leviathan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/leviathan, .gemini/skills/leviathan, .github/skills/leviathan and .opencode/skills/leviathan in your project.
Going by SKILL.md and its folder, Leviathan needs the command-line tools its instructions call (psql).
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Leviathan is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 887 tokens (SKILL.md is roughly 3.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Leviathan: Incident Alert Tickets (langfuse/langfuse, 36k stars), Implementing Ticketing System For Incidents (mukul975/Anthropic-Cybersecurity-Skills, 34k stars), Detecting Golden Ticket Attacks In Kerberos Logs (mukul975/Anthropic-Cybersecurity-Skills, 34k stars) and Indexability (thedaviddias/Front-End-Checklist, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
elstongun (a GitHub user) maintains it in elstongun/leviathan, which has 716 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 9, 2026.
Source: elstongun/leviathan on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.