gsd-session-report

gsd-session-report is a skill for Codex from SpillwaveSolutions/agent-brain. It costs 19 tokens per session (601 once invoked), scanned A, original, MIT.

A session-reporting helper that summarises work, outcomes, and estimated token usage. Tokens are the small pieces of text used to measure an AI conversation's input and output.

In plain words
What is it for?
Use it to produce a report covering the session's work summary, results, and token estimates.
Why use it?
It provides a record of what happened in a coding session and an estimate of its AI usage.

Skill for Codex

Written for Codex: installed under .codex/. Also seen: names the AskUserQuestion tool; mentions Claude Code; mentions Codex.

Good fit Use it to produce a report covering the session's work summary, results, and token estimates.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/spillwavesolutions/agent-brain/gsd-session-report
Install

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.

Any agent
npx skills add SpillwaveSolutions/agent-brain --skill gsd-session-report
Clone the repo
git clone --depth 1 https://github.com/SpillwaveSolutions/agent-brain

Made for: Codex.

Wrote 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.

agentmods badge for gsd-session-report

README.md
[![agentmods](https://agentmods.dev/badge/skills/spillwavesolutions/agent-brain/gsd-session-report/github.svg)](https://agentmods.dev/skills/spillwavesolutions/agent-brain/gsd-session-report)
Your own site
<a href="https://agentmods.dev/skills/spillwavesolutions/agent-brain/gsd-session-report"><img src="https://agentmods.dev/badge/skills/spillwavesolutions/agent-brain/gsd-session-report/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.

agentmods 80×15 button for gsd-session-report

Your own site · 80×15
<a href="https://agentmods.dev/skills/spillwavesolutions/agent-brain/gsd-session-report"><img src="https://agentmods.dev/badge/skills/spillwavesolutions/agent-brain/gsd-session-report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 19 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 601 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00019 $0.00601
Opus 5.5 $0.00008 $0.00240
Sonnet 5.5 $0.00004 $0.00120
Haiku 4.5 $0.00002 $0.00060

Measured 1mo ago against content hash 4c2c1f7fc036, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

gsd-session-report 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 1mo 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.

Origin

Copies of this mod

3 near-identical copies found in the catalogue:

.codex/skills/gsd-session-report/SKILL.md · 59 lines

How it starts

The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.

<codex_skill_adapter>

A. Skill Invocation

  • This skill is invoked by mentioning $gsd-session-report.
  • Treat all user text after $gsd-session-report as {{GSD_ARGS}}.
  • If no arguments are present, treat {{GSD_ARGS}} as empty.

B. AskUserQuestion → request_user_input Mapping

GSD workflows use AskUserQuestion (Claude Code syntax). Translate to Codex request_user_input:

Parameter mapping:

  • header → header
  • question → question
  • Options formatted as "Label" — description → {label: "Label", description: "description"}
  • Generate id from header: lowercase, replace spaces with underscores

Batched calls:

  • AskUserQuestion([q1, q2]) → single request_user_input with multiple entries in questions[]

Multi-select workaround:

  • Codex has no multiSelect. Use sequential single-selects, or present a numbered freeform list asking the user to enter comma-separated numbers.

Execute mode fallback:

  • When request_user_input is rejected (Execute mode), present a plain-text numbered list and pick a reasonable default.

C. Task() → spawn_agent Mapping

GSD workflows use Task(...) (Claude Code syntax). Translate to Codex collaboration tools:

Direct mapping:

  • Task(subagent_type="X", prompt="Y") → spawn_agent(agent_type="X", message="Y")
  • Task(model="...") → omit (Codex uses per-role config, not inline model selection)
  • fork_context: false by default — GSD agents load their own context via <files_to_read> blocks

Parallel fan-out:

  • Spawn multiple agents → collect agent IDs → wait(ids) for all to complete

Result parsing:

  • Look for structured markers in agent output: CHECKPOINT, PLAN COMPLETE, SUMMARY, etc.
  • close_agent(id) after collecting results from each agent </codex_skill_adapter>

<execution_context> @/Users/richardhightower/clients/spillwave/src/agent-brain/.codex/get-shit-done/workflows/session-report.md </execution_context>

Read the full file on GitHub · 59 lines

Changes

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.

  1. 1mo ago First seen · 59 lines · 19 tokens per session scan A 4c2c1f7fc036

Subscribe to this mod's changes

gsd-session-report is a skill published in the GitHub repository SpillwaveSolutions/agent-brain (119 stars, last pushed 26d ago), licensed MIT. It adds 19 tokens to every session and 601 once invoked, about $0.0001 per session on Opus 5.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-09-05.

Related

Other skills, from other repositories

install-openviking-memory

Install and configure the OpenViking long-term memory plugin for OpenClaw via natural conversation. Once installed, the plugin automatically captures facts from chats and recalls relevant context before each reply (auto-capture + auto-recall, cross-session). Covers prerequisites, install through OpenClaw's plugin…

volcengine/OpenViking · 191 tokens

ov-session-report

Analyze local Q&A session JSONL files and produce a complete, auditable English Markdown weekly report over consecutive time windows, with all data required for downstream Feishu document and whiteboard rendering. Use for requests such as "analyze the latest week of sessions," "generate a community Q&A weekly report,"…

volcengine/OpenViking · 86 tokens

skill-creator

Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.

volcengine/OpenViking · 28 tokens

llm-wiki

Compile heterogeneous knowledge sources—including documents, notes, web content, transcripts, research materials, and code repositories—into a Karpathy-style, evidence-grounded LLM Wiki with a maintained index; default entity and concept pages; and selective method, comparison, analysis, or instruction-requested…

volcengine/OpenViking · 90 tokens

openviking-context-database

Use OpenViking from OpenClaw through @openviking/openclaw-plugin: long-term memory, session archives, resource and Agent Skill import, semantic recall, recall trace debugging, and externalized tool-result recovery. Prefer this skill when the user wants to use, query, debug, or operate OpenViking context from an…

volcengine/OpenViking · 95 tokens

knowledge-distillation

Compile one or more OpenViking knowledge bases or document collections into topic-organized, evidence-grounded high-level knowledge, including cross-source findings, trends, changes, drivers, comparisons, implications, and uncertainties. Use with ov compile when the user asks to distill or synthesize a knowledge base…

volcengine/OpenViking · 89 tokens