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/ayoubben18/ab-method/create-goalgit clone --depth 1 https://github.com/ayoubben18/ab-methodWhat 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.00608 |
| Opus 5 | $0.00000 | $0.00304 |
| Sonnet 5 | $0.00000 | $0.00122 |
| Haiku 4.5 | $0.00000 | $0.00061 |
Grade A, and why
create-goal 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Goal
Description
Produce a ready-to-run goal prompt for an autonomous /goal loop (Claude Code or Codex), using the AB Method's grilling + domain-grounding workflow.
Usage
/create-goal
Behavior
Loads and executes the create-goal workflow from .ab-method/core/create-goal.md
This workflow will:
- Always invoke
grill-with-docsto interview the user and pin down the objective, a verifiable measurable end state, the feedback loops that steer the loop, and constraints (no skip) - Read UBIQ + CONTEXT + tech-stack + patterns + ADRs to ground the goal in canonical terms
- Write
docs/goals/<goal-name>/goal.md— the prompt you paste into/goal - Write
docs/goals/<goal-name>/progress-tracker.md— an empty notes log the loop fills as it runs - Stop.
/create-goalproduces the files; the/goalloop does the work
/create-goal vs /create-task
/create-goal— one continuous objective with a verifiable stop condition, handed to an autonomous loop you walk away from/create-task— broken into missions you review and run throughtddyourself, one at a time
Workflow Details
- Always grill —
grill-with-docsruns on every invocation - Verifiable end state required — if "done" can't be checked by a command, the workflow keeps grilling or recommends
/create-task - Feedback loops steer the run — the grill captures the checks (tests, type-check, build, visual checks) the
/goalloop runs every iteration to self-correct - The loop is told about the tracker —
goal.mdexplicitly instructs the/goalloop to maintainprogress-tracker.md, logging only important discovered facts (no generic narration) - References docs, doesn't inline them — the loop reads UBIQ/CONTEXT/architecture in-repo
- Black boxes are briefed, never decided (rare) — a question you genuinely can't answer yet is parked in
docs/goals/<goal-name>/unresolved-questions.md, andgoal.mdgets a Black boxes section telling the loop to build the agreed placeholder behind aTODO(UQ-n)seam and never to answer the question itself. The measurable end state may never depend on an open question — if it does, the goal isn't ready
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 · 45 lines · 0 tokens per session scan A 3b5eeddb423b
create-goal is a command published in the GitHub repository ayoubben18/ab-method (187 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 608 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
git
Git operations with intelligent commit messages and workflow optimization.
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.
constitution
Create or update the project constitution from interactive or provided principle inputs.