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 agentmods add skills/tellahq/opensession/audit-codebasenpx skills add tellahq/opensession --skill audit-codebasegit clone --depth 1 https://github.com/tellahq/opensessionWhat 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 | $0.00046 | $0.01703 |
| Opus 5 | $0.00023 | $0.00851 |
| Sonnet 5 | $0.00009 | $0.00341 |
| Haiku 4.5 | $0.00005 | $0.00170 |
Grade A, and why
audit-codebase 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 2d 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit codebase
/audit-codebase → inventory every subsystem → bounded waves of read-only reviewers → validate each finding → audit the audit
You are the coordinator of a read-only audit. The question is not "are there bugs" and not "is this pretty". It is whether the codebase's data structures, state representation, control flow, algorithms and ownership boundaries could be materially simpler than they are.
Keep going until every subsystem has been reviewed and the finished audit has survived fresh checking passes. Adapted from Aaron Francis's audit prompt: https://gist.github.com/aarondfrancis/8735edbe48532f97ee5ea818db4dbd47
The read-only contract
Do not edit files, run tests, implement a recommendation, commit, or push.
Read-only inspection is the whole toolkit: reading files, grep and glob, git log, git diff, listing directories, reading CI config. The repository must be
byte-identical when you finish, working tree and index alike.
Everything you want changed goes into the report as a recommendation. Someone else decides whether to do it, and when.
If $ARGUMENTS names a scope (a directory, a package, a named subsystem), audit
that and record in the report that the boundary was narrowed deliberately.
Otherwise audit the whole repository.
Phase 0 — The report is the state
One canonical report accumulates everything and you update it as you go. Do not carry the inventory in your head: waves of workers will outlive your attention to any single row.
Write it outside the checkout, or you break the read-only contract:
- With Open Session's assets tools,
write_assettoaudit/report.md. That is session scratch space, not the repo, so it works in a read-only Ask session and shows up in the session's Assets tab. - Otherwise a file under
/tmp.
The report holds:
- Subsystem inventory (the coverage contract)
- Confirmed opportunities (validated findings, one row each)
- Explicit skips (a subsystem reviewed and found already clear)
- Cross-cutting patterns (the same shape in three places)
- Duplicates and superseded findings (what you merged, and into what)
- Final priorities and dependencies
- Audit log (which wave covered which rows, and when)
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.
- 2d ago First seen · 169 lines · 46 tokens per session scan A 718a6658537b
audit-codebase is a skill published in the GitHub repository tellahq/opensession (327 stars, last pushed 2d ago), licensed MIT. It adds 46 tokens to every session and 1,703 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…