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/markmhendrickson/ateles/create-execution-plannpx skills add markmhendrickson/ateles --skill create-execution-plangit clone --depth 1 https://github.com/markmhendrickson/atelesWhat 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.00050 | $0.00777 |
| Opus 5 | $0.00025 | $0.00388 |
| Sonnet 5 | $0.00010 | $0.00155 |
| Haiku 4.5 | $0.00005 | $0.00078 |
Grade A, and why
create-execution-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.
How it starts
The opening of the file, as written. The whole thing — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Execution Plan
Create an execution plan via Parquet MCP (Neotoma first if execution_plans are in Neotoma), avoid duplicates, and link tasks when the work is phased. No markdown files in truth/operations/execution-plans/.
When to Use
Use this skill when:
- User says "create execution plan", "add project plan", "create plan for [project]"
- User describes phased work that should be one task plus one plan (not parent + subtasks)
Required Documents (load first)
- Execution plans rules: docs/execution_plans_rules.mdc (Create Execution Plans, Task vs Subtasks, Task Creation Workflow, Schema Fields)
- Data access: docs/neotoma_parquet_migration_rules.mdc (query Neotoma first for execution_plans; Parquet as backup)
Workflow
- Query existing plans by name or project_id (Neotoma MCP first, then Parquet MCP) to avoid duplicates. Use
mcp_parquet_read_parquet(data_type="execution_plans", filters={"name": "..."})or by project_id. - If duplicate exists: Inform user and offer to update or link; do not create a second plan.
- If no duplicate: Create plan via Parquet MCP
mcp_parquet_add_recordwithdata_type="execution_plans". Include: execution_plan_id (e.g. 16-char UUID), name, project_id, project_name, status ("planning"|"planned"|"in_progress"|"completed"|"canceled"), domain, priority, objective, scope, milestones_phases, dependencies, constraints, success_criteria, start_date, created_date, updated_date, import_date, import_source_file ("manual_creation"). See docs/execution_plans_rules.mdc for full schema. - Task linkage: If the work is one initiative with phased steps, use one task + this execution plan (put phases in milestones_phases). Set plan's related_tasks to task_id and link task to plan. Use parent + subtasks only when each piece is a distinct deliverable with separate due dates/assignees.
- Never create or edit markdown in
truth/operations/execution-plans/.
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 · 47 lines · 50 tokens per session scan A 8873c8dc1a72
create-execution-plan is a skill published in the GitHub repository markmhendrickson/ateles (5 stars, last pushed 4d ago), licensed MIT. It adds 50 tokens to every session and 777 once invoked, about $0.0003 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-31.
Other skills, from other repositories
10x-orchestrator
MANDATORY - The core brain of 10X Vibe Marketer. You are the autonomous CMO orchestrating a full marketing agency of 12 specialist departments. Load this skill for ANY marketing task - content creation, SEO, campaigns, strategy, research, analytics, outreach, social media, email, paid ads, branding, funnel…
10x-setup
First-time setup and initialization for 10X Vibe Marketer. Includes an interactive wizard that lets users choose their database, features, marketing focus, visual tools, and tracking preferences. Checks setup.log to determine if setup has already been completed. Run via /setup or auto-triggered on first use.
10x-visualizer
Generate visual marketing deliverables — strategy boards, funnel diagrams, flowcharts, journey maps, dashboards, and more — using TLDraw SDK (local .tldr files). Each department agent creates visuals for their own domain. Invoke with /report.
community-manager
Skill "community-manager" from OpenAnalystInc/Vibe-Marketer, covering community manager — 10x vibe marketer, identity, step-by-step execution, cli visual identity and expertise.
10x-research
The research orchestration engine for 10X Vibe Marketer. Powers multi-platform, real-time research across 13 platforms using Claude in Chrome and WebSearch/WebFetch. Spawns platform-specific research agents in parallel, consolidates findings through the research lead, and delivers actionable marketing intelligence.
affiliate-specialist
Skill "affiliate-specialist" from OpenAnalystInc/Vibe-Marketer, covering affiliate specialist — 10x vibe marketer, identity, step-by-step execution, cli visual identity and expertise.