log

A command for viewing persistent operation and audit logs. Audit logs are records of actions and outcomes kept for troubleshooting, review, or compliance.

In plain words
What is it for?
Use it to browse logs interactively, show recent entries, inspect errors, review audit records, view statistics, output JSON lines, or clear the operations log.
Why use it?
It helps you find what happened during a failed operation without scanning every log entry. Filters and summaries make it easier to focus on a command, status, time period, or project.

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/runkids/skillshare/log
Clone the repo
git clone --depth 1 https://github.com/runkids/skillshare
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 2,176 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.02176
Opus 5 $0.00000 $0.01088
Sonnet 5 $0.00000 $0.00435
Haiku 4.5 $0.00000 $0.00218

Measured yesterday against content hash dc7dd1c359fc, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

log 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 yesterday.

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.

website/docs/reference/commands/log.md · 251 lines

How it starts

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

log

View persistent operations and audit logs for debugging and compliance.

skillshare log                    # Interactive TUI (default on TTY)
skillshare log --audit            # Show only audit log
skillshare log --tail 50          # Show last 50 entries
skillshare log --cmd sync         # Show only sync entries
skillshare log --status error     # Show only errors
skillshare log --since 2d         # Entries from last 2 days
skillshare log --stats            # Show summary statistics
skillshare log --json             # Output as JSONL
skillshare log --no-tui           # Plain text output
skillshare log --clear            # Clear operations log
skillshare log -p                 # Project operations + audit logs

When to Use

  • Browse and filter log entries interactively
  • Debug what happened during a failed operation
  • Review the audit trail for compliance or troubleshooting
  • Filter logs by command, status, or time range for investigation

Interactive TUI

On a TTY, skillshare log launches an interactive terminal UI with:

  • Fuzzy filtering — type to filter by timestamp, command, status, source, or detail content
  • Keyboard navigation — arrow keys to browse, q to quit
  • Detail panel — shows full timestamp, command, status, duration, source, and structured args for the selected entry
  • Stats footer — always-visible compact summary: ops count, success rate, last operation
  • Stats panel — press s to toggle a full breakdown by command with success/failure counts
  • Merged view — operations and audit entries are merged and sorted by time when viewing both

Use --no-tui to skip the TUI and print plain text instead:

skillshare log --no-tui           # Plain text output
skillshare log --no-tui | less    # Pipe to pager manually

What Gets Logged

Every mutating CLI and Web UI operation is recorded as a JSONL entry with timestamp, command, status, duration, and contextual args.

Command Log File
install, uninstall, sync, push, pull, collect, backup, restore, update, target, trash, config, check, diff, init, upgrade operations.log
audit audit.log

Read the full file on GitHub · 251 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. yesterday First seen · 251 lines · 0 tokens per session scan A dc7dd1c359fc

Subscribe to this mod's changes

log is a command published in the GitHub repository runkids/skillshare (2,597 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,176 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.