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.
git clone --depth 1 https://github.com/markmhendrickson/neotomaWrote 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/commands/markmhendrickson/neotoma/migrate_plans)<a href="https://agentmods.dev/commands/markmhendrickson/neotoma/migrate_plans"><img src="https://agentmods.dev/badge/commands/markmhendrickson/neotoma/migrate_plans/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/commands/markmhendrickson/neotoma/migrate_plans"><img src="https://agentmods.dev/badge/commands/markmhendrickson/neotoma/migrate_plans.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.00000 | $0.03615 |
| Opus 5.5 | $0.00000 | $0.01446 |
| Sonnet 5.5 | $0.00000 | $0.00723 |
| Haiku 4.5 | $0.00000 | $0.00362 |
Grade A, and why
migrate_plans 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 — 500 lines — stays where its author put it; the contents beside it link to each section on GitHub.
migrate_plans
Automatically review all plans in .cursor/plans/, determine relevance, and migrate relevant ones to docs/proposals/ for future consideration.
Purpose
This command:
- Reviews all plan files in
.cursor/plans/ - Determines which plans are still relevant (pending work, architecture aligned)
- Migrates relevant plans to
docs/proposals/with appropriate format - Archives completed plans to
docs/proposals/archived/ - Generates a migration report
Usage
Standalone execution:
/migrate_plans
Automatic execution:
- Runs automatically during
/commitworkflow (after security audit, before staging) - Can be disabled in
foundation-config.yaml
Configuration
Enable/disable in foundation-config.yaml:
development:
commit:
migrate_plans: true # Enable automatic plan migration during commit
migrate_plans_config:
proposals_dir: "docs/proposals"
archive_completed: true
auto_remove_obsolete: false
relevance_check:
check_architecture: true
check_completion: true
check_duplicates: true
Relevance Criteria
The migration command analyzes plan content (not just todos) to determine implementation status:
Implementation Analysis
For each plan, the command:
-
Extracts implementation items from plan content:
- File paths (
src/services/...,**/migrations/...) - Function names (
createDeletionObservation,generateRecordSummary) - API endpoints (
/gdpr_delete,/store_record) - Database tables/columns (
CREATE TABLE,ALTER TABLE) - Services (
src/services/deletion.ts)
- File paths (
-
Checks if items exist in the codebase:
- Files: Checks if file exists
- Functions: Searches codebase for function definitions
- Migrations: Finds migration files matching patterns
- Endpoints: Searches
actions.tsandserver.ts - Tables/Columns: Checks
schema.sql
-
Calculates completion percentage:
found_items / total_items * 100- Example: 18/31 items found = 58% complete
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 · 500 lines · 0 tokens per session scan A 3f20370bb8b0
migrate_plans is a command published in the GitHub repository markmhendrickson/neotoma (34 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,615 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-09-03.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
my-tasks
Track, prioritize, and execute tasks with goal alignment and due date awareness. Claude doesn't just remind you — it helps get work done.
sugar-task
Create a comprehensive Sugar task with rich context and metadata.
shortlist
Select and prioritize MVP features from an existing backlog.
arckit.traceability
Generate requirements traceability matrix from requirements to design to tests.