auditing-security-logging-completeness

auditing-security-logging-completeness is a skill for Claude Code from UnboundCompute/security-agent-skills. It costs 178 tokens per session (1,966 once invoked), scanned A, original, MIT.

A security audit of an application's logs, checking whether important security actions are recorded and whether log entries can expose secrets, personal data, or misleading text.

In plain words
What is it for?
Use it to check logging for sign-ins, access denials, permission changes, and access to sensitive data.
Why use it?
Missing records make investigations incomplete, while unsafe records can leak information or let attackers forge an audit trail.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the security-agent-skills plugin — 174 skills shipped together

Good fit Use it to check logging for sign-ins, access denials, permission changes, and access to sensitive data.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/unboundcompute/security-agent-skills/auditing-security-logging-completeness
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.

Any agent
npx skills add UnboundCompute/security-agent-skills --skill auditing-security-logging-completeness
Clone the repo
git clone --depth 1 https://github.com/UnboundCompute/security-agent-skills

Made for: Claude Code.

Or install security-agent-skills, the plugin that ships this one along with the rest of its 174 skills.

Wrote 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.

agentmods badge for auditing-security-logging-completeness

README.md
[![agentmods](https://agentmods.dev/badge/skills/unboundcompute/security-agent-skills/auditing-security-logging-completeness/github.svg)](https://agentmods.dev/skills/unboundcompute/security-agent-skills/auditing-security-logging-completeness)
Your own site
<a href="https://agentmods.dev/skills/unboundcompute/security-agent-skills/auditing-security-logging-completeness"><img src="https://agentmods.dev/badge/skills/unboundcompute/security-agent-skills/auditing-security-logging-completeness/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.

agentmods 80×15 button for auditing-security-logging-completeness

Your own site · 80×15
<a href="https://agentmods.dev/skills/unboundcompute/security-agent-skills/auditing-security-logging-completeness"><img src="https://agentmods.dev/badge/skills/unboundcompute/security-agent-skills/auditing-security-logging-completeness.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 178 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,966 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original 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.1 $0.00178 $0.01966
Opus 5 $0.00089 $0.00983
Sonnet 5 $0.00036 $0.00393
Haiku 4.5 $0.00018 $0.00197

Measured 8d ago against content hash d9525b6c0ae9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

auditing-security-logging-completeness 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 8d 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.

skills/auditing-security-logging-completeness/SKILL.md · 135 lines

How it starts

The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Auditing security-logging completeness: whether the record exists when you need it

Detection and forensics can only work with signals the application actually emits. A gate that denies access but writes nothing is invisible after the fact; a privilege change with no audit entry cannot be reconstructed; a log that quietly captures a token or an email address becomes a disclosure store; a log that accepts raw newlines can be forged to hide a trail. This audit is the mirror of the usual hunt: the source is a security-relevant action that must reach an audit sink, or a secret that must never reach a log sink, and the finding is a record that is missing, insufficient, leaking, or forgeable. You do it by enumerating the decisions that matter and following each to whether, and how, it is recorded.

When to use

  • You are assessing whether an application produces the security events an investigation would need.
  • Authorization denials, authentication, privilege changes, or sensitive reads may go unrecorded.
  • Logs may capture secrets or personal data, or accept unneutralized untrusted input.

Scope check

Audit logging and log contents only in systems you own or are authorized to assess, and treat any secrets or personal data you find in logs as sensitive: report their presence, do not copy them out. If you can't name the authorization, stop.

The loop

  1. Enumerate the security decisions that should be recorded. Inventory where a security-relevant event happens: authentication attempts and their outcome, authorization denials and sensitive grants, credential and privilege changes, account lifecycle events, and access to sensitive data. This is the set of sources that each need to reach a durable audit sink.

  2. Check each decision actually reaches an audit sink. For every one, trace whether it emits a durable, security-relevant record, not just a response to the user. A denial that returns an error but logs nothing, or logs only at a debug level that is off in production, is invisible to an investigation. A decision that fires with no record is the core gap.

Read the full file on GitHub · 135 lines

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. 8d ago First seen · 135 lines · 178 tokens per session scan A d9525b6c0ae9

Subscribe to this mod's changes

auditing-security-logging-completeness is a skill published in the GitHub repository UnboundCompute/security-agent-skills (5 stars, last pushed 5d ago), licensed MIT. It adds 178 tokens to every session and 1,966 once invoked, about $0.0009 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-31.

Related

Other skills, from other repositories

protect

Add Arcjet request protection to JavaScript and TypeScript HTTP handlers. Use when protecting Next.js, Express, Fastify, SvelteKit, Remix, Astro, Nuxt, Bun, Deno, NestJS, or Node.js routes with rate limiting, bot detection, Shield, email validation, or sensitive info detection.

arcjet/arcjet-js · 67 tokens

create-auth-skill

Scaffold and implement authentication in TypeScript/JavaScript apps using Better Auth. Detect frameworks, configure database adapters, set up route handlers, add OAuth providers, and create auth UI pages. Use when users want to add login, sign-up, or authentication to a new or existing project with Better Auth.

Agent-Threat-Rule/agent-threat-rules · 66 tokens

fhir-developer-skill

FHIR API development guide for building healthcare endpoints. Use when: (1) Creating FHIR REST endpoints (Patient, Observation, Encounter, Condition, MedicationRequest), (2) Validating FHIR resources and returning proper HTTP status codes and error responses, (3) Implementing SMART on FHIR authorization and OAuth…

Agent-Threat-Rule/agent-threat-rules · 132 tokens

api-security

Reviews REST and GraphQL APIs against the OWASP API Security Top 10:2023. Auto-invoked when reviewing OpenAPI/Swagger specs, API endpoint code, or GraphQL schemas. Covers BOLA, BFLA, authentication, rate limiting, and SSRF. Produces findings mapped to API1-API10 with remediation guidance.

UnitOneAI/SecuritySkills · 74 tokens

create-auth-skill

Scaffold and implement authentication in TypeScript/JavaScript apps using Better Auth. Detect frameworks, configure database adapters, set up route handlers, add OAuth providers, and create auth UI pages. Use when users want to add login, sign-up, or authentication to a new or existing project with Better Auth.

Agent-Threat-Rule/agent-threat-rules · 66 tokens

api-breaker

Automated API security testing starting from domains. Discovers REST, GraphQL, and SOAP APIs, reconstructs schemas, and tests for BOLA/IDOR, BFLA, mass assignment, JWT attacks, rate limiting bypass, and business logic flaws. Use when user asks to "test API security", "break API", "find API vulnerabilities", "test…

Orizon-eu/claude-code-pentest · 101 tokens