agentmods.dev

audit

audit is a command for coding agents from sk-lim19f/Hypomnema. It costs 34 tokens per session (650 once invoked), scanned A, original, MIT.

A command for reviewing recent Claude Code sessions for missing activity and producing an optional weekly report.

In plain words
What is it for?
It is for checking session metrics, classifying observability gaps, and summarising them weekly.
Why use it?
It shows whether useful wiki actions, such as searching, importing information, or recording feedback, were missed.

Command

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the hypo plugin — 1 skill, 16 commands, 9 hooks shipped together

not rated 10 changed yesterday A scan 34 tokens original MIT
View the source file sk-lim19f/Hypomnema
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/sk-lim19f/hypomnema/audit
Clone the repo
git clone --depth 1 https://github.com/sk-lim19f/Hypomnema

Or install hypo, the plugin that ships this one along with the rest of its 1 skill, 16 commands, 9 hooks.

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 audit

README.md
[![agentmods](https://agentmods.dev/badge/commands/sk-lim19f/hypomnema/audit.svg)](https://agentmods.dev/commands/sk-lim19f/hypomnema/audit)
Your own site
<a href="https://agentmods.dev/commands/sk-lim19f/hypomnema/audit"><img src="https://agentmods.dev/badge/commands/sk-lim19f/hypomnema/audit.svg" alt="Measured on agentmods" height="20"></a>
Per session 34 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 650 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.1 $0.00034 $0.00650
Opus 5 $0.00017 $0.00325
Sonnet 5 $0.00007 $0.00130
Haiku 4.5 $0.00003 $0.00065

Measured yesterday against content hash ec55aa70457b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, 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 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.

commands/audit.md · 47 lines

How it starts

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

You are running /hypo:audit. Inspect recent Claude Code sessions to see how much of the wiki's value motion is actually happening (search, ingest, feedback), then either show the result inline or write a weekly observability page.

What this shows

  • Per-session metrics — search count, ingest count, URL mentions, feedback count
  • Classification — normal / search-0 / search-many / ingest-missed / staleness-skip
  • Optional weekly aggregation with an autonomy score (heuristic v0)

Definition: [[pages/observability/_index]].

Step 1 — Run script

Bundled scripts here run via ${CLAUDE_PLUGIN_ROOT}/scripts/. To resolve that package root: if ${CLAUDE_PLUGIN_ROOT} is already an absolute path, use it; otherwise read pkgRoot from ~/.claude/hypo-pkg.json (only when non-empty and the target script exists under it); otherwise use the hypo@hypomnema (or legacy hypomnema@hypomnema) installPath in ~/.claude/plugins/installed_plugins.json; if none resolve, stop and tell the user to run hypomnema upgrade --apply (or /hypo:upgrade on a plugin install) or reinstall instead of guessing the cache layout.

If the user specified a Hypomnema directory, pass it as --hypo-dir="<path>". Otherwise omit the flag.

Step 2 — Decide the mode

  • Per-session view (default) — show recent sessions with metrics + classification: 
    node ${CLAUDE_PLUGIN_ROOT}/scripts/session-audit.mjs [--hypo-dir="<path>"] [--limit=20]
  • Weekly report (when the user asks for "weekly", "score", or names a week) — write the report to journal/weekly/<YYYY-Www>.md (spec §6.4 SoT): 
    node ${CLAUDE_PLUGIN_ROOT}/scripts/weekly-report.mjs [--hypo-dir="<path>"] [--week=YYYY-Www] --write
  • JSON for tooling — append --json to either script.

Step 3 — Report results

Show the output verbatim. Then add a brief interpretation:

  • If staleness-skip dominates: "Most sessions audited are older than 30 days — score reflects backlog, not current behavior."
  • If search-0 count is high: "Sessions ran without consulting the wiki — consider whether /hypo:query was the right reflex."
  • If ingest-missed is non-zero: "Sessions discussed URLs but no /hypo:ingest ran — those captures got lost."
  • Otherwise: "Audit window looks healthy; weekly report committed to the wiki for trend tracking."

Read the full file on GitHub · 47 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 Changed ec55aa70457b
  2. 5d ago First seen · 47 lines · 34 tokens per session scan A 4628fb89eb61

Subscribe to this mod's changes

audit is a command published in the GitHub repository sk-lim19f/Hypomnema (10 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 650 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-08-31.

Analytics and metrics
Related

Other commands, from other repositories

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

clarify

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

github/spec-kit · 26 tokens

converge

Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

github/spec-kit · 35 tokens

implement

Execute the implementation plan by processing and executing all tasks defined in tasks.md.

github/spec-kit · 14 tokens