Agent skill

Performing Indicator Lifecycle Management

by mukul975 in mukul975/Anthropic-Cybersecurity-Skills

Tracks IOCs through discovery, enrichment/validation (VirusTotal, Shodan, passive DNS), deployment to SIEM/IDS watchlists, hit-rate and false-positive monitoring, confidence-score decay, and…

Apache-2.0Auto-check passedSecurity

Install Performing Indicator Lifecycle Management

skills CLI
$ npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill performing-indicator-lifecycle-management -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mukul975/Anthropic-Cybersecurity-Skills performing-indicator-lifecycle-management --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/performing-indicator-lifecycle-management .claude/skills/performing-indicator-lifecycle-management && rm -rf skills-src

Use ~/.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/

Facts

Skill name
performing-indicator-lifecycle-management
GitHub stars
34k
Token cost
~1.5k tokens
SKILL.md length
343 words
Files
8 (incl. scripts, references, assets)
Skills in repo
644
Repo updated
First seen
Licence
Apache-2.0

At a glance

Tracks IOCs through discovery, enrichment/validation (VirusTotal, Shodan, passive DNS), deployment to SIEM/IDS watchlists, hit-rate and false-positive monitoring, confidence-score decay, and…

  • Works in 7 steps: Discovery: IOC first identified from… → Validation: IOC verified against… → Enrichment: Additional context added… → …
  • Maintaining a threat intelligence indicator lifecycle process
  • SKILL.md covers Overview, When to Use, Prerequisites and Key Concepts, plus 3 more sections
  • Runs Python scripts from its folder

What it does

Performing Indicator Lifecycle Management is an agent skill from mukul975/Anthropic-Cybersecurity-Skills. Tracks IOCs through discovery, enrichment/validation (VirusTotal, Shodan, passive DNS), deployment to SIEM/IDS watchlists, hit-rate and false-positive monitoring, confidence-score decay, and automated expiration using MISP/OpenCTI and STIX. Use when building or maintaining a threat intelligence indicator lifecycle process, aging out stale IOCs, or reducing analyst fatigue from low-quality indicators.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including scripts, reference files and assets (for example `assets/template.md`, `references/api-reference.md` and `references/standards.md`).

It sits in Security, covering OSINT and Security operations. The repository describes itself as: 817 structured cybersecurity skills for AI agents · Mapped to 6 frameworks: MITRE ATT&CK, NIST CSF 2.0, MITRE ATLAS, D3FEND, NIST AI RMF & MITRE F3 (Fight Fraud) · agentskills.io…. The licence is Apache-2.0.

When your agent uses it

  • Maintaining a threat intelligence indicator lifecycle process
  • Aging out stale IOCs
  • Reducing analyst fatigue from low-quality indicators

Example prompts

  • “Use the performing-indicator-lifecycle-management skill to track IOCs through discovery, enrichment/validation (VirusTotal, Shodan, passive DNS)…”
  • “/performing-indicator-lifecycle-management”

Requirements

  • Python 3

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Discovery: IOC first identified from threat intelligence, malware analysis, or incident response
  2. Validation: IOC verified against enrichment sources (VirusTotal, Shodan)
  3. Enrichment: Additional context added (WHOIS, passive DNS, threat actor attribution)
  4. Deployment: IOC pushed to detection systems (SIEM, IDS, firewall)
  5. Monitoring: Track hit rates, false positive rates, detection efficacy
  6. Review: Periodic assessment of IOC relevance and accuracy
  7. Retirement: IOC expired or removed based on aging policy

What it can do on your machine

Read from SKILL.md and the folder at commit 54a7988. It shows what the files ask for, not the result of running them.

  • Tool permissions

    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.

  • Runs code

    Ships 2 files in scripts/ (Python), which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • misp-project.org
    • docs.oasis-open.org
    • first.org

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Performing Indicator Lifecycle Management loads about 1.5k tokens when it runs, and up to ~2.5k if it reads all its reference files. Until then it costs about 111 tokens; SKILL.md has 343 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~111
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.5k

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.

Safety

Auto-check passed

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); the scripts in this folder are not scanned.

SKILL.md

The full file from mukul975/Anthropic-Cybersecurity-Skills at commit 54a7988, republished under its Apache-2.0 licence (© mukul975). 343 words, ~1,461 tokens.

Download SKILL.mdSave it as .claude/skills/performing-indicator-lifecycle-management/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.
name
performing-indicator-lifecycle-management
description
Tracks IOCs through discovery, enrichment/validation (VirusTotal, Shodan, passive DNS), deployment to SIEM/IDS watchlists, hit-rate and false-positive monitoring, confidence-score decay, and automated expiration using MISP/OpenCTI and STIX. Use when building or maintaining a threat intelligence indicator lifecycle process, aging out stale IOCs, or reducing analyst fatigue from low-quality indicators.
domain
cybersecurity
subdomain
threat-intelligence
tags
threat-intelligence, cti, ioc, mitre-attack, stix, indicator-lifecycle, ioc-management
version
1.0
author
mahipal
license
Apache-2.0
nist_csf
ID.RA-01, ID.RA-05, DE.CM-01, DE.AE-02
mitre_attack
T1591, T1592, T1593, T1589

Performing Indicator Lifecycle Management

Overview

Indicator lifecycle management tracks IOCs from initial discovery through validation, enrichment, deployment, monitoring, and eventual retirement. This skill covers implementing systematic processes for IOC quality assessment, aging policies, confidence scoring decay, false positive tracking, hit-rate monitoring, and automated expiration to maintain a high-quality, actionable indicator database that minimizes analyst fatigue and maximizes detection efficacy.

When to Use

  • When conducting security assessments that involve performing indicator lifecycle management
  • When following incident response procedures for related security events
  • When performing scheduled security testing or auditing activities
  • When validating security controls through hands-on testing

Prerequisites

  • Python 3.9+ with pymisp, requests, stix2 libraries
  • MISP or OpenCTI instance for indicator storage
  • SIEM with IOC watchlist capabilities (Splunk, Elastic)
  • Understanding of IOC types, confidence scoring, and TLP classifications

Key Concepts

Indicator Lifecycle Phases
  1. Discovery: IOC first identified from threat intelligence, malware analysis, or incident response
  2. Validation: IOC verified against enrichment sources (VirusTotal, Shodan)
  3. Enrichment: Additional context added (WHOIS, passive DNS, threat actor attribution)
  4. Deployment: IOC pushed to detection systems (SIEM, IDS, firewall)
  5. Monitoring: Track hit rates, false positive rates, detection efficacy
  6. Review: Periodic assessment of IOC relevance and accuracy
  7. Retirement: IOC expired or removed based on aging policy
Confidence Decay

Indicator confidence decreases over time as adversaries rotate infrastructure. A time-based decay function reduces confidence scores automatically, ensuring old indicators do not generate excessive alerts. Typical half-life: IP addresses (30 days), domains (90 days), file hashes (365 days).

Quality Metrics
  • Hit Rate: Percentage of deployed IOCs generating true positive alerts
  • False Positive Rate: Percentage of IOC alerts that are benign
  • Coverage: Percentage of known threat techniques with IOC coverage
  • Freshness: Average age of active indicators in the database

Workflow

Step 1: Implement IOC Lifecycle State Machine
python
from datetime import datetime, timedelta
from enum import Enum

class IOCState(Enum):
    DISCOVERED = "discovered"
    VALIDATED = "validated"
    ENRICHED = "enriched"
    DEPLOYED = "deployed"
    MONITORING = "monitoring"
    UNDER_REVIEW = "under_review"
    RETIRED = "retired"

class IOCLifecycle:
    def __init__(self, ioc_type, value, source, initial_confidence=50):
        self.ioc_type = ioc_type
        self.value = value
        self.source = source
        self.confidence = initial_confidence
        self.state = IOCState.DISCOVERED
        self.created = datetime.utcnow()
        self.last_updated = datetime.utcnow()
        self.last_seen = None
        self.hit_count = 0
        self.false_positive_count = 0
        self.history = [{"state": "discovered", "timestamp": self.created.isoformat()}]

    def transition(self, new_state: IOCState, reason=""):
        self.state = new_state
        self.last_updated = datetime.utcnow()
        self.history.append({
            "state": new_state.value,
            "timestamp": self.last_updated.isoformat(),
            "reason": reason,
        })

    def apply_decay(self):
        """Apply confidence decay based on IOC type half-life."""
        half_lives = {"ip": 30, "domain": 90, "hash": 365, "url": 60}
        half_life = half_lives.get(self.ioc_type, 90)
        age_days = (datetime.utcnow() - self.created).days
        decay_factor = 0.5 ** (age_days / half_life)
        self.confidence = max(0, int(self.confidence * decay_factor))

    def record_hit(self, is_true_positive=True):
        self.hit_count += 1
        self.last_seen = datetime.utcnow()
        if not is_true_positive:
            self.false_positive_count += 1
            if self.false_positive_count > 3:
                self.transition(IOCState.UNDER_REVIEW, "Excessive false positives")

    def should_retire(self):
        max_ages = {"ip": 90, "domain": 180, "hash": 730, "url": 120}
        max_age = max_ages.get(self.ioc_type, 180)
        age_days = (datetime.utcnow() - self.created).days
        return age_days > max_age and self.hit_count == 0

Validation Criteria

  • IOC lifecycle state machine transitions correctly between phases
  • Confidence decay reduces scores based on IOC type half-life
  • Hit rate and false positive tracking functional
  • Aging policy automatically flags indicators for review/retirement
  • Quality metrics dashboard shows IOC database health

References

© mukul975, 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

Files

SKILL.md and 7 other files (scripts, references, assets) in skills/performing-indicator-lifecycle-management of mukul975/Anthropic-Cybersecurity-Skills.

  • SKILL.md
  • LICENSE
  • assets/template.md
  • references/api-reference.md
  • references/standards.md
  • references/workflows.md
  • scripts/agent.py
  • scripts/process.py

Open the folder on GitHubat commit 54a7988

Compare with similar skills

Performing Indicator Lifecycle Management 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.

Performing Indicator Lifecycle Management compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Performing Indicator Lifecycle Management this skillmukul975/Anthropic-Cybersecurity-Skills34k—~1.5kAutomated safety check: PassApache-2.0
Threat Intelligence OSINTzhaoxuya520/reverse-skill40k1 repos~1kAutomated safety check: PassMIT
Enrich Iocdandye/ai-runbooks127—~702Automated safety check: PassApache-2.0
Secops Detection Engineeringgoogle/skills21k—~4.8kAutomated safety check: PassApache-2.0
Malware Analystaiskillstore/marketplace4306 repos~1.7kAutomated safety check: PassNone
Detection Engineering Coverage Evaluationgoogle/skills21k—~3.3kAutomated safety check: PassApache-2.0

Similar skills

  • Threat Intelligence OSINT

    zhaoxuya520/reverse-skill

    Enriches IOCs, campaigns, impersonation and scams from public sources, including bounded X search through Xquik, and checks each lead against independent evidence.

    40k GitHub starsUsed in 1 repo~1k tokens
    SecurityAuto-check passed
  • Enrich Ioc

    dandye/ai-runbooks

    Enrich an IOC (IP, domain, hash, URL) with threat intelligence.

    127 GitHub stars~702 tokensUpdated 1 mo ago
    SecurityAuto-check passed
  • Official

    Author, validate, test, and deploy YARA-L 2.0 detection rules and evaluate end-to-end detection coverage gaps in Google SecOps.

    21k GitHub stars~4.8k tokensUpdated today
    SecurityAuto-check passed
  • Malware Analyst

    aiskillstore/marketplace

    Expert malware analyst specializing in defensive malware research, threat intelligence, and incident response.

    430 GitHub starsUsed in 6 repos~1.7k tokens
    SecurityAuto-check passed
  • Automates the end-to-end detection engineering workflow in Google SecOps using MCP tools.

    21k GitHub stars~3.3k tokensUpdated today
    SecurityAuto-check passed
  • Hunt Threat

    dandye/ai-runbooks

    Conduct proactive, hypothesis-driven threat hunting. An agent skill from dandye/ai-runbooks.

    127 GitHub stars~1.4k tokensUpdated 1 mo ago
    SecurityAuto-check passed

More from mukul975/Anthropic-Cybersecurity-Skills

All 644 skills in this repo
  • Campaign Attribution Evidence Analysis

    mukul975/Anthropic-Cybersecurity-Skills

    Weighs infrastructure, TTP, malware code and timing evidence with the Diamond Model and competing hypotheses to reach a confidence-rated attribution.

    34k GitHub stars~2.3k tokensUpdated 1 mo ago
    Auto-check passed
  • Go Malware Analysis in Ghidra

    mukul975/Anthropic-Cybersecurity-Skills

    Walks through reverse engineering Go-compiled malware in Ghidra: parsing buildinfo and pclntab, recovering stripped function names and extracting dependencies.

    34k GitHub stars~2.8k tokensUpdated 1 mo ago
    Auto-check passed
  • LNK and Jump List Forensics

    mukul975/Anthropic-Cybersecurity-Skills

    Guides forensic analysis of Windows LNK shortcut files and Jump Lists with LECmd, JLECmd and manual parsing to show file access and program execution.

    34k GitHub stars~2.8k tokensUpdated 1 mo ago
    Auto-check passed
  • Malware Persistence Analysis with Autoruns

    mukul975/Anthropic-Cybersecurity-Skills

    Hunts Windows malware persistence with Sysinternals Autoruns, covering run keys, services, scheduled tasks and drivers, with baseline comparison.

    34k GitHub stars~1.2k tokensUpdated 1 mo ago
    Auto-check passed
  • NTFS MFT Deleted File Recovery

    mukul975/Anthropic-Cybersecurity-Skills

    Guides a Windows forensic examination of the NTFS Master File Table to recover deleted-file evidence, build timelines and spot timestomping.

    34k GitHub stars~2.7k tokensUpdated 1 mo ago
    Auto-check passed
  • Network Covert Channel Analysis

    mukul975/Anthropic-Cybersecurity-Skills

    Detects DNS tunneling, ICMP exfiltration and HTTP-based covert channels in packet captures and DNS logs when hunting for hidden command-and-control traffic.

    34k GitHub stars~2k tokensUpdated 1 mo ago
    Auto-check passed

Categories

Questions about Performing Indicator Lifecycle Management

What does Performing Indicator Lifecycle Management do?

Tracks IOCs through discovery, enrichment/validation (VirusTotal, Shodan, passive DNS), deployment to SIEM/IDS watchlists, hit-rate and false-positive monitoring, confidence-score decay, and…. Performing Indicator Lifecycle Management is an agent skill from mukul975/Anthropic-Cybersecurity-Skills. Tracks IOCs through discovery, enrichment/validation (VirusTotal, Shodan, passive DNS), deployment to SIEM/IDS watchlists, hit-rate and false-positive monitoring, confidence-score decay, and automated expiration using MISP/OpenCTI and STIX.

When should I use Performing Indicator Lifecycle Management?

Performing Indicator Lifecycle Management fits situations like: maintaining a threat intelligence indicator lifecycle process; aging out stale IOCs; reducing analyst fatigue from low-quality indicators.

How do I install Performing Indicator Lifecycle Management in Claude Code?

Run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill performing-indicator-lifecycle-management -a claude-code`. Or copy the skill folder (skills/performing-indicator-lifecycle-management in mukul975/Anthropic-Cybersecurity-Skills) into .claude/skills/performing-indicator-lifecycle-management in your project. Claude Code loads it when a task matches its description.

How do I install Performing Indicator Lifecycle Management in Codex?

Run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill performing-indicator-lifecycle-management -a codex`. Or copy the skill folder (skills/performing-indicator-lifecycle-management in mukul975/Anthropic-Cybersecurity-Skills) into .agents/skills/performing-indicator-lifecycle-management in your project. Codex loads it when a task matches its description.

Can I use Performing Indicator Lifecycle Management in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill performing-indicator-lifecycle-management -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/performing-indicator-lifecycle-management, .gemini/skills/performing-indicator-lifecycle-management, .github/skills/performing-indicator-lifecycle-management and .opencode/skills/performing-indicator-lifecycle-management in your project.

What does Performing Indicator Lifecycle Management need to run?

Going by SKILL.md and its folder, Performing Indicator Lifecycle Management needs Python for the scripts in its folder. Our summary lists: Python 3.

Does Performing Indicator Lifecycle Management access the network?

SKILL.md names 3 domains. As links in the text: misp-project.org, docs.oasis-open.org and first.org. This is read from the text; nothing was executed.

Is Performing Indicator Lifecycle Management safe to install?

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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Performing Indicator Lifecycle Management use?

Performing Indicator Lifecycle Management is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Performing Indicator Lifecycle Management use?

About 1.5k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1k tokens, read only when the agent opens those files.

What are the alternatives to Performing Indicator Lifecycle Management?

Skills that share tags, products or a category with Performing Indicator Lifecycle Management: Threat Intelligence OSINT (zhaoxuya520/reverse-skill, 40k stars), Enrich Ioc (dandye/ai-runbooks, 127 stars), Secops Detection Engineering (google/skills, 21k stars) and Malware Analyst (aiskillstore/marketplace, 430 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Performing Indicator Lifecycle Management?

mukul975 (a GitHub user) maintains it in mukul975/Anthropic-Cybersecurity-Skills, which has 33,993 GitHub stars. The repository holds 644 skills in this directory. The repository was last updated on August 31, 2026.

Source: mukul975/Anthropic-Cybersecurity-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.