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 supermaciz/sessions-chronicle --skill pr-quizgit clone --depth 1 https://github.com/supermaciz/sessions-chronicleWrote 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/supermaciz/sessions-chronicle/pr-quiz)<a href="https://agentmods.dev/skills/supermaciz/sessions-chronicle/pr-quiz"><img src="https://agentmods.dev/badge/skills/supermaciz/sessions-chronicle/pr-quiz/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/supermaciz/sessions-chronicle/pr-quiz"><img src="https://agentmods.dev/badge/skills/supermaciz/sessions-chronicle/pr-quiz.svg" alt="Reviewed on agentmods" width="80" 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.00039 | $0.00987 |
| Opus 5 | $0.00019 | $0.00494 |
| Sonnet 5 | $0.00008 | $0.00197 |
| Haiku 4.5 | $0.00004 | $0.00099 |
Grade A, and why
pr-quiz 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 10d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Quiz Facilitator (Sessions Chronicle)
Overview
Turn a PR diff into an interactive review quiz for Sessions Chronicle. Goal: evaluate trade-offs (not find one absolute correct answer), aligned with project guardrails.
When to Use
Use when the user asks for:
- a code review quiz on a PR or diff
- learning through A/B implementation choices
- review coaching focused on Rust, Relm4, SQLite, or parser decisions
Do not use when user asks for direct refactoring or direct bugfix implementation or a simple code review.
Workflow
- Ask for input source if missing:
- GitHub PR URL, or
- local repo + base branch (usually
main)
- Build context before quiz:
- PR intent (title, description, commits)
- related design doc in
docs/explorations/*-design.mdor*-exploration.mdwhen available - full diff scope (
base...HEAD)
- Reduce scope if diff is large (>15 files or >400 changed lines):
- announce scope reduction
- keep core logic files and skip generated, lock, config, and cosmetic-only files
- Select 1-5 comparisons with priority:
src/database/,src/parsers/,src/session_sources.rssrc/ui/behavior and data-flow filessrc/models/API shape and contracts- tests covering changed behavior
- Present one comparison at a time and wait for answer before moving on.
- After each answer:
- if user answers only "A" or "B", ask "Pourquoi ?"
- reveal PR origin (A or B)
- explain trade-offs fairly
- recommend keep, improve, or context-dependent
- End with review phase:
- per comparison: chosen option, PR origin, trade-off analysis, recommendation
- global: strengths + 1-2 actionable improvements
Sessions Chronicle Evaluation Lens
Always evaluate options against these guardrails:
- Data safety
- stream JSONL with
BufReaderline iteration - handle malformed or untrusted entries gracefully
- continue indexing where possible
- stream JSONL with
- Path handling
- no hardcoded user or system paths
- use existing path-resolution helpers (
session_sources.rspatterns)
- Architecture consistency
- keep Relm4 message and update flow clear
- keep boundaries clear across
models/,database/, andui/
- Performance
- consider startup and indexing cost
- avoid loading large logs fully into memory
- UX consistency
- preserve GNOME and Libadwaita interaction patterns
- preserve keyboard and accessibility behavior
- Verification discipline
- tests updated for behavior changes
- CI-parity commands considered
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.
- 10d ago First seen · 132 lines · 39 tokens per session scan A e4da9f13c290
pr-quiz is a skill published in the GitHub repository supermaciz/sessions-chronicle (5 stars, last pushed yesterday), licensed MIT. It adds 39 tokens to every session and 987 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.
Other skills, from other repositories
code-review-excellence
This skill should be used when the user asks to review a diff or pull request, write review comments, audit code quality, establish review standards, or improve how a team performs code review.
plan-eng-review
Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations. Use when asked to "review the architecture", "engineering review", or "lock in the plan". Proactively suggest when…
autoplan
Auto-review pipeline — reads the full CEO, design, eng, and DX review skills from disk and runs them sequentially with auto-decisions using 6 decision principles. Surfaces taste decisions (close approaches, borderline scope, codex disagreements) at a final approval gate. One command, fully reviewed plan out. Use when…
pre-landing-review
Pre-landing PR review. Analyzes diff against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues. Use when explicitly asked for the specialized pre-landing workflow. Product /review requests are handled by OpenBitFun's unified Review mechanism instead.…
pr-review-canvas
Create a OpenBitFun Canvas for reviewing a pull request, branch diff, or change set with Cursor-style diff cards, review maps, risk callouts, and focused reviewer flow. Use when the user asks for a PR review canvas, diff walkthrough, change-set overview, or visual review summary.
github-review-pr
Review GitHub pull requests with detailed, multi-perspective code analysis using parallel subagents. Use this skill whenever the user wants to review a PR, asks for code review on a pull request, mentions "review PR", "check this PR", "look at pull request", or references a PR number or GitHub PR URL. Do NOT use for…