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 skills/redhatproductsecurity/prodsec-skills/loggingnpx skills add RedHatProductSecurity/prodsec-skills --skill logginggit clone --depth 1 https://github.com/RedHatProductSecurity/prodsec-skillsWrote 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/redhatproductsecurity/prodsec-skills/logging)<a href="https://agentmods.dev/skills/redhatproductsecurity/prodsec-skills/logging"><img src="https://agentmods.dev/badge/skills/redhatproductsecurity/prodsec-skills/logging.svg" alt="Measured on agentmods" 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.00038 | $0.00776 |
| Opus 5 | $0.00019 | $0.00388 |
| Sonnet 5 | $0.00008 | $0.00155 |
| Haiku 4.5 | $0.00004 | $0.00078 |
Grade A, and why
logging 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 6d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Logging for External Data Source Access
Security Requirement
If the data contained and served by external data sources is sensitive, accesses to them MUST be logged. The product SHOULD have the functionality to send these events to an external logging facility using industry standards.
What to Log
| Event | Details to Capture |
|---|---|
| Data access | Who accessed what data, when, from where |
| Data modification | Who modified what data, what changed |
| Access denial | Failed access attempts (authentication or authorization failures) |
| Bulk operations | Large data exports or queries |
| Connection events | Connection establishment and teardown |
| Schema changes | Structural changes to data sources |
Logging Requirements
| Requirement | Details |
|---|---|
| External logging facility | Logs must be sendable to an external SIEM or logging platform |
| Industry standard protocols | Use syslog, OTLP, Fluentd, or equivalent |
| Structured format | JSON with consistent field names |
| Principal identity | Every log entry includes the authenticated principal |
| Configurable | Customers must be able to configure the external log destination |
| Non-repudiation | Logs should not be modifiable by the application |
Log Safety
| Rule | Rationale |
|---|---|
| No secrets in logs | Credentials, API keys, and session tokens must never appear in log output |
| No PII in logs | Personally identifiable information creates compliance and privacy risks |
| No session identifiers | Session IDs in logs can enable session hijacking |
| Log injection prevention | Untrusted input in logs can exploit log viewers (XSS, RCE in parsers); sanitize all values before logging |
| Trusted system logging | Logging controls must run on a trusted system (server-side), not client-side |
What to Log
Log both success and failure of security events:
- Authentication attempts, especially failures
- Access control failures
- Tampering events (unexpected state changes)
- Invalid or expired session token usage
- System exceptions
- Administrative functions and security configuration changes
- Bulk data operations and large exports
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.
- 6d ago First seen · 81 lines · 38 tokens per session scan A 255c0a2dccca
logging is a skill published in the GitHub repository RedHatProductSecurity/prodsec-skills (52 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 38 tokens to every session and 776 once invoked, about $0.0002 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…