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 jrjsmrtn/tlx --skill spec-auditgit clone --depth 1 https://github.com/jrjsmrtn/tlxWrote 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/jrjsmrtn/tlx/spec-audit)<a href="https://agentmods.dev/skills/jrjsmrtn/tlx/spec-audit"><img src="https://agentmods.dev/badge/skills/jrjsmrtn/tlx/spec-audit.svg" alt="Measured on agentmods" 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.00088 | $0.01278 |
| Opus 5 | $0.00044 | $0.00639 |
| Sonnet 5 | $0.00018 | $0.00256 |
| Haiku 4.5 | $0.00009 | $0.00128 |
Grade A, and why
spec-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 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.
Spec Audit — Formal Verification Coverage Report
Scan a project to find modules that TLX extractors can process, check which already have formal specs, and prioritize verification effort.
When to Use
- Starting formal verification on an existing project
- After adding new modules and wondering if they need specs
- Reviewing spec coverage before a release
- Triaging which modules to formally specify first
Step 1: Scan for Extractable Modules
Search the project's lib/ directory for modules matching these patterns:
OTP Behaviours
| Pattern | Type | Extractor |
|---|---|---|
use GenServer or @behaviour :gen_server |
GenServer | mix tlx.gen.from_gen_server |
use GenStateMachine or @behaviour :gen_statem |
gen_statem | mix tlx.gen.from_state_machine |
use Phoenix.LiveView |
LiveView | mix tlx.gen.from_live_view |
.erl with -behaviour(gen_server) |
Erlang gen_server | mix tlx.gen.from_erlang |
.erl with -behaviour(gen_fsm) |
Erlang gen_fsm | mix tlx.gen.from_erlang |
Framework Extensions
| Pattern | Type | Extractor |
|---|---|---|
extensions: [AshStateMachine] |
Ash.StateMachine | mix tlx.gen.from_ash_state_machine |
Workflow & Pipeline Libraries
| Pattern | Type | Extractor |
|---|---|---|
use Reactor |
Reactor workflow | mix tlx.gen.from_reactor |
use Broadway |
Broadway pipeline | mix tlx.gen.from_broadway |
Scan commands
# OTP behaviours
grep -rl "use GenServer\|@behaviour :gen_server" lib/
grep -rl "use GenStateMachine\|@behaviour :gen_statem" lib/
grep -rl "use Phoenix.LiveView\|use.*Live" lib/
grep -rl "behaviour(gen_server)\|behaviour(gen_fsm)" lib/ --include="*.erl"
# Framework extensions
grep -rl "AshStateMachine" lib/
# Workflow & pipeline
grep -rl "use Reactor" lib/
grep -rl "use Broadway" lib/
Step 2: Check Existing Spec Coverage
For each extractable module, check if a corresponding spec exists:
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 · 88 tokens per session scan A 9b9c5c751765
spec-audit is a skill published in the GitHub repository jrjsmrtn/tlx (10 stars, last pushed 1mo ago), licensed MIT. It adds 88 tokens to every session and 1,278 once invoked, about $0.0004 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
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…