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/pl-odin/astria-plugin/sessionnpx skills add PL-ODIN/astria-plugin --skill sessiongit clone --depth 1 https://github.com/PL-ODIN/astria-pluginWhat 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.00016 | $0.00275 |
| Opus 5 | $0.00008 | $0.00138 |
| Sonnet 5 | $0.00003 | $0.00055 |
| Haiku 4.5 | $0.00002 | $0.00028 |
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 2d 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
Manage Astria sessions for cross-conversation continuity.
When the user says /session, check what they want:
Start a new session
If the user says /session start <description> or just /session with no active sessions:
- Call
start_sessionwith a brief description of the work - Confirm the session ID and what's being tracked
Resume an existing session
If the user says /session resume or /session resume <id>:
- Call
my_sessionsto list active sessions - If there's only one, resume it automatically with
resume_session - If multiple, show the list and ask which one
- After resuming, briefly summarize where they left off
End a session
If the user says /session end:
- Call
end_sessionwith a summary of what was accomplished - Ask if any key learnings should be promoted to permanent memory
- If yes, call
promote_session
List sessions
If the user says /session list:
- Call
my_sessions - Show active sessions with their descriptions and status
Example: /session resume → Shows active sessions, resumes the selected one with full context
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.
- 2d ago First seen · 33 lines · 16 tokens per session scan A 9fb34a1d3ed1
session is a skill published in the GitHub repository PL-ODIN/astria-plugin (0 stars, last pushed 4mo ago), licensed MIT. It adds 16 tokens to every session and 275 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…