paseo-session-brief

paseo-session-brief is a skill for Claude Code, Codex from wilgon456/Paseobility. It costs 117 tokens per session (1,000 once invoked), scanned A, original, MIT.

A skill that creates a short working brief for a software project before coding or when handing work to another agent. It checks the repository state, reads key guidance files, and summarizes commands, structure, and risks.

In plain words
What is it for?
Use it to prepare a session brief covering the repository root, Git state, important documentation, available scripts, and likely risk areas.
Why use it?
It reduces the chance of starting work with missing project context or overlooking the correct development and test commands.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions CLAUDE.md; mentions AGENTS.md.

Good fit Use it to prepare a session brief covering the repository root, Git state, important documentation, available scripts, and likely risk areas.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/wilgon456/paseobility/paseo-session-brief
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 wilgon456/Paseobility --skill paseo-session-brief
Clone the repo
git clone --depth 1 https://github.com/wilgon456/Paseobility

Made for: Claude Code, 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 paseo-session-brief

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/wilgon456/paseobility/paseo-session-brief"><img src="https://agentmods.dev/badge/skills/wilgon456/paseobility/paseo-session-brief.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 117 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,000 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.00117 $0.01000
Opus 5 $0.00059 $0.00500
Sonnet 5 $0.00023 $0.00200
Haiku 4.5 $0.00012 $0.00100

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

Security

Grade A, and why

paseo-session-brief 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.

skills/paseo-session-brief/SKILL.md · 148 lines

How it starts

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

Paseo Session Brief

This skill produces a short, actionable context brief for the current repo. It is meant for the start of a work session, not for deep implementation.

Use /paseo-project-bootstrap when the user wants setup scripts or generated .paseobility/ files. Use this skill when the user wants a readable brief in the conversation.

Goals

  • identify the active project and git state
  • read the most important docs and agent instructions
  • identify likely install/dev/build/test commands
  • summarize project shape and risk areas
  • give the next agent or human a clean starting point

Core workflow

  1. Confirm root and status:
    pwd
    git rev-parse --show-toplevel
    git remote -v
    git branch --show-current
    git status --short
    
  2. When Paseo CLI is available, establish the live topology without mutation:
    paseo --version
    paseo daemon status --json
    paseo project ls --json
    paseo workspace ls --json
    paseo script ls --cwd <project-root> --json
    
    Do not restart the daemon or start workspace scripts for a brief.
  3. List files with rg --files first.
  4. Read available instruction sources:
    • README*
    • AGENTS.md
    • CLAUDE.md
    • .cursor/rules/**
    • .github/copilot-instructions.md
    • important files under docs/
  5. Detect project commands from:
    • package.json
    • pyproject.toml, requirements*.txt
    • Cargo.toml
    • go.mod
    • Makefile, justfile, Taskfile.yml
    • paseo.json
  6. Produce the brief. Do not edit files unless the user asks.

Reading strategy

Keep the brief lightweight:

  • Read README and explicit instruction files first.
  • For docs/, list files and read only obviously relevant overview, setup, architecture, contributing, or decision documents.
  • Do not read every source file unless the repo is tiny or the user asks.
  • Prefer command discovery over guessing.
  • If generated .paseobility/context.md exists, read it and verify it against current git state.

Read the full file on GitHub · 148 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 · 148 lines · 117 tokens per session scan A ab835042decb

Subscribe to this mod's changes

paseo-session-brief is a skill published in the GitHub repository wilgon456/Paseobility (19 stars, last pushed 14d ago), licensed MIT. It adds 117 tokens to every session and 1,000 once invoked, about $0.0006 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens