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 xalgorix/xalgorix --skill performing-cloud-native-forensics-with-falcogit clone --depth 1 https://github.com/xalgorix/xalgorixWrote 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/xalgorix/xalgorix/performing-cloud-native-forensics-with-falco)<a href="https://agentmods.dev/skills/xalgorix/xalgorix/performing-cloud-native-forensics-with-falco"><img src="https://agentmods.dev/badge/skills/xalgorix/xalgorix/performing-cloud-native-forensics-with-falco/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/xalgorix/xalgorix/performing-cloud-native-forensics-with-falco"><img src="https://agentmods.dev/badge/skills/xalgorix/xalgorix/performing-cloud-native-forensics-with-falco.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 75 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 75 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00077 | $0.00979 |
| Opus 5 | $0.00039 | $0.00490 |
| Sonnet 5 | $0.00015 | $0.00196 |
| Haiku 4.5 | $0.00008 | $0.00098 |
Grade B, and why
performing-cloud-native-forensics-with-falco 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 7d 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.
Reaches for credential filesmediumPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
2. Sensitive file access (/etc/shadow, /etc/passwd) Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Performing Cloud Native Forensics with Falco
When to Use
- When conducting security assessments that involve performing cloud native forensics with falco
- 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
Detection Gaps & Validation
- Rule exceptions are an evasion surface: the
not proc.pname in (docker-entrypo, supervisord)exclusion in the shell rule means an attacker who renames or reparents under those names evades it. Audit everynot ...clause and anchor conditions onproc.exepath/container.imagerather thanproc.pname. - No driver = no events: Falco needs a working kernel module or eBPF probe. If the driver fails to load, Falco runs but sees zero syscalls. Verify the driver loaded with
falco --versionand confirm events flow by triggering a known action. - Syscall drops silently lose alerts: under load the ring buffer overflows. Monitor
falco_n_drops/n_evts(Prometheus metrics or the periodic stats line) - nonzero drops mean missed detections, not a quiet host. - Detection is not prevention, and alerts must leave the node first: an attacker can kill
falcoor wipe/var/log/falco/alerts.json. Ship alerts off-host immediately via the gRPC output / Falcosidekick so evidence survives node compromise. - K8s context needs the audit feed:
container.*/k8s.*fields and the k8s audit rules require the API audit log / metadata plugin wired in; without it, pod/namespace attribution is blank. - How to confirm coverage:
kubectl exec -it <pod> -- shinto a workload and confirm the "Shell Spawned in Container" alert appears inalerts.jsonwith the rightcontainer.name/image; read a sensitive file and confirm the file-access rule fires. - Don't conclude the cluster is clean until the driver is confirmed loaded,
falco_n_dropsis zero over the window, alerts are shown arriving at the off-node sink, and a synthetic shell/file-read actually triggers.
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.
- 7d ago First seen · 88 lines · 77 tokens per session scan B f61ae0126106
performing-cloud-native-forensics-with-falco is a skill published in the GitHub repository xalgorix/xalgorix (972 stars, last pushed yesterday), licensed Apache-2.0. It adds 77 tokens to every session and 979 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 1 finding (reaches for credential files). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
analyzing-docker-container-forensics
Use when investigate compromised Docker containers by analyzing images, layers, volumes, logs, and runtime artifacts to identify malicious activity and evidence. Use when working with analyzing docker container forensics.
analyzing-docker-container-forensics
Investigate compromised Docker containers by analyzing images, layers, volumes, logs, and runtime artifacts to identify malicious activity and evidence.
atmos-helmfile
Helmfile orchestration: sync/apply/destroy/diff, Kubernetes deployments, varfile generation, EKS integration, source management.
atmos-devcontainer
Devcontainer orchestration: start/stop/attach/shell/exec/rebuild, instance management, config handling, VS Code integration.
atmos-container
Atmos container components: components.container, Docker Compose migration, build/run/push/pull/up/down/list/ps/logs/exec, stack-scoped persistent containers, container workflow steps, compositions, and hooks.
atmos-emulator
Atmos emulator components: local AWS/GCP/Azure/Kubernetes/Vault/OpenBao/registry emulators, components.emulator, !emulator, identities, persistence, health checks, and emulator commands.