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 skills add baphuongna/pi-crew --skill ownership-session-securitygit clone --depth 1 https://github.com/baphuongna/pi-crewWrote 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/baphuongna/pi-crew/ownership-session-security)<a href="https://agentmods.dev/skills/baphuongna/pi-crew/ownership-session-security"><img src="https://agentmods.dev/badge/skills/baphuongna/pi-crew/ownership-session-security/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.
<a href="https://agentmods.dev/skills/baphuongna/pi-crew/ownership-session-security"><img src="https://agentmods.dev/badge/skills/baphuongna/pi-crew/ownership-session-security.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 57 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00032 | $0.00630 |
| Opus 5.5 | $0.00013 | $0.00252 |
| Sonnet 5.5 | $0.00006 | $0.00126 |
| Haiku 4.5 | $0.00003 | $0.00063 |
Grade A, and why
ownership-session-security 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ownership-session-security
Use this skill for cross-session safety and trust-boundary work.
Source patterns distilled
- Pi session IDs:
ctx.sessionManager.getSessionId()from Pi coreExtensionContext - pi-crew ownership:
TeamRunManifest.ownerSessionId,src/extension/team-tool/run.ts,cancel.ts,respond.ts - Path safety:
src/utils/safe-paths.ts,src/state/state-store.ts,src/state/mailbox.ts - Destructive actions:
src/extension/team-tool/lifecycle-actions.ts,src/worktree/cleanup.ts
Rules
- Propagate the active Pi session ID into
TeamContextfor every production tool/command path. - New runs should record
ownerSessionIdwhen available. - For owned runs, cross-session actions that mutate state must be rejected unless explicit force/admin semantics are designed and tested.
- Legacy runs without
ownerSessionIdmay remain permissive for backward compatibility, but document this behavior. - User/LLM-controlled path fields (
cwd, import paths, artifact paths, task IDs) must be normalized and contained under an allowed base. - Use
resolveContainedPath,resolveRealContainedPath,assertSafePathId, and symlink checks rather than ad-hocstartsWithchecks. - Destructive management actions must require
confirm: true; referenced resource deletes must requireforce: truewhere applicable.
Enforcement — Ownership Session Security Gate
Before mutating run state or cross-session operations, verify:
- Session ID propagated into TeamContext for production paths
- ownerSessionId verified before respond/cancel/mutate operations
- Path fields (cwd, import, artifact) normalized and contained under allowed base
- Safe path helpers used (resolveContainedPath, assertSafePathId) not startsWith checks
- Destructive actions require explicit confirm/force parameters
If ANY answer is NO → Stop. Verify ownership before mutating state.
Anti-patterns
- Assuming
ctx.sessionIdexists directly on Pi context. - Letting
cwd: ../other-projectmove run state into another project. - Letting
respond/cancelmutate a foreign owned run. - Trusting task IDs, run IDs, or artifact paths from tool params without validation.
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.
- 1mo ago Changed · +3 lines · +22 tokens per session 5dd0cab234c4
- 1mo ago First seen · 61 lines · 10 tokens per session scan A 9cd5547ebfcb
ownership-session-security is a skill published in the GitHub repository baphuongna/pi-crew (59 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 630 once invoked, about $0.0001 per session on Opus 5.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.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.