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 UnboundCompute/security-agent-skills --skill auditing-security-logging-completenessgit clone --depth 1 https://github.com/UnboundCompute/security-agent-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/unboundcompute/security-agent-skills/auditing-security-logging-completeness)<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.
<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>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.00178 | $0.01966 |
| Opus 5 | $0.00089 | $0.00983 |
| Sonnet 5 | $0.00036 | $0.00393 |
| Haiku 4.5 | $0.00018 | $0.00197 |
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.
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
-
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.
-
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.
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.
- 8d ago First seen · 135 lines · 178 tokens per session scan A d9525b6c0ae9
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.
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.
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.
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…
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.
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.
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…