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/perhapsspy/project-legibility/project-context-migrationnpx skills add perhapsspy/project-legibility --skill project-context-migrationgit clone --depth 1 https://github.com/perhapsspy/project-legibilityWhat 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.00027 | $0.00474 |
| Opus 5 | $0.00014 | $0.00237 |
| Sonnet 5 | $0.00005 | $0.00095 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
project-context-migration 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.
How it starts
The opening of the file, as written. The whole thing — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Context Migration
Purpose
Audit scattered repository docs and notes before moving the right working context into project-context. Apply the main project-context contract first. Use this companion only for existing legacy context, not to initialize an empty repo.
Classification
TASK: material that belongs in agent working context but is task-local, historical, exploratory, unresolved, or not trusted as current truth.REFERENCE: current trusted rules, facts, or shared contracts another task can directly reuse.LEAVE: product/user/team docs, human-facing top-level notes, and origin/about/repository narrative that do not belong in agent working context.ARCHIVE: stale duplicates or superseded docs only when cleanup is authorized; it is not a defaultproject-contextdestination.
LEAVE is a valid result. If membership in agent working context is uncertain, use LEAVE; if membership is clear but current truth or adoption is uncertain, use TASK. Do not promote content to REFERENCE merely because it is technical.
Migration Contract
Inventory candidate sources read-only, then resolve each source or separable part to a classification, currentness, existing owner, target or leave decision, and reason. Persist this map in one dated migration task before rewriting, moving, archiving, or deleting content.
Apply only the resolved map. Preserve existing canonical and human-facing owners; merge overlapping working context into one preferred task or reference owner. Rewrite current reference truth instead of copying timeline noise, and keep comparison detail, rationale, uncertainty, and change trace in the migration task.
Preserve shipped authority and human-facing documents outside project-context. Normalize saved paths to repo-relative paths or stable placeholders. If an item lacks a trustworthy date, use the migration date and record that uncertainty in its task.
Run the main runtime-shape checker, then reconcile the map and spot-review representative or high-risk classifications and owner transitions. Shape success does not prove migration correctness.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 34 lines · 27 tokens per session scan A ef6647c6bcf3
project-context-migration is a skill published in the GitHub repository perhapsspy/project-legibility (5 stars, last pushed 5d ago), licensed MIT. It adds 27 tokens to every session and 474 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
author
Write a new doc in the right place with the right name. Use when asked to "write a doc", "where should this doc go", "add an ADR", "document this decision", "new spec", or "new feature plan".
router
Find the right doc before reading code. Use when asked "where is X documented", "is there a spec/ADR for X", "what's the roadmap", "open bugs", "read the docs about X", or "share the docs".
changelog
Record shipped work in the monthly changelog (append-only). Use when something ships or when asked "what changed", "add to changelog", "release notes", or "what shipped this month".
init
Set up docflow in a repo with no docs yet: scaffold the docs tree, write docflow.json, add agent guidance. Use when asked to "set up docflow", "initialize docs", "scaffold docs", or "make this repo use docflow".
check
Friendly docflow readiness check: one status, one reason, and the exact next command. Use when asked if docflow is set up, ready, or "what do I do next".
doctor
Read-only docflow diagnosis: scans docs, config, changelog, and links, then recommends init, adopt, or repair. Use when asked "check docs setup", "should I set up docflow", "why is docflow not working", or "doctor".