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/basilisk-labs/agentplane/agentplane-local-dev-operatornpx skills add basilisk-labs/agentplane --skill agentplane-local-dev-operatorgit clone --depth 1 https://github.com/basilisk-labs/agentplaneWrote 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/basilisk-labs/agentplane/agentplane-local-dev-operator)<a href="https://agentmods.dev/skills/basilisk-labs/agentplane/agentplane-local-dev-operator"><img src="https://agentmods.dev/badge/skills/basilisk-labs/agentplane/agentplane-local-dev-operator.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00045 | $0.00475 |
| Opus 5 | $0.00023 | $0.00237 |
| Sonnet 5 | $0.00009 | $0.00095 |
| Haiku 4.5 | $0.00005 | $0.00047 |
Grade A, and why
agentplane-local-dev-operator 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 4d 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.
What it actually says
AgentPlane Local Dev Operator
Use This Skill When
- A task asks which local checks are sufficient for a change.
- A branch_pr worktree needs scope validation before commit or PR update.
- Dependency bumps need repo-specific triage before merge.
- A developer or agent wants graph-aware local evidence.
Core Rule
Prefer existing repo-local check routing and Turborepo evidence over broad, slow command chains. Use the narrowest check set that still covers the changed files and release risk.
Script Entry Points
bun run dev:impact
bun run dev:impact -- --json
bun run dev:task-scope:check -- --task-id <task-id>
bun run deps:triage
bun run deps:triage -- --write
bun run dev:turbo:affected
bun run ci:local:turbo
dev:impactlists changed files, the local CI selector bucket, and recommended commands.dev:task-scope:checkfails when branch_pr mutations appear onmainor the branch does not match the task id.deps:triageis dry-run by default; use--writeto run install/parity/schema/knip/local CI checks for dependency bumps.dev:turbo:affectedandci:local:turboproduce local graph/evidence reports under.agentplane/cache/and.turbo/runs/.
Dependency Bump Triage
Do not treat a successful lockfile update as proof that a dependency PR is safe. Run the affected repo surfaces:
bun run deps:triage -- --write
Expected evidence:
bun install --ignore-scriptsbun run release:paritybun run schemas:checkbun run knip:checkbun run ci:local:fast
If one dependency family fails, keep the failure scoped and either fix that migration in the same approved task or classify the bump as deferred/stale.
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.
- 4d ago First seen · 53 lines · 45 tokens per session scan A 3b91119613d1
agentplane-local-dev-operator is a skill published in the GitHub repository basilisk-labs/agentplane (76 stars, last pushed today), licensed MIT. It adds 45 tokens to every session and 475 once invoked, about $0.0002 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-30.
Other skills, from other repositories
html-ppt-zhangzara-coral
OpenDesign's community-growth campaign across GitHub, Discord, and X: the loops, the content calendar, and the pipeline math. Built as a decision-grade marketing & GTM deck for growth team, community lead.
hr-onboarding
A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".
html-ppt-hermes-cyber-terminal
OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.
html-ppt-taste-brutalist
16:9 HTML deck in tactical-telemetry / CRT-terminal taste. Deactivated-CRT charcoal slides, white-phosphor monospace, hazard-red accent, scanline overlay, ASCII syntax, density over decoration. Distilled from Leonxlnx/taste-skill brutalist-skill (Tactical Telemetry mode).
deepstream-sop
Use this skill when building, deploying, evaluating, debugging, or measuring latency for the DeepStream SOP Inference Microservice — a GPU-accelerated FastAPI service that detects whether operators perform assembly-line steps in order via event boundary detection (GEBD) plus VLM classification. Trigger even if the…
cupynumeric-migration-readiness
Pre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment…