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/phantom/phantom-connect-sdk/auditnpx skills add phantom/phantom-connect-sdk --skill auditgit clone --depth 1 https://github.com/phantom/phantom-connect-sdkWhat 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.00000 | $0.00856 |
| Opus 5 | $0.00000 | $0.00428 |
| Sonnet 5 | $0.00000 | $0.00171 |
| Haiku 4.5 | $0.00000 | $0.00086 |
Grade A, and why
audit 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.
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: audit
Perform a structured code quality review of a single package in this monorepo.
Arguments: <package-name> — matches a directory under packages/ (e.g. react-sdk, browser-sdk, auth2). If all or empty, do an architecture-level review instead.
Phase 0 — Check previous audits
Glob audit/*-{package-name}*.md. If a recent audit exists, read it for prior findings, resolved items, and open issues. Treat it as a hypothesis, not ground truth — verify every claim against current code before repeating it.
Phase 1 — Read and understand
Read every source file in packages/{package-name}/src/. Build a map of:
- What the package exports (check
packages/{package-name}/src/index.tsand package.jsonexportsfield) - What it imports from other workspace packages (
@phantom/*) - What external APIs, browser APIs, or runtime globals it talks to
- What events or callbacks it emits/subscribes to
- Any React context providers or hooks it exposes
Environment branch scan: Before moving on, grep the package for process.env.NODE_ENV, import.meta.env, __TEST__, or any test-environment guards in business logic. Any branch on NODE_ENV === 'test' inside non-test files is a red flag — it means tests run different code than production. Flag every hit with file and line number.
Phase 2 — Read the tests
Read all test files (*.test.ts, *.test.tsx, **/__tests__/**/*.ts, **/__tests__/**/*.tsx) in the package. Assess:
- What is tested vs what is not
- Mock quality: are mocks accurate representations of real dependencies?
- Assertion specificity: do tests verify outcomes or just that functions were called?
- Whether tests exercise error paths, edge cases, and not just the happy path
Phase 3 — Assess quality
Rate each dimension Good / Fair / Poor with one specific observation each:
| Dimension | Rating | Specific observation |
|---|---|---|
| Implementation quality | ||
| Error handling | ||
| Type safety | ||
| Unit test coverage | ||
| Integration coverage | ||
| Architectural fit | ||
| Security |
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 · 94 lines · 0 tokens per session scan A 2409fa0747f9
audit is a skill published in the GitHub repository phantom/phantom-connect-sdk (159 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 856 tokens. 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
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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.