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 bang9/ai-tools --skill rewind-analyzegit clone --depth 1 https://github.com/bang9/ai-toolsWrote 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/bang9/ai-tools/rewind-analyze)<a href="https://agentmods.dev/skills/bang9/ai-tools/rewind-analyze"><img src="https://agentmods.dev/badge/skills/bang9/ai-tools/rewind-analyze.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.00033 | $0.02175 |
| Opus 5 | $0.00016 | $0.01087 |
| Sonnet 5 | $0.00007 | $0.00435 |
| Haiku 4.5 | $0.00003 | $0.00217 |
Grade B, and why
rewind-analyze scanned grade B with 1 finding 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 7d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- If a session ID is given: find the JSONL file at `~/.codex/sessions/YYYY/MM/DD/*-<id>.jsonl` How it starts
The opening of the file, as written. The whole thing — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior engineering coach reviewing an AI coding session transcript. Your job is to extract actionable insights that help the user improve their next session. Be specific, honest, and constructive.
Optimize for signal over coverage. Omit low-value observations instead of filling every section with weak commentary.
Workflow
Step 1: Locate the session file
Determine the session to analyze from the argument:
- If a session ID is given: find the JSONL file at
~/.codex/sessions/YYYY/MM/DD/*-<id>.jsonl - If
--pathis given: use that file directly - If no argument: prompt the user for a session ID or path
Step 2: Read the session transcript
Read the JSONL file. Each line is a JSON object representing a session event. Focus on:
- User messages (what was asked)
- Assistant responses and tool calls (what was done)
- Tool results (what succeeded/failed)
- Thinking blocks (reasoning quality)
Treat eventIndex as the 1-based line number in the original JSONL file. Note: one JSONL line may produce multiple events in the viewer, so this is an approximate reference.
Step 3: Analyze and generate insights
Produce a JSON file matching this exact schema:
{
"generatedAt": "ISO-8601 timestamp",
"model": "model that generated this analysis",
"promptReviews": [
{
"eventIndex": 0,
"promptSnippet": "first 100 chars of the user message",
"quality": "good|fair|poor",
"feedback": "why this prompt was effective or problematic",
"suggestion": "optional: how to rephrase for better results"
}
],
"strategyCritique": {
"summary": "one-paragraph overall session strategy assessment",
"strengths": ["what went well"],
"weaknesses": ["what could improve"],
"alternativeApproach": "optional: a fundamentally different strategy that might have worked better"
},
"keyDecisions": [
{
"eventIndex": 0,
"description": "what decision was made",
"impact": "positive|neutral|negative",
"reasoning": "why this decision helped or hurt"
}
],
"takeaways": [
"Specific, actionable improvement for next session"
],
"workTypeReviews": [
{
"workType": "debugging|feature|refactoring|planning|code-review|docs",
"eventRange": [10, 85],
"score": "good|fair|poor",
"description": "what was done in this segment (the actual work, not the evaluation)",
"practices": [
{
"name": "practice name",
"followed": "yes|partial|no",
"note": "concrete evidence from the transcript"
}
],
"summary": "one-line assessment of how well best practices were followed"
}
]
}
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 181 lines · 33 tokens per session scan B dcdf020bb131
rewind-analyze is a skill published in the GitHub repository bang9/ai-tools (10 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 2,175 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
kanban-tui
Comprehensive kanban board and task management via ktui CLI. Use for project tracking, todo lists, task dependencies, workflow automation, and board management. Activates when user mentions boards, tasks, kanban, or project management. If the ktui command is not available, but uv is available utilize uvx kanban-tui…
quick-capture
Use this skill to drop a new task into GSD Task Manager from any AI assistant that has the gsd-mcp-server connected.
triage-inbox
Use this skill to walk the user through their unfiled or stale tasks and move them into the right Eisenhower quadrant.
agentrq
Lead multiple agents to accomplish big tasks with specialized workspaces/agents by assigning tasks to specialized agents.
himalaya
Manage email accounts and mailboxes through the local Himalaya CLI. Use for reading mail, searching folders, flagging messages, moving or deleting messages, downloading attachments, composing or sending messages/templates, and diagnosing Himalaya email account configuration once the skill runtime is enabled.
agentrq
Execute tasks assigned by humans or supervisor agents within a specific AgentRQ workspace. Use when you receive channel messages or need to report progress on tasks.