Borrowing it
Nothing to install: this file belongs to phase-rs/phase. 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/phase-rs/phase/main/.claude/skills/project-reference/SKILL.mdgit clone --depth 1 https://github.com/phase-rs/phaseWrote 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/phase-rs/phase/project-reference)<a href="https://agentmods.dev/skills/phase-rs/phase/project-reference"><img src="https://agentmods.dev/badge/skills/phase-rs/phase/project-reference/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/phase-rs/phase/project-reference"><img src="https://agentmods.dev/badge/skills/phase-rs/phase/project-reference.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
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 →
- high Tool Misuse · line 292 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- medium Agent Snooping · line 209 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Excessive Agency · line 292 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00117 | $0.06383 |
| Opus 5.5 | $0.00047 | $0.02553 |
| Sonnet 5.5 | $0.00023 | $0.01277 |
| Haiku 4.5 | $0.00012 | $0.00638 |
Grade A, and why
project-reference 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 8d 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 — 340 lines — stays where its author put it; the contents beside it link to each section on GitHub.
phase.rs Project Reference
Lookup material for build commands, the verification cadence, architecture, environment variables, releasing, and CI. The always-on rules (design principles, Tilt-not-cargo, building blocks, CR annotations, Rust idioms) live in the root CLAUDE.md / AGENTS.md; this skill holds the on-demand reference that doesn't need to be resident every turn.
Tilt resources & operational rules
Tilt is always running and continuously rebuilds on file changes. Do NOT run cargo build, cargo clippy, cargo test -p phase-engine, pnpm run type-check, or pnpm lint directly — they compete for cargo target locks. Check Tilt logs instead.
Available Tilt resources (defined in Tiltfile):
| Resource | What it does | Triggers on |
|---|---|---|
clippy |
cargo clippy --all-targets -- -D warnings |
crates/ changes |
test-engine |
cargo test -p phase-engine |
crates/engine/src/ changes |
test-ai |
cargo test -p phase-ai |
crates/engine/src/ or crates/phase-ai/src/ changes |
wasm |
WASM build (depends on clippy) | engine/AI/WASM src changes |
card-data |
./scripts/gen-card-data.sh |
crates/engine/src/ changes |
check-frontend |
pnpm run type-check && pnpm lint |
client/src/ changes |
test-frontend |
pnpm test -- --run |
client/src/ changes |
server |
Build + serve phase-server | server src changes |
coverage |
cargo coverage |
Manual trigger only |
How to check results:
tilt logs clippy --tail 30 --since 2m # Recent clippy output
tilt logs test-engine --tail 50 --since 2m # Recent test results
tilt logs card-data --tail 20 --since 1m # Card data gen output
tilt logs check-frontend --tail 30 --since 2m # TS type-check + lint
How to wait for current results without dumping logs:
./scripts/tilt-wait.sh clippy test-engine card-data # wait until all settle (no timeout)
./scripts/tilt-wait.sh --interval 10 clippy # poll faster for a single fast resource
./scripts/tilt-wait.sh --timeout 600 clippy test-engine # bound the wait
Exit codes: 0 all ok, 1 a resource is in terminal error (updateStatus=error with no in-flight build), 2 usage error, 3 cannot answer the question, 124 timeout (only when --timeout is set). The script prints one <resource> status=… current=… last=… line per tick so you can see why a wait is taking time without paying for log payloads. After exit 1, fetch details with tilt logs <resource> --tail 50 --since 2m.
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.
- 8d ago Changed · +34 lines · +7 tokens per session 8053eb13ca40
- 2mo ago First seen · 306 lines · 110 tokens per session scan A 76d73fbb793f
project-reference is a skill published in the GitHub repository phase-rs/phase (313 stars, last pushed today), licensed Apache-2.0. It adds 117 tokens to every session and 6,383 once invoked, about $0.0005 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
anarlog
Query Anarlog meetings, notes, summaries, transcripts, participants, action items, and recurring history, or import a local recording. Use when a user asks about their Anarlog meeting data or needs meeting context for another task.
tauri-pilot
Inspect, interact with, and test a running Tauri v2 app via CLI. Communicates over Unix socket using JSON-RPC 2.0. Use when testing UI, automating interactions, or debugging a Tauri app.
systematic-debugging
4-phase systematic debugging methodology with root cause analysis and evidence-based verification. Use when debugging complex issues.
tdd-workflow
Test-Driven Development workflow principles. RED-GREEN-REFACTOR cycle, writing failing tests first, and enforcing behavioral verification.
testing-patterns
Testing patterns and principles. Unit, integration, mocking strategies, Arrange-Act-Assert (AAA), and multi-ecosystem test runners.
webapp-testing
Web application testing principles. E2E, Playwright, deep audit strategies.