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 johnfkoo951/cmdspace-plugins --skill plangit clone --depth 1 https://github.com/johnfkoo951/cmdspace-pluginsWrote 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/johnfkoo951/cmdspace-plugins/plan)<a href="https://agentmods.dev/skills/johnfkoo951/cmdspace-plugins/plan"><img src="https://agentmods.dev/badge/skills/johnfkoo951/cmdspace-plugins/plan/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/johnfkoo951/cmdspace-plugins/plan"><img src="https://agentmods.dev/badge/skills/johnfkoo951/cmdspace-plugins/plan.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00058 | $0.00631 |
| Opus 5.5 | $0.00023 | $0.00252 |
| Sonnet 5.5 | $0.00012 | $0.00126 |
| Haiku 4.5 | $0.00006 | $0.00063 |
Grade A, and why
plan 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan — Implementation Planning
Creates a structured execution plan for any development task.
Workflow
Step 1: Gather Planning Context
Use AskUserQuestion:
{
"questions": [
{
"question": "What are you planning to build or change?",
"header": "Scope",
"options": [
{"label": "New feature", "description": "Building something new from scratch"},
{"label": "Refactor", "description": "Restructuring existing code without changing behavior"},
{"label": "Migration", "description": "Moving between technologies, versions, or architectures"},
{"label": "Bug fix campaign", "description": "Systematic resolution of multiple related issues"}
],
"multiSelect": false
},
{
"question": "How detailed should the plan be?",
"header": "Detail Level",
"options": [
{"label": "High-level (Recommended)", "description": "Phases, key tasks, and dependencies. Good for getting started."},
{"label": "Detailed", "description": "Every file to create/modify, specific implementation steps."},
{"label": "Sprint-ready", "description": "Detailed with effort estimates, broken into sprint-sized chunks."}
],
"multiSelect": false
}
]
}
Step 2: Explore the Codebase
Dispatch explorer (Haiku) to:
- Map the current project structure
- Identify relevant files and patterns
- Detect the tech stack and conventions
Step 3: Create the Plan
Dispatch planner (Opus) with the exploration results and user requirements to produce:
- Summary: What will be done and why
- Prerequisites: What must exist before starting
- Phases: Grouped tasks with dependency arrows
- Task Details: For each task — agent, tier, complexity, files involved
- Quality Gates: Checkpoints between phases
- Risks: What could go wrong and how to mitigate
- Estimates: Rough complexity scores (not time predictions)
Step 4: Present the Plan
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.
- 1mo ago First seen · 81 lines · 58 tokens per session scan A 91e7c22118ff
plan is a skill published in the GitHub repository johnfkoo951/cmdspace-plugins (7 stars, last pushed today), licensed MIT. It adds 58 tokens to every session and 631 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-31.
Other skills, from other repositories
obsidian-bases
Explain, draft, and validate Obsidian Bases .base files with filters, formulas, properties, summaries, and table, card, list, or version-gated kanban views. Use for Obsidian Bases, database-like vault views, dynamic tables, reading lists, task trackers, filters, formulas, summaries, and .base file edits.
wiki-ingest
Ingest supplied source material into an Obsidian vault with provenance and claim tracking: pasted text, files staged in the selected vault's inbox or .raw archive, or explicitly approved URLs. Use for a single source or bounded batch, not for saving an assistant answer. Triggers: ingest, ingest this file, ingest this…
autoresearch
Run a bounded, source-grounded research loop, draft a cited dossier, and optionally propose a separately reviewed canonical vault merge. Use when the user wants autonomous or deep research that may access the public web. Triggers: /autoresearch, autoresearch, research this topic, deep dive into, investigate, find…
wiki-retrieve
Build and query a vault-local contextual BM25 retrieval index with optional multilingual Nomic cosine reranking; use for retrieve, hybrid retrieval, BM25, rerank, contextual retrieval, chunk search, vault search, semantic search, find relevant passages, or retrieval diagnostics. Derived caches stay under .vault-meta…
ariadne:workspace-instructions
Create or update workspace-level instruction files for code repositories or ordinary project folders, including AGENTS.md, CLAUDE.md, GEMINI.md, local override files, and Ariadne vault-link blocks. Use when a user wants to initialize, repair, or refresh workspace instructions, connect a workspace to a registered…
ariadne:global-discovery
Register existing Markdown knowledge vaults for machine-level discovery so cold agents can find long-term knowledge from any workspace. Use when checking, adding, updating, repairing, or removing global vault discovery.