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 commands/geckse/markdown-vdb/plangit clone --depth 1 https://github.com/geckse/markdown-vdbWhat 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.00000 | $0.00381 |
| Opus 5 | $0.00000 | $0.00191 |
| Sonnet 5 | $0.00000 | $0.00076 |
| Haiku 4.5 | $0.00000 | $0.00038 |
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 2d 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
Plan: Create a Structured Implementation Plan
Take the following feature description and create a comprehensive, structured implementation plan.
Feature: $ARGUMENTS
Process
-
Understand the request — Parse the feature description above. Identify what needs to change and what stays the same.
-
Research the codebase — Read relevant source files to understand current patterns. Check existing code for conventions, architecture, and testing patterns. Read
CLAUDE.mdfor project context. -
Ask clarifying questions — IMPORTANT: Before writing the plan, use the AskUserQuestion tool to ask at least 5 questions about requirements, edge cases, and design decisions. Cover: scope boundaries, error handling, backward compatibility, testing expectations, and UI/UX decisions. Provide suggested answers based on your codebase research.
-
Write the plan — After receiving answers, create a structured plan with these sections:
Summary
One-paragraph description of what will be built.
Files to Modify
List every file that needs changes, with a description of what changes.
Files to Create
List any new files, with their purpose.
Implementation Steps
Numbered steps in implementation order. Each step should reference specific files and describe the exact changes.
Testing Plan
Which existing tests need updating, what new tests to write, and how to verify the feature end-to-end.
Patterns to Follow
Reference specific patterns from the existing codebase that the implementation should match.
-
Save the plan — Write the plan to
docs/plans/$ARGUMENTS.md(kebab-case the arguments). Create thedocs/plans/directory if it doesn't exist.
The plan should be detailed enough that a fresh Claude session with only the plan as input could implement the feature correctly.
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.
- 2d ago First seen · 38 lines · 0 tokens per session scan A 9495081a5a3f
plan is a command published in the GitHub repository geckse/markdown-vdb (23 stars, last pushed 18d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 381 tokens. 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 commands, from other repositories
fieldtheory
Explain and drive the Field Theory CLI — bookmark-sourced seeds, repo-aware possibility runs that score ideas onto a 2x2 grid, and the interconnected .md files they leave behind. Trigger when the user asks about ft, bookmarks, seeds, ft possible (or the older name ft ideas), grids, dots/nodes, or how to turn saved…
issue-amend
Re-snapshot the active issue's scope from the spec, clear verified and reviewed receipts, and record the change as a permanent amendment.
q-research
Read the research-mode skill's SKILL.md for the full ruleset before proceeding. Follow all constraints, the source lookup cascade, the token budget, and the "what counts as cited" rules exactly.
demo-command
Example slash command that wraps the demo-skill. Showcases the command kind.
ingest-l1
L1 analysis loop for the abapwiki knowledge base: for each batch it launches the abap-analyzer sub-agent in parallel, then the adversarial judge abap-deepcheck (separate session), applies only the analyses that pass the fail-closed gate, and commits. Resumes exactly after an interruption. Use this skill to document…
web-search
Search fetched web-source Markdown by regex and pull surrounding context for the best hits. Optionally restrict to one source alias.