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/gtmagents/gtm-agentsWrote 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/gtmagents/gtm-agents/plan-pillar)<a href="https://agentmods.dev/commands/gtmagents/gtm-agents/plan-pillar"><img src="https://agentmods.dev/badge/commands/gtmagents/gtm-agents/plan-pillar/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/gtmagents/gtm-agents/plan-pillar"><img src="https://agentmods.dev/badge/commands/gtmagents/gtm-agents/plan-pillar.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.00019 | $0.00704 |
| Opus 5 | $0.00010 | $0.00352 |
| Sonnet 5 | $0.00004 | $0.00141 |
| Haiku 4.5 | $0.00002 | $0.00070 |
Grade A, and why
plan-pillar 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 8d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command: plan-pillar
Inputs
- theme – content pillar topic.
- window – program duration.
- channels – comma-separated roster (blog, video, webinar, social, email, enablement).
- audiences – optional persona/vertical list.
- goals – optional KPIs (pipeline, subscribers, product adoption).
GTM Agents Pattern & Plan Checklist
Derived from GTM Agents orchestrator blueprint @puerto/plugins/orchestrator/README.md#112-325.
- Pattern selection: Default to pipeline (brief → hero asset → derivatives → owners → distribution). Use diamond when creative pods and distribution prep can run in parallel; document the pattern in the plan header.
- Plan schema: Save
.claude/plans/plan-<timestamp>.jsonwith objective, asset stages, task IDs, parallel groups, dependency graph, error handling, and success criteria (e.g., MQL, pipeline, share of voice). - Tool hooks: Reference
docs/gtm-essentials.mdstack (Serena for CMS/landing updates, Context7 for brand/legal docs, Sequential Thinking for retros, Playwright for QA of landing pages). - Guardrails: Define retry strategy (default 2) and escalation ladder (Editorial Director → Creative Producer → Marketing Director) for missed approvals or QA issues.
- Review: Before execution, run the checklist in
docs/usage-guide.md#orchestration-best-practices-puerto-parityto confirm agents, dependencies, deliverables.
Workflow
- Brief Intake – align on objectives, persona needs, proof assets, campaign tie-ins.
- Hero Asset Definition – define flagship deliverables (ebook, webinar, video series) with requirements.
- Derivative Mapping – outline derivative assets per channel with rough cadence.
- Resourcing & Owners – assign writers, designers, reviewers, budgets, tooling.
- Distribution Hooks – highlight promotion partners, paid support, enablement ties.
Outputs
- Pillar blueprint table (asset, format, owner, due date, CTA, dependency).
- Creative brief package template per asset.
- Initial distribution + amplification notes.
- Plan JSON entry stored/updated in
.claude/plansfor audit trail.
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.
- 8d ago First seen · 49 lines · 19 tokens per session scan A de059cb48f11
plan-pillar is a command published in the GitHub repository gtmagents/gtm-agents (398 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 704 once invoked, about $0.0001 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-09-03.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.