rsyslog modules.plugins.instructions.md

Repository instructions for rsyslog, a software project described here as a log collection and transformation engine. No detailed instructions are included.

In plain words
What is it for?
It may point agents to project guidance, but its concrete uses cannot be determined from the available text.
Why use it?
The entry does not provide enough information to explain a specific problem it solves.

Instructions file for GitHub Copilot

Install

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.

agentmods
npx agentmods add instructions/rsyslog/rsyslog/modules.plugins
Clone the repo
git clone --depth 1 https://github.com/rsyslog/rsyslog

Made for: GitHub Copilot.

Per session 152 This file is loaded in full into every session.
When invoked 152 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00152 $0.00152
Opus 5 $0.00076 $0.00076
Sonnet 5 $0.00030 $0.00030
Haiku 4.5 $0.00015 $0.00015

Measured 2d ago against content hash 94e385a6f90f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

rsyslog modules.plugins.instructions.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 2d 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.

.github/instructions/modules.plugins.instructions.md · 20 lines

The source is not reproduced here

Licensed LGPL-3.0

The repository is licensed LGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

Changes

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.

  1. 2d ago First seen · 20 lines · 152 tokens per session scan A 94e385a6f90f

Subscribe to this mod's changes

rsyslog modules.plugins.instructions.md is an instructions file published in the GitHub repository rsyslog/rsyslog (2,330 stars, last pushed 2d ago), licensed LGPL-3.0. It adds 152 tokens to every session, about $0.0008 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.