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/ai-analyst-lab/agentxp/readoutsnpx skills add ai-analyst-lab/agentxp --skill readoutsgit clone --depth 1 https://github.com/ai-analyst-lab/agentxpWrote 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/ai-analyst-lab/agentxp/readouts)<a href="https://agentmods.dev/skills/ai-analyst-lab/agentxp/readouts"><img src="https://agentmods.dev/badge/skills/ai-analyst-lab/agentxp/readouts.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 | $0.00026 | $0.00737 |
| Opus 5 | $0.00013 | $0.00368 |
| Sonnet 5 | $0.00005 | $0.00147 |
| Haiku 4.5 | $0.00003 | $0.00074 |
Grade A, and why
readouts 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.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: /readouts
Purpose
Every readout produced by the presentation spine appends one entry to experiments/<id>/readouts/catalog.jsonl — an append-only hash-chained ledger. This skill walks the catalog (per-experiment or cross-experiment), validates the chain, and regenerates the static HTML index navigator.
The catalog is the only surviving hash chain in v2; tampering breaks it independently of git.
When to invoke
Direct:
/readouts <exp_id>— list this experiment's renders/readouts --index— regenerate the cross-experiment HTML navigator/readouts <exp_id> --validate— walk the chain, exit non-zero on break
Plain-English routing:
| Phrase | What to do |
|---|---|
| "Show me the renders for exp_001" | /readouts exp_001 |
| "Rebuild the audit index" | /readouts --index |
| "Is the catalog intact" | /readouts <exp_id> --validate |
| "What readouts have I made across all experiments" | /readouts --index |
Procedure
Catalog mode
from pathlib import Path
from agentxp.workflows.readouts import list_catalog
entries = list_catalog(Path.cwd() / "experiments" / args.exp_id)
for i, entry in enumerate(entries):
payload = entry.payload
print(f"{i:>3} {entry.timestamp} {payload.event:<26} ...")
Index mode
from agentxp.workflows.readouts import build_index
rows = build_index(Path.cwd())
# Each row: experiment_id, n_renders, worst_status, latest_render_type, latest_render_at
Render an HTML table from the rows and write to readouts/index.html. The worst-case status per experiment uses the cascade: UNVERIFIABLE > DRAFT_UNVERIFIED > VERIFIED.
Validate mode
from agentxp.render.catalog import validate_catalog, CatalogChainBreak
try:
validate_catalog(Path.cwd() / "experiments" / args.exp_id / "readouts" / "catalog.jsonl")
print("catalog chain ok")
except CatalogChainBreak as exc:
print(f"catalog chain break: {exc}", file=sys.stderr)
raise SystemExit(1)
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.
- 3d ago First seen · 88 lines · 26 tokens per session scan A 76560b60ea9a
readouts is a skill published in the GitHub repository ai-analyst-lab/agentxp (11 stars, last pushed 6d ago), licensed Apache-2.0. It adds 26 tokens to every session and 737 once invoked, about $0.0001 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…