Borrowing it
Nothing to install: this file belongs to butgo/butgo-specdrive-lab. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/butgo/butgo-specdrive-lab/main/.agents/skills/session/SKILL.mdgit clone --depth 1 https://github.com/butgo/butgo-specdrive-labWrote 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/butgo/butgo-specdrive-lab/session)<a href="https://agentmods.dev/skills/butgo/butgo-specdrive-lab/session"><img src="https://agentmods.dev/badge/skills/butgo/butgo-specdrive-lab/session.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.00036 | $0.00488 |
| Opus 5 | $0.00018 | $0.00244 |
| Sonnet 5 | $0.00007 | $0.00098 |
| Haiku 4.5 | $0.00004 | $0.00049 |
Grade A, and why
session 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 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.
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.
What it actually says
Session
Use this skill as the argument-based entry point for specdrive session work.
Invocation Rule
If the user's message is exactly $session, treat it as a no-action router call.
Do not wait for another message or ask a follow-up question.
Immediately print the no-action output below and stop.
Supported actions:
start-litestartstatussave
Aliases:
lite->start-litestart-lite->start-litestart->startstatus->statussave->save
If the user provided $session without an action, or provided no recognizable action, list the action choices and stop.
Dispatch
Follow the matching repo-local session action instructions:
start-lite:.agents/skills/session/actions/start-lite.mdstart:.agents/skills/session/actions/start.mdstatus:.agents/skills/session/actions/status.mdsave:.agents/skills/session/actions/save.md
Do not combine actions in one response unless the user explicitly asks.
Output: No Action
Reply with:
- available actions
- short descriptions
- copy-ready examples
Use this concrete shape:
사용 가능한 $session action:
- start-lite: docs/AI_CONTEXT.md 기준으로 최소 세션 복구를 합니다.
- start: 전체 세션 복구용 copy prompt를 준비합니다.
- status: 현재 세션 상태를 짧게 확인합니다.
- save: 세션 저장용 AI_CONTEXT 반영 초안을 준비합니다.
예시:
$session start-lite
$session start
$session status
$session save
Examples:
$session start-lite
$session start
$session status
$session save
Boundaries
- Session work is meta operation work.
- Do not perform
doc,dev, orgitwork through this skill. - Do not edit files unless the dispatched action explicitly allows it and the user approves.
- Do not inspect
docs/history/**unless the user explicitly asks for history lookup.
What ships with it
4 files 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 · 84 lines · 36 tokens per session scan A 49e018f2684f
session is a skill published in the GitHub repository butgo/butgo-specdrive-lab (1 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 488 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
sdlc-review
Review Kanban handoffs and route verified outcomes.
huashu-keynote-black
OpenDesign's all-hands: the year in review, the three priorities, and what every team owns next quarter. Built as a decision-grade corporate strategy deck for whole company.
gh-issues
Use when creating, triaging, or commenting on GitHub issues for the Kilo VS Code extension or JetBrains plugin via gh. Covers issue templates, project board assignment, title conventions, and required gh scopes.
triage-issue
Intelligently triage bug reports and error messages by searching for duplicates in Jira and offering to create new issues or add comments to existing ones. When an agent needs to: (1) Triage a bug report or error message, (2) Check if an issue is a duplicate, (3) Find similar past issues, (4) Create a new bug ticket…
create-stories
Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.
team-qa
Orchestrate the QA team through a full testing cycle. Coordinates qa-lead (strategy + test plan) and qa-tester (test case writing + bug reporting) to produce a complete QA package for a sprint or feature. Covers: test plan generation, test case writing, smoke check gate, manual QA execution, and sign-off report.