audit

A command-line tool for viewing audit logs, which are records of actions performed in a system.

In plain words
What is it for?
Use it to list or inspect audit entries, filter them by operation type, user ID, date range, limit, or offset, and output results as JSON.
Why use it?
It lets you narrow down recorded activity by operation, user, and time instead of searching through all records manually.

Command

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 commands/gotempsh/temps/audit
Clone the repo
git clone --depth 1 https://github.com/gotempsh/temps
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 328 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00328
Opus 5 $0.00000 $0.00164
Sonnet 5 $0.00000 $0.00066
Haiku 4.5 $0.00000 $0.00033

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

Security

Grade A, and why

audit 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 3d 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/temps/references/commands/audit.md · 42 lines

What it actually says

audit command reference

Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.

audit

View audit logs

Subcommands:

  • list (ls) - List audit logs
  • show - Show audit log details

audit list (alias: ls)

List audit logs

Options:

Flag Description Default Required
--json Output in JSON format - No
--limit <n> Maximum number of logs to return 50 No
--offset <n> Number of logs to skip - No
--operation-type <type> Filter by operation type - No
--user-id <id> Filter by user ID - No
--from <timestamp> Start timestamp (ISO 8601 or epoch ms) - No
--to <timestamp> End timestamp (ISO 8601 or epoch ms) - No

audit show

Show audit log details

Options:

Flag Description Default Required
--id <id> Audit log ID - Yes
--json Output in JSON format - No
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. 3d ago First seen · 42 lines · 0 tokens per session scan A 9d1d030c0ab8

Subscribe to this mod's changes

audit is a command published in the GitHub repository gotempsh/temps (700 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 328 tokens. 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.