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 agentmods add instructions/sous-chefs/ossec/agents-mdgit clone --depth 1 https://github.com/sous-chefs/ossecWhat 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 | $0.02235 | $0.02235 |
| Opus 5 | $0.01118 | $0.01118 |
| Sonnet 5 | $0.00447 | $0.00447 |
| Haiku 4.5 | $0.00224 | $0.00224 |
Grade A, and why
ossec AGENTS.md scanned grade A with 0 findings 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 3d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Cookbook Purpose
Provides custom resources for managing OSSEC HIDS packages and configuration
Agent Findings
- This cookbook is in an incremental modernization pass. Preserve existing public recipes and attributes unless a later full migration is explicitly selected.
- Dependency management should use
Policyfile.rb; do not reintroduce Berkshelf.
Known Limitations
This cookbook currently installs OSSEC HIDS packages from the Atomicorp archive paths used in the legacy cookbook, not from a first-party Chef workflow. Current upstream OSSEC documentation also supports source builds, and that source-install path is the safest fallback when packaged artifacts are missing or lagging.
Package Availability
APT (Debian/Ubuntu)
- Repository base URL used by the cookbook:
https://updates.atomicorp.com/channels/atomic/<platform> - Current cookbook GPG key:
https://www.atomicorp.com/RPM-GPG-KEY.atomicorp.txt - Current cookbook layout logic:
- Ubuntu 20.04+ and Debian 11+ use
codename/<arch>/ - older releases use the legacy
codename+mainlayout
- Ubuntu 20.04+ and Debian 11+ use
Verified Atomicorp archive trees on 2026-04-15:
- Ubuntu trees present:
xenial,bionic,focal,jammy,noble - Debian trees present:
buster,bullseye,bookworm,trixie
Verified package artifacts on 2026-04-15:
- Ubuntu 20.04
focal: OSSEC 4.0.0 agent/server packages observed foramd64andarm64 - Ubuntu 22.04
jammy: OSSEC 4.0.0 agent/server packages observed foramd64andarm64 - Ubuntu 24.04
noble: OSSEC 4.0.0 agent/server packages observed foramd64andarm64
Vendor support documentation currently lists:
- Debian 11 / 12 / 13:
x86_64,aarch64/ARM64 - Ubuntu 20 / 22 / 24:
x86_64,aarch64/ARM64
Practical limitation:
- The archive still exposes older distro trees, but those should not be treated as support commitments
- Ubuntu 18.04 and 20.04 remain available in the archive, but 18.04 is ESM-only and 20.04 standard support ended on 2025-05-31
- Debian 13 package metadata currently requires a compatibility fallback in this
cookbook: the Atomicorp signing path is not accepted by current apt policy, so
the cookbook enables
trusted=yesfor Debian 13 only to keep installs working
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.
- 3d ago First seen · 198 lines · 2,235 tokens per session scan A b36d23f5a105
ossec AGENTS.md is an instructions file published in the GitHub repository sous-chefs/ossec (46 stars, last pushed 20d ago), licensed Apache-2.0. It adds 2,235 tokens to every session, about $0.0112 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
postfix copilot-instructions.md
Instructions for sous-chefs/postfix, covering copilot instructions for sous chefs cookbooks, repository overview, project structure, build and test system and environment setup.
postfix AGENTS.md
Instructions for sous-chefs/postfix: This cookbook manages Postfix through operating system packages and service/configuration files. It does not build Postfix from source.
varnish AGENTS.md
Instructions for sous-chefs/varnish, covering agents.md, agent guidance, package availability, apt (debian/ubuntu) and dnf/yum (rhel family).
nfs AGENTS.md
Instructions for sous-chefs/nfs, covering agent notes, package availability, apt (debian/ubuntu), dnf/yum (rhel family, fedora, amazon linux) and zypper (suse).
emacs AGENTS.md
Instructions for sous-chefs/emacs, covering agents.md, cookbook purpose, agent findings, known limitations and package availability.
beyondcompare AGENTS.md
Instructions for sous-chefs/beyondcompare, covering agents.md, cookbook purpose, agent findings, known limitations and package availability.