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 GaosCode/PlanWeave --skill plan-importergit clone --depth 1 https://github.com/GaosCode/PlanWeaveWrote 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/gaoscode/planweave/plan-importer)<a href="https://agentmods.dev/skills/gaoscode/planweave/plan-importer"><img src="https://agentmods.dev/badge/skills/gaoscode/planweave/plan-importer/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/gaoscode/planweave/plan-importer"><img src="https://agentmods.dev/badge/skills/gaoscode/planweave/plan-importer.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 Rogue Agent · line 19 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00048 | $0.02412 |
| Opus 5.5 | $0.00019 | $0.00965 |
| Sonnet 5.5 | $0.00010 | $0.00482 |
| Haiku 4.5 | $0.00005 | $0.00241 |
Grade A, and why
plan-importer 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Importer
Use this skill to turn existing project planning material into a PlanWeave Plan Package.
Command Entry
Resolve the command before writing files:
- Use a user-provided command if given.
- Else try global
planweave. - In the PlanWeave repo, prefer
pnpm --filter @planweave-ai/cli planweave. - If the repo defines another local script, use that exact entry and show it in the report.
Write examples as <pw> ..., where <pw> is the resolved command.
Use the CLI to resolve the target workspace before writing files:
<pw> init --json
<pw> paths --json
<pw> validate --json
Use the CLI for command discovery, workspace/path resolution, and validation in this workflow. Materialize imports by writing package files directly into the CLI-returned PlanWeave workspace paths.
Workspace
- Run
<pw>from the target project root, not from the PlanWeave repo unless PlanWeave itself is the target project. - Do not create or write
./.planweaveinside the target project by hand. - PlanWeave stores project plans under
PLANWEAVE_HOMEwhen set; otherwise defaults to:- macOS:
~/.planweave - Linux:
~/.planweave - Windows:
%USERPROFILE%\.planweave
- macOS:
- Read exact workspace paths from
<pw> init --jsonand<pw> paths --json. - Write only inside CLI-returned PlanWeave workspace paths, such as
workspaceRoot,projectGraphPath, and package directories under that workspace. - For a single-canvas import with an explicit existing target canvas, write only inside that canvas package directory.
- For a single-canvas import without an explicit target canvas, do not overwrite the existing default/current canvas. Create a new formal canvas entry in
project-graph.json, allocate a collision-free canvas id, and write the imported package under that canvas package directory. - For formal multi-canvas plans, write
project-graph.jsonat the returned project/workspace root and write each canvas package only under the package directories named by that project graph. - Treat CLI-returned project/workspace and package directories as the only writable PlanWeave locations.
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 First seen · 144 lines · 48 tokens per session scan A 38a5f0acdfdd
plan-importer is a skill published in the GitHub repository GaosCode/PlanWeave (424 stars, last pushed 5d ago), licensed MIT. It adds 48 tokens to every session and 2,412 once invoked, about $0.0002 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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…