Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add 26zl/cybersec-toolkit --skill analyzing-persistence-mechanisms-in-linuxgit clone --depth 1 https://github.com/26zl/cybersec-toolkitWrote 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.
[](https://agentmods.dev/skills/26zl/cybersec-toolkit/analyzing-persistence-mechanisms-in-linux)<a href="https://agentmods.dev/skills/26zl/cybersec-toolkit/analyzing-persistence-mechanisms-in-linux"><img src="https://agentmods.dev/badge/skills/26zl/cybersec-toolkit/analyzing-persistence-mechanisms-in-linux/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.
<a href="https://agentmods.dev/skills/26zl/cybersec-toolkit/analyzing-persistence-mechanisms-in-linux"><img src="https://agentmods.dev/badge/skills/26zl/cybersec-toolkit/analyzing-persistence-mechanisms-in-linux.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00050 | $0.00707 |
| Opus 5 | $0.00025 | $0.00353 |
| Sonnet 5 | $0.00010 | $0.00141 |
| Haiku 4.5 | $0.00005 | $0.00071 |
Grade B, and why
analyzing-persistence-mechanisms-in-linux scanned grade B with 1 finding 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 10d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- Root or sudo access on target Linux system (or forensic image) This is a copy
86% identical to analyzing-persistence-mechanisms-in-linux — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyzing Persistence Mechanisms in Linux
Overview
Adversaries establish persistence on Linux systems through crontab jobs, systemd service/timer units, LD_PRELOAD library injection, shell profile modifications (.bashrc, .profile), SSH authorized_keys backdoors, and init script manipulation. This skill scans for all known persistence vectors, checks file timestamps and integrity, and correlates findings with auditd logs to build a timeline of persistence installation.
When to Use
- When investigating security incidents that require analyzing persistence mechanisms in linux
- When building detection rules or threat hunting queries for this domain
- When SOC analysts need structured procedures for this analysis type
- When validating security monitoring coverage for related attack techniques
Prerequisites
- Root or sudo access on target Linux system (or forensic image)
- auditd configured with file watch rules on persistence paths
- Python 3.8+ with standard library (os, subprocess, json)
- Optional: OSSEC/Wazuh agent for file integrity monitoring alerts
Steps
- Scan Crontab Entries — Enumerate all user crontabs, /etc/cron.d/, /etc/cron.daily/, and anacron jobs for suspicious commands
- Audit Systemd Units — Check /etc/systemd/system/ and ~/.config/systemd/user/ for non-package-managed service and timer units
- Detect LD_PRELOAD Hijacking — Check /etc/ld.so.preload and LD_PRELOAD environment variable for injected shared libraries
- Inspect Shell Profiles — Scan .bashrc, .bash_profile, .profile, /etc/profile.d/ for injected commands or reverse shells
- Check SSH Authorized Keys — Audit all authorized_keys files for unauthorized public keys with command restrictions
- Correlate Auditd Logs — Search auditd logs for file modification events on persistence paths to build an installation timeline
- Generate Persistence Report — Produce a risk-scored report of all discovered persistence mechanisms
Expected Output
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 75 lines · 50 tokens per session scan B 7d4dcb2126ec
analyzing-persistence-mechanisms-in-linux is a skill published in the GitHub repository 26zl/cybersec-toolkit (52 stars, last pushed today), licensed MIT. It adds 50 tokens to every session and 707 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). It is 86% identical to analyzing-persistence-mechanisms-in-linux, differing in 4 lines, and is treated as a copy.
Other skills, from other repositories
analyzing-persistence-mechanisms-in-linux
Scan Linux systems for persistence mechanisms including crontab/systemd entries, LDPRELOAD injection, shell profile modifications (.bashrc, .profile), and SSH authorizedkeys backdoors, then correlate findings with auditd logs into an installation timeline. Use during incident response or threat hunting to detect or…
analyzing-persistence-mechanisms-in-linux
A guide to finding ways attackers can make Linux programs or accounts start again automatically after a restart or login. It examines scheduled tasks, system services, shell startup files, injected libraries, and SSH keys.
analyzing-persistence-mechanisms-in-linux
Detect and analyze Linux persistence mechanisms including crontab entries, systemd service units, LDPRELOAD hijacking, bashrc modifications, and authorizedkeys backdoors using auditd and file integrity monitoring.
analyzing-persistence-mechanisms-in-linux
Scan Linux systems for persistence mechanisms including crontab/systemd entries, LDPRELOAD injection, shell profile modifications (.bashrc, .profile), and SSH authorizedkeys backdoors, then correlate findings with auditd logs into an installation timeline. Use during incident response or threat hunting to detect or…
analyzing-persistence-mechanisms-in-linux
Detect and analyze Linux persistence mechanisms including crontab entries, systemd service units, LDPRELOAD hijacking, bashrc modifications, and authorizedkeys backdoors using auditd and file integrity monitoring.
analyzing-persistence-mechanisms-in-linux
Detect and analyze Linux persistence mechanisms including crontab entries, systemd service units, LDPRELOAD hijacking, bashrc modifications, and authorizedkeys backdoors using auditd and file integrity monitoring.