agentleFS
ferr079ferr079/claude-code-cybersec-skills/skills/aide-fim/SKILL.md

aide-fim

Skill0 starsChanged 32 days agoMITView on GitHub

Set up file integrity monitoring with AIDE: database initialization, rule tuning, scheduled checks, change review. Use when adding FIM to a Linux host.

  • Installs packages

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When deploying or configuring implementing file integrity monitoring with aide capabilities in your environment

    line 16
  2. Distinctive:

    When establishing security controls aligned to compliance requirements

    line 17
  3. Distinctive:

    When building or improving security architecture for this domain

    line 18
  4. Distinctive:

    When conducting security assessments that require this implementation

    line 19

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Implementing File Integrity Monitoring with AIDE

Overview

AIDE (Advanced Intrusion Detection Environment) is a host-based intrusion detection system that monitors file and directory integrity using cryptographic checksums. This skill covers generating AIDE configuration files, initializing baseline databases, running integrity checks, parsing change reports, and setting up automated cron-based monitoring with alerting.

When to Use

  • When deploying or configuring implementing file integrity monitoring with aide capabilities in your environment
  • When establishing security controls aligned to compliance requirements
  • When building or improving security architecture for this domain
  • When conducting security assessments that require this implementation

Prerequisites

  • AIDE installed on target Linux system (apt install aide / yum install aide)
  • Root or sudo access for file system scanning
  • Python 3.8+ with standard library

Steps

  1. Generate AIDE Configuration — Create aide.conf with monitoring rules for critical directories (/etc, /bin, /sbin, /usr/bin, /boot)
  2. Initialize Baseline Database — Run aide --init to create the initial file integrity baseline
  3. Run Integrity Check — Execute aide --check to compare current state against baseline
  4. Parse Change Report — Extract added, removed, and changed files from AIDE output
  5. Configure Automated Monitoring — Generate cron job for scheduled integrity checks
  6. Generate Compliance Report — Produce structured report of all file changes with severity classification

Expected Output

  • AIDE configuration file (aide.conf)
  • Baseline database creation status
  • JSON report of file changes (added/removed/changed) with severity
  • Cron job configuration for automated monitoring

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.