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 agentmods add skills/paultyng/skill-issue/set-session-contextnpx skills add paultyng/skill-issue --skill set-session-contextgit clone --depth 1 https://github.com/paultyng/skill-issueWhat 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 | $0.00044 | $0.00426 |
| Opus 5 | $0.00022 | $0.00213 |
| Sonnet 5 | $0.00009 | $0.00085 |
| Haiku 4.5 | $0.00004 | $0.00043 |
Grade A, and why
set-session-context 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 3d 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
Set Session Context
Automatically set session name and color based on the current git branch and PR.
Steps
-
Detect branch:
git symbolic-ref --short HEAD- If detached HEAD (command fails) → stop, do nothing
- If
mainormaster→ stop, do nothing
-
Look up PR title:
gh pr view --json title --jq '.title' -
Determine session name:
- If PR exists → use PR title
- If no PR → humanize branch name: strip the conventional prefix and slash/hyphen separator, replace remaining hyphens with spaces
feat/add-widget→add widgetfix-login-bug→login bug
-
Run:
/rename <session name> -
Determine color from the branch prefix (match
^(type)[/-]):Prefix Color featblue fixred choregreen docscyan refactoryellow testpurple ciorange buildorange perfyellow stylecyan (no match) blue -
Run:
/color <color>
Behavior
- Execute silently: do not announce, explain, or narrate what you are doing.
- Do not ask for confirmation.
- If
ghis unavailable or fails, fall back to the humanized branch name.
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.
- 3d ago First seen · 58 lines · 44 tokens per session scan A 718c0c4a3460
set-session-context is a skill published in the GitHub repository paultyng/skill-issue (9 stars, last pushed 22d ago), licensed MIT. It adds 44 tokens to every session and 426 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
promptscript
PromptScript language expert for reading, writing, modifying, and troubleshooting .prs files. Use when working with PromptScript syntax, creating or editing .prs files, adding blocks like @identity, @standards, @restrictions, @shortcuts, @skills, or @agents, configuring promptscript.yaml, resolving compilation errors…
thesis-control
Use when AI-assisted thesis edits risk claim drift, scope creep, loss of author control, or repeated revisions that fail to converge; provides spine cards, edit contracts, drift audits, revision escalation, and human gates.
helius-jupiter
Skill "helius-jupiter" from helius-labs/core-ai, covering helius x jupiter — build defi apps on solana, mcp router surface, prerequisites, 1. helius mcp server and 2. jupiter api key.
argument-governance
Build and audit the manuscript argument system: intent, gap-contribution alignment, hierarchical claims, evidence balance, limitations, and reviewer attack surfaces. Use when a paper, thesis chapter, review article, or rebuttal needs explicit intent registers, contribution chains, claim hierarchy, argument maps…
verify
Fact-check claims encountered during reading — dates, names, events, citations. Use when encountering historical facts or disputed claims.
map
Show or update the mapping between literature and thesis chapters — which sources support which arguments. Use for tracking coverage.