agentmods.dev

session-report

session-report is a skill for Codex from HoangNguyen0403/agent-skills-standard. It costs 22 tokens per session (659 once invoked), scanned A, original, MIT.

A session record that captures what changed during a development task, how it was checked, which files were affected, and what remains unresolved.

In plain words
What is it for?
It is for documenting commands, test results, changed files, blockers, risks, follow-up owners, and gaps in requirements or standards.
Why use it?
It preserves delivery evidence after work ends, so others can understand the result without reconstructing the whole session.

Skill for Codex

Written for Codex: installed under .codex/.

not rated 565repo +4 3d ago A scan SkillSpector: pass 22 tokens original MIT

Good fit It is for documenting commands, test results, changed files, blockers, risks, follow-up owners, and gaps in requirements or standards.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/hoangnguyen0403/agent-skills-standard/session-report
View source ↗ HoangNguyen0403/agent-skills-standard npmjs.com
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 HoangNguyen0403/agent-skills-standard --skill session-report
Clone the repo
git clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standard

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 session-report

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/session-report"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/session-report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 659 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.00022 $0.00659
Opus 5 $0.00011 $0.00329
Sonnet 5 $0.00004 $0.00132
Haiku 4.5 $0.00002 $0.00066

Measured 9d ago against content hash 3e006d1ae76e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

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 9d 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.

.codex/skills/session-report/SKILL.md · 86 lines

How it starts

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

Session Report Skill

[!IMPORTANT] Capture delivery evidence, commands, changed files, blockers, and standards feedback after a work session.

Optional args: slug=, ticket=<id/url>, mode=interactive|autonomous|channel, channel=, auto_continue=true|false, profile=business|hybrid|technical.

Instructions

When the user asks to perform this workflow, execute the following steps:

Session Report Workflow

Goal: Preserve a concise artifact of what changed, how it was verified, and what should improve.

Steps

  1. Collect session facts:
    • User goal, ticket/PR/spec links, changed files, commands run, test results, screenshots/logs, environments.
    • MCP/tool calls used when available; otherwise local command summaries and artifact paths.
    • Load common-operator-profile; carry the inherited operator_profile from the Handoff Payload without re-inferring it.
  2. Capture evidence:
    • Implementation summary tied to ACs or tasks.
    • Verification commands and PASS/FAIL/BLOCKED status.
    • Remaining risks, assumptions, and follow-up owners.
  3. Record requirements drift:
    • BRD-lite, PRD, and SRS/FRS updates completed or missing.
    • Traceability gaps found during implementation or verification.
  4. Route:
    • Remaining code work -> implement-feature or dev-fix.
    • Missing evidence -> verify-work or traceability-audit.
    • Standards update -> retro-learn.
    • Release communication -> publish-notes.

Runtime Contract

  • Use at the end of a work session to preserve evidence and follow-ups before context is lost.
  • Required inputs: session goal plus changed files or commands run during the session.
  • Return BLOCKED only when no session evidence (changes, commands, or verification) exists to report.

Handoff Payload

  • slug, operator_profile, goal, changes, verification results, requirement-drift status, risks, follow-ups, next workflow.

Blocking Questions

  • Ask max 3 at a time with a recommended default and 2-3 options.

Read the full file on GitHub · 86 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. 9d ago First seen · 86 lines · 22 tokens per session scan A 3e006d1ae76e

Subscribe to this mod's changes

session-report is a skill published in the GitHub repository HoangNguyen0403/agent-skills-standard (565 stars, last pushed 3d ago), licensed MIT. It adds 22 tokens to every session and 659 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-09-03.

Project managementReactWriting and docsbest-practicescoding-standardsflutternestjsnextjs
Related

Other skills, from other repositories

intelligence-docs

Keeps the CopilotKit Intelligence landing page in sync when a new Intelligence feature ships or when Intelligence docs are added, renamed, or removed. Use when adding Intelligence capabilities, writing or moving pages under docs/intelligence, editing IntelligenceFeatureCards, or changing…

CopilotKit/CopilotKit · 83 tokens

plan

PM planning workflow that gathers requirements, decomposes them into prioritized tasks, defines API contracts, and produces both a machine-readable plan and a human-readable tracker in docs/plans/.

first-fluke/fullstack-starter · 37 tokens

coordinate-pro

Thorough version of coordinate - high-quality development workflow with 11 review steps out of 17.

first-fluke/fullstack-starter · 22 tokens

coordinate

Coordinate multiple agents for a complex multi-domain project using PM planning, parallel agent spawning, and QA review.

first-fluke/fullstack-starter · 22 tokens

exec-plan

Create, manage, and track execution plans as first-class repository artifacts in docs/exec-plans/.

first-fluke/fullstack-starter · 23 tokens

work

Coordinate multiple agents for a complex multi-domain project using PM planning, parallel agent spawning, and QA review.

first-fluke/fullstack-starter · 22 tokens