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 Eliyce/paqad-ai --skill logging-monitoring-reviewgit clone --depth 1 https://github.com/Eliyce/paqad-aiWrote 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/eliyce/paqad-ai/logging-monitoring-review)<a href="https://agentmods.dev/skills/eliyce/paqad-ai/logging-monitoring-review"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/logging-monitoring-review/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/eliyce/paqad-ai/logging-monitoring-review"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/logging-monitoring-review.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.00030 | $0.00905 |
| Opus 5 | $0.00015 | $0.00452 |
| Sonnet 5 | $0.00006 | $0.00181 |
| Haiku 4.5 | $0.00003 | $0.00090 |
Grade A, and why
logging-monitoring-review 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 9d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What It Does
Reviews whether the application logs security-relevant events with sufficient context for incident detection and forensic analysis — and whether the logging itself is secure (no sensitive data in logs, no log injection surfaces). Maps to OWASP 2025 A09 — Security Logging and Alerting Failures.
Use This When
Use this when module docs describe authentication, authorization decisions, financial transactions, data exports, admin operations, or any high-value action that must be auditable for compliance or incident response.
Inputs
- Read module docs to identify which operations are high-value and must be audited.
- Read
references/logging-gaps-checklist.mdbefore evaluating each area. - Read logging configuration files (Laravel
config/logging.php, DjangoLOGGINGdict, Express winston/pino config) and test files.
Procedure
-
Authentication event logging: Check whether failed and successful login attempts are logged with IP address, timestamp, and username (not password). Check that password changes, MFA enrollment/removal, and session invalidations are also logged.
-
Authorization event logging: Check whether access denials (403 responses) are logged with the requested resource and caller identity. Check that privilege escalation attempts are detected and logged.
-
Data modification logging: For each create/update/delete operation on sensitive models (users, payments, permissions, audit records themselves), verify an audit log entry is written with actor identity. Financial transaction audit trails must be append-only and tamper-resistant.
-
Log integrity: Check whether logs can be tampered with by an application-level user (e.g., a normal user can delete their own activity logs). Check whether logs are stored on a separate system from the application server.
-
Log injection: Check whether user-supplied input is written directly into log strings without sanitization. An attacker controlling a username or message field can:
- Insert fake log entries by embedding newlines (
\n) in the input - Inject ANSI escape codes to corrupt terminal-based log viewers
- Corrupt structured JSON log format by embedding
}or"characters
- Insert fake log entries by embedding newlines (
What ships with it
6 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.
- 9d ago First seen · 75 lines · 30 tokens per session scan A 42e3352a2df6
logging-monitoring-review is a skill published in the GitHub repository Eliyce/paqad-ai (8 stars, last pushed yesterday), licensed MIT. It adds 30 tokens to every session and 905 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-09-03.
Other skills, from other repositories
pr-writing-review
Extract and analyze writing improvements from GitHub PR review comments. Use when asked to show review feedback, style changes, or editorial improvements from a GitHub pull request URL. Handles both explicit suggestions and plain text feedback. Produces structured output comparing original phrasing with reviewer…
session-investigator
Investigate fast-agent session and history files to diagnose issues. Use when a session ended unexpectedly, when debugging tool loops, when correlating sub-agent traces with main sessions, or when analyzing conversation flow and timing. Covers session.json metadata, history JSON format, message structure, tool…
auto-go
A command that implements code from a SPEC, a document describing the required behavior and work.
auto-plan
A code-planning skill that examines a codebase and creates a detailed specification, implementation plan, and acceptance criteria. It can organize requirements using EARS, a structured way to describe how software should behave in different situations.
agent-pipeline
Multi-agent pipeline orchestration skill.
adaptive-quality
Per-task execution profile selection based on complexity in Balanced quality mode.